QASource Blog

Going to market with a perfectly functioning product is a great way to attract customers and cement relationships with them. And for many software product or service companies, that’s their goal. But many others are resistant to the idea of allocating budget toward the thorough QA testing required to achieve that goal. Their reasons range from “Our developers are smart, they can test their own code” to “We don’t know if QA will provide good ROI.” But, as the recent spike in data breaches and hacking has shown, an ounce of prevention is worth a pound of cure.

It’s widely known that thorough API testing results in a high-quality final product. One question that lingers for many product companies, however, has to do with timing -- when should API testing be introduced? For many top QA teams, the answer aligns with the increasingly popular Agile methodology. For a strong, robust product, API testing is best performed in parallel with development.

Recently, QASource, in conjunction with Sauce Labs, presented "Measuring Your Way to Successful Automation," a webinar during which QASource took a poll of its attendees about their automation metrics. Using the results of this poll, QASource put together an infographic that highlights the many ways metrics can benefit QA teams and testing projects.

Today, it seems like we don't go a week without hearing about a high-profile hack or breach of customer data. As customers, we spread our information across a huge variety of applications, and we trust that no ill will come of it. The truth is, however, that we’re more vulnerable than ever, and the risk of a hack is made clearer to us everyday. We rationalize the situation, thinking, “Well, they must have people safeguarding my information, right?” Right — for the most part.

If there’s one thing startups know all too well, it’s that speed to market is crucial to a company’s success. However, customers today are increasingly unwilling to put up with faulty products and buggy apps, so developers cannot afford not to test. So how can an organization choose which to invest in, speed or quality?

QASource's Mobile QA Group analyzed market statistics from various sources: Statista, IDC, comScore, and Gartner, and identified suggestions in this quarter's Mobicast expert series.

Responsive applications are growing in the market which has increased the requirement for testing apps. We have tailored our tool evaluation to support the automation of applications on multiple platforms and their responsiveness.

One of the main challenges startups face is accomplishing critical functions when there isn't enough money, resources or time to staff properly. While it's inevitable that members of a startup wear some different hats, there comes a point when it's unsustainable to continue doing this at every level if the organization wants to grow. It makes more sense to outsource. But which functions does it make sense to contract out? Let's look at 5 areas.

Outsourcing QA has become a popular option for many organizations, particularly for startups, but there is still much confusion around how effective and efficient it can be. Let’s dispel 7 of these common myths about outsourcing QA for startups!