Normally in component testing, the developer who writes the code writer the unit tests. Very often, what i consider the achilees heel is that the unit test will be positive flow. Code coverage ranges from anything higher than 70% and which is usually met with ease just looking at the targets.
The absurdness in setting KPIs is that KPIs eventually become reality.
Anyways, the other less used but much better for quality is that tester writes the unit tests. The difference between developer coding unit tests and the tester coding it will be the difference between how developer and tester tests the product. The number of tests are exhaustive and more meaningful and covers negative flows as well.
What is probably the most effective component testing is the test driven development in agile world. In this approach, the unit tests are first written and ensured that it fails. Then actual code is written so that the failed TC passes. Writing unit test and code happens in sequence and is highly effective when done by two different programmers working in pair mode.
Will write more about TDD is days ahead. Enough for now.
The absurdness in setting KPIs is that KPIs eventually become reality.
Anyways, the other less used but much better for quality is that tester writes the unit tests. The difference between developer coding unit tests and the tester coding it will be the difference between how developer and tester tests the product. The number of tests are exhaustive and more meaningful and covers negative flows as well.
What is probably the most effective component testing is the test driven development in agile world. In this approach, the unit tests are first written and ensured that it fails. Then actual code is written so that the failed TC passes. Writing unit test and code happens in sequence and is highly effective when done by two different programmers working in pair mode.
Will write more about TDD is days ahead. Enough for now.
No comments:
Post a Comment