b******g
发帖数: 81 | 1 正在进行技术路线的评估，看了网上很多评论和一些例子程序。感觉这个Test Driven
Development挺吸引人，可总觉得什么地方缺了点。
不知道哪位实践过，说说优缺点。
谢了！ |
c**d
发帖数: 579 | 2 优点是如果按代码行数收费你的收入会翻倍，缺点是写完程序后不需要再写unit
testing没事可干 |
N********n
发帖数: 8363 | 3 TDD is the way to go especially for large projects. Not a whole lot
of shortcomings worth mentioning in my mind.
Driven
【在 b******g 的大作中提到】
: 正在进行技术路线的评估，看了网上很多评论和一些例子程序。感觉这个Test Driven
: Development挺吸引人，可总觉得什么地方缺了点。
: 不知道哪位实践过，说说优缺点。
: 谢了！
|
b******g
发帖数: 81 | 4 What is the role for TDD after the system has been integrated. Are there any
integration test practice using TDD?
There are articles saying TDD is not sufficient for GUI test and Database
test:
http://en.wikipedia.org/wiki/Test-driven_development#Limitations
How will TDD method handle GUI and Database. Sometimes I have requirements
like "when I submit an sales order, I want anther shipping order been
created also, blah blah blah". That kind of requirements is a nightmare for
testing. According t
【在 N********n 的大作中提到】
: TDD is the way to go especially for large projects. Not a whole lot
: of shortcomings worth mentioning in my mind.
:
: Driven
|
c**d
发帖数: 579 | 5 suppose in your business logic layer you have this code to insert a new
sales order,
ISalesOrderRepository.Insert(order);
and the following code to insert a new shipping order
IShippingOrderRepository.Insert(shippingOrder);
You will need a test to verify whether both code are called exactly once.
Moq is a good .net mocking framework for this purpose.
You will also need integration tests to check whether the orders are
actually inserted into the database. |
