3 ms·
Dev writing automation tests for their code is kinda pointless. It would be better to have another dev or a different team such as automation engineers writing
by CodeSheikh 11y ago
Dev writing automation tests for their code is kinda pointless. It would be better to have another dev or a different team such as automation engineers writing regression automation tests. Automating regression tests is definitely better than manual QA-ing the same 1000 tests over and over again. There has to be a good balance. Have extensive coverage of automated regression tests and let manual QA test new features. This will at least increase the frequency of release cycles. Getting rid of an entire QA dept is somewhat equivalent to shooting yourself in the foot.
- sanderjd 11y agoThis is basically my experience. I think the ideal situation is having development and QA cultures that both prioritize quality and automation. Development cultures sometimes fail to prioritize quality ("not our problem"), and QA teams sometimes fail to prioritize automation ("not how we do things"), but those are problems with those specific cultures, not with the entire concepts of development and QA.
- serge2k 11y agoNah, you write the code you write the tests. Then you do a code review and make sure that the reviewer examines the code for missed cases.