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.
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.
For healthcare providers, mobile apps present an incredible opportunity to impact the lives of patients. In addition to providing patients with secure access to their health records and direct mobile interaction with healthcare professionals, these mobile apps can be true lifesavers. Consider the London boy who saved his unconscious mother with help from Apple’s Touch ID and Siri. Continued innovation in this space can change the way people think about seeking diagnosis and treatment, accessing and managing their health records, and reporting emergency situations.
No one ever said that migrating a new platform was easy. In fact, the road to a successful platform migration is difficult and long—for some, a little too long. But in the words of the visionary modernist T.S. Eliot, “Only those who will risk going too far can possibly find out how far one can go.” Though it will be tough, it will be worth it.
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?
What happens when you can’t accurately measure the cost, effectiveness, and progress of a software testing project? A lot of less-than-ideal things. Projects can balloon in cost, creep in scope, fall in quality, or run on for what seems like forever. Without defined metrics attached to each QA project, they can get out of control -- and this scenario is a nightmare for both the product company and their team and the testing provider and their engineers.
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.
Short answer: yes, definitely. The Agile method is quickly becoming the preferred way of working at today’s most successful product companies. Agile teams are, by their nature, cross-functional. They’re composed of technical team members, such as developers, as well as non-technical folks, such as business analysts. Together, these teams have the combined knowledge and skill required to produce an exceptional product. They share their achievements and progress with each other, anticipate any potential roadblocks, and plan accordingly to help deliver a high-quality product.
One of the key challenges of working with an outsourced QA partner is aligning a new, offshore team with your product, procedures, and larger business objectives. Without the proper transfer of knowledge from the customer to the offshore team, engineers will be testing blindly. This leads to process slow-downs, inflated project budgets, and even lost contracts.