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
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.