3 ms·
Dev sometimes aren't the best QA because they think like developers and not like end users. The mindset prevents you from doing things on the corners that end
by protomyth 5y ago
Dev sometimes aren't the best QA because they think like developers and not like end users. The mindset prevents you from doing things on the corners that end users do. Its like your instincts kick and a keep you safe without the railing where an end user might plow ahead thinking their path is ok and fall off the edge.
Devs should do automated unit and functional tests, but after that, get some good QA that do not have the same boss (at least at the first level) as the developers.
- regularfry 5y agoThis can absolutely be learned, enabled, and encouraged by the right guidance and, if necessary, training at the dev-team level. It's just part of the job.
- detaro 5y agoCan be, yes. Devs aren't always the best group to do that with though. I've had quite a bit of user training in a product I work on, but unsurprisingly the QA group of people who in their primary roles use it daily and have degrees in the problem domain are way more effective at finding non-obvious problems.
- protomyth 5y agoI really don't think any Dev team will be as good at QA as a dedicated QA team. The mindset is very different and the context switch is hard. Checking your own work is also not the greatest of ideas.
- regularfry 5y agoYou are free to think that. I've seen it done.
- tester34 5y agofor what kind of software? if your product is e.g docker, git - then yea, easily if it's soft for different industry, then complexity increases
- regularfry 5y agoPublic-facing web apps in this case, with internally-facing domain-expert interfaces.