ScrimmageQA

An often repeated truism: “Shipping good software is difficult.”

When it comes to shipping good software, testing is crucial. While there are a lot of tools which make automating tests about as easy as can be, running manual verification among a team often seems very ad-hoc and error-prone.

But why do manual testing at all? Isn’t automated testing enough? No doubt - automated testing is very important.

However, automated tests will not do things like discover if your user interface is confusing. Oftentimes automated tests are rather complex and have bugs themselves. All tests can pass and there can still be a bug in your software.

The next line of defense is manual QA testing - actually using the product.

Groups with a dedicated QA team split testing responsibilities away from developers. In theory this allows testers to focus on testing and developers to focus on developing. In practice it can sometimes lead to very poor communication between teams and bugs being released to production.

Increasingly often, teams are merging the roles of development and QA. Now dev and product teams are expected to be solely responsible for the quality of their software. Yet team members don’t feel like they have a good idea of what exactly they should be testing or how to divide up responsibilities. This inevitably leads to uneven code coverage and bugs in production!

ScrimmageQA is our take on automating the coordination of your QA process. Our product aims to augment your current process, and works with dedicated QA teams, self-testing teams and cooperatively with automated testing.

We strongly believe that automated and manual testing should work cooperatively, and can even serve to periodically keep each other honest.