DEV TEST- Test Driven Development (Integration Test)

Tdd
is about showing external observable behavior， it is a design tool and rely on your test to dictate how your structure your code.

 

 [TestMethod]public void MOQ_Return_ItemTypeId(){Mock<IItemTypePersistence> ItemTypePersistence = new Mock<IItemTypePersistence>();ItemTypePersistence.Setup(c => c.Save(It.IsAny<ItemType>())).Returns(1);int i = ItemTypePersistence.Object.Save(new ItemType());Assert.IsTrue(ItemTypePersistence.Object.Save(new ItemType()) == 0, "Expect 0 Returns " + i.ToString());}

 

 

1 outline all the function / rules you want to test.

 

2. naming the functionakies/class is not  important, throw in ur biz domain class / interface under the test project and let your thoght stream runs.

 

3.dont pay too much attention on challwnging detail, focus on what is known and start your work firat

 

4.all class with behavior can have interface defined and mock it.cuz a lot of time they are dependencies.

constantly changing the processor.processPayment method after feeding the charger mocker object and customer entity to processor.

 Integration Test

TDD and UT only garantee the quality up to the class and method.

An integration test is a test designed to target the various seams in an application and ensure that
the pieces of the application work together correctly. They are similar to unit tests in that the same
automated unit testing framework can (and should) be used to create them. They differ in that
unlike unit tests, which use mocks to isolate specifi c methods and classes under test, integration
tests cover all the application code between the method that the integration test was written for, all
the way to the lowest level of the system, usually the data store.

in brownfield development (you are maintaining, extending, or
enhancing an existing application) without existing unit tests, 

integration tests may be the only
option available for automated testing if practices such as dependency injection were not employed
in the application design

it is usually economically unfeasible to
reengineer the code base to introduce the dependency injection that would allow true unit testing.
In these cases, remember that any testing (even integration testing) is better than no testing at all.