3 ms·
The problem with having a separate test group is that developers who don't test don't write anything to be testable. They don't add features that allow fault in
by jschwartzi 10y ago
The problem with having a separate test group is that developers who don't test don't write anything to be testable. They don't add features that allow fault injection, and they don't modularize code to be independently tested. As a result, testing any of their code is highly tedious.
Developers should also write their own tests. QA should have tests too. It shouldn't be a matter of throwing software over the fence to a separate group.
- alkonaut 10y agoHopefully no company has a QA department or QA person ("Tester") that writes unit test for code already written by a developer. Unit tests can't be separated from the code, and has to be written in conjuction with the code. That said, it's often possible to write higher level tests in advance as a specification, or afterwards as a regression/integration suite. Testing code can be used for many things such as UI regression testing, performance testing etc. That kind of test is black box and not tied to a specific piece of code. So I think it's hard to debate "who tests" or "who writes tests" without discussing exactly what kind of test.
- BaronSamedi 10y agoThis is a problem that a good project manager and the company's development culture can solve. Ops also frequently has things they need from developers but rarely get.