3 ms·
FWIW, I work on Google Search, possibly the largest software system on the planet, and Google is famous for being tester-light and automation-heavy. We rely mu
by nostrademons 17y ago
FWIW, I work on Google Search, possibly the largest software system on the planet, and Google is famous for being tester-light and automation-heavy. We rely much more on code reviews and on having good engineers who aren't rushed than on testers.
The reason is just as you state: beyond a certain point, the number of states in the system becomes so great that you simply can't test them all. Replacing developers with testers doesn't change that. So you're better off understanding what you're doing than trying to avoid all the possible ways that you could go wrong.
- ericb 17y agoAutomation heavy is a good thing in my book. I think whether the developer writes it is often a function of what you're testing. For example, WinRunner has its own learning curve, and so seems to be left to QA more often. Whereas Selenium seems to have a smaller curve. Generally though, I like the idea of someone else proofreading my work, because for the same reason that I forgot to account for a set of inputs, I will tend to forget to test with those inputs.