QASource, in conjunction with Sauce Labs, recently presented the webinar "Measuring Your Way To Successful Automation." When preparing each webinar, we field a variety of questions about the topic at hand. We have coordinated with our expert automation engineers to answer several of the most common questions about team metrics and measurement approaches below:
For many U.S.-based software product companies, outsourcing is a cost-effective way to retain top talent at an affordable rate. The IT sector is booming in places like India, Mexico, and South America, and companies that aren’t quite ready to hire on an in-house QA team often meet their needs with an offshore provider. Inevitably, challenges arise. How do the teams stay in communication? How does the outsourced QA team learn the company, product, and working culture? In short, how do we make this arrangement work?
The future of your product is in the hands of many people: your engineers, your business analysts, and your senior leaders. But it’s also in the hands of another group of people that may be overlooked. Who are those people? Your QA team! QA engineers are tasked with ensuring the quality of the product. They’re the last line of defense between the bugs that can run your product (and business reputation) into the ground and your users.
Though most product companies are vigilant in protecting themselves and their product from security vulnerabilities, they often cut corners when it comes to other concerns, such as load testing, UI testing, and API testing. The consequences of this type of corner-cutting are not as drastic as the PR fallout that follows massive cyberattacks, but they are dangerous to company image nonetheless.
Product companies who balked at QA outsourcing in the past are now running to it with open arms. Rapid release schedules along with high overhead costs have QA Managers and CTOs searching for a solution that is affordable, not cheap. Enter outsourcing!
Opening up your product to a skilled, dedicated offshore team comes with too many advantages to list here, but rest assured -- there are many. But the one aspect of outsourcing that many still worry about is communication. How can you be sure that your QA partner will communicate with you promptly, clearly and without any technical hang-ups?
Agile processes have been adopted by most software testing companies to keep up with rapid release schedules and customer demand. Gone are the days of slow but big results under the waterfall model -- Agile requires dev and testing teams to work hand-in-hand to produce fresh, fast results on a weekly basis.
There’s no way that this approach is working without a significant of automated testing in place, so let’s make that first on the list.
Why do most product companies hire a QA partner? The details vary, but the main reason is this: it’s a great insurance policy. Testing ensures that your product meets your quality standards and is ready for use in the market. This protects your customer from a poor user experience and you from bad PR and revenue loss.
For many product companies, QA remains a grey area. Maybe there are a few QA engineers onsite, thinly spread over a bunch of different projects. Maybe the developers double up and test as they code. Maybe they use a nearshore vendor that eats up the testing budget, or an offshore provider delivers a bug-ridden product. What is the solution for a company looking to strike a balance between quality, cost and great client experience?