Done right, an in-house QA team provides an enormous amount of value to an organization. Their expertise in testing strategies and testing tools, combined with their familiarity with your product and customer, can help developers ship fast and deliver a great user experience.
But building an effective in-house team takes significant investment in both people and infrastructure. Without the right systems in place, end-to-end regression quickly becomes a bottleneck, or gets side-stepped by fast-moving teams.
Using this calculator, you’ll be able to estimate the ongoing costs of maintaining an in-house team. When you’re ready, schedule time with someone from our sales team to see how much QA Wolf will save you.
80% is considered a good goal for end-to-end testing.
Team size is a helpful way to estimate an app's complexity and needs. More.
Expect about 50 cases for junior hires, and 100 for very senior hires. More.
One can typically manage the testing infrastructure.
We’ve found that team size is a pretty reliable indicator of how complex your application is, and how many test cases you’re likely to need. For an application to have 80% end-to-end test coverage, expect to need about 25 tests cases per developer.
Through our own experience, as well as interviews with QA engineers, managers, and technical leaders, we’ve found that an experienced, full-time QA engineer can maintain a suite of 50–100 test cases. Maintenance means keeping tests reliably functioning, and accurately reporting, as the product changes. Their capacity increases and decreases based on their experience, the complexity of the product, and how often new features are released.
We’re using base salaries without benefits or other comp for openings in large and mid-sized cities as of January 2022. For QA engineers, salary ranges were taken from job openings like Senior QA Engineer and Senior Test Automation Engineer. For SDET, titles included Senior Software Engineer in Test and SDET.
Parallelization becomes more and more critical as your team grows so your developers avoid blocking each other during test runs. It also becomes more expensive. As of January 2022, the two biggest cross-browser testing platforms were charging $116 per parallel test run per month for enterprise customers.