Unit testing is a nice development discipline to stabilize, reach quality faster, and reduce QA bottleneck
By
Jonathan Vargas
on February 23, 2007
If developers apply unit testing, they reduce most of functionality bugs, and QA testing gets better testable builds. There is a lot of bottleneck when during the development phase (implementing scope) both QA and development roles play together.
Agreed
33
1
97.1% 2.9%
Embed Claim
Make a related claim
Claims inspired by this one
Similar claims
- 44-18 I do use unit testing in my projects
- 23-25 We use a software testing discipline at my work
- 66-5 Unit tests can be useful, but they're not the magical bug-killing silver bullets they're often made out to be.
- 34-23 I use trac
- 97-16 The single most important activity on the Internet hasn't been developed yet.
Discussion (1)
I quibble with the 'and'.
In my experience, unit Tests does nothing to address the QA bottleneck. If QA is less rigorous with any section of code because of unit tests, then they have failed.
Now, there may be less breaks due to unit tests, but that doesn't significantly reduce their bottlenecks, which have (in my experience) almost always been due to too little time between code complete and release dates, rather than due to number of breaks and retesting.