Focus: Test Design, Coding Style, Not Test Patters
What is the problem ? In general, we will avoid following thing when we writing tests:
Test Code is hard to read.
Lack of design patterns. There are many C# design patterns, what and how we should use?
Legacy code is hard to test, Legacy test code is hard to maintain. So we want avoid this happen when we start to use programming way to write test. We want the test only change when the spec/requirement is changed.
Sometime, we lose the connected between test spec and test code. We can make a test as a document which describe what it want to achieve.
TODO, can we give some example?
What are we today? We need to find the answer. Asking PipiLine guys, ADO .Net guys 's experience can give us some idea, also can we should some example from outside of SQL.
What is the relationship between other testing projects? Let us find it out
Why we need do something? Apparent, we need to convince ourself and the convince others.