5 ms·
But then you're settling for low quality testing. There's an excellent methodology a good test team uses on devs that throw it over the wall. They throw it back
by splitstud 5y ago
But then you're settling for low quality testing. There's an excellent methodology a good test team uses on devs that throw it over the wall. They throw it back with the first bug report.
That said, it's sometimes the right thing for the team when something gets thrown over raw. A good test team should be fine with that and play their part.
- void_mint 5y ago> But then you're settling for low quality testing. Not necessarily though. I would also argue that manual testing is just an insurmountable timesink. You'll never have enough time because manual testing balloons to the time allotted. > There's an excellent methodology a good test team uses on devs that throw it over the wall. They throw it back with the first bug report. Sure, but continuing a cycle of "not my problem" helps no one and wastes time. Removing QA as a team/role/specialization, and instead making it a step in the process a dev goes through to ship software, you're fixing the broken feedback cycle QA teams create.