>Having an internal QA team is not a practical solution if you want to deploy your application frequently. By having testers who are not connected to your comp

>Having an internal QA team is not a practical solution if you want to deploy your application frequently. By having testers who are not connected to your company nor care about its success, you overlook a crucial feature of having in-house QA. It doesn't have to mean weeks of non-stop manual regression testing. It means having a team working in tandem with developers to create unit, functional, and integration tests for rapid deployments. I've used mechanical turk and similar services for data entry and other repetitive tasks, and it can be useful. But quality, usability testing, and sanity checking are the last areas I would consider handing over a mechanical turk service. The notion that "In-house QA is killing your business" is one of the most laughable tech articles I've read all year. The hyperbole from Rainforest is over the top.