test automation

Test coverage is a strategy to help us spend scarce testing time on the right priorities. When things were tested last, how much automation coverage we have, how often the customers use the feature, and how critical the feature is to application are all factors to consider. Here are some ideas for keeping quality high when you're transitioning to continuous delivery.

In this culture of shorter time to market and release-ready sprints, it is vital for QA to keep pace by using test automation practices and tools. This article traces the shift from script-based testing with hard-coded data to automated frameworks, exploring the beginning of test automation and its evolution to where we are today—and possibly to where we will be.

If you're uncertain about where to focus your testing or what kind of testing you should be doing, look at what your users are telling you. Understanding the analytics of how your customers use your application can help you improve your test efforts. This article explores instances of how this data can inform user interface automation, compatibility testing, and web services tests.

Many automation tools have a mechanism for storing data used in their test scripts. Typically, the specifics of this mechanism is different across tools, making it difficult to use this data outside the tool itself. Using an external, reusable data source allows organizations to avoid the cost of migrating or duplicating existing data, thereby future-proofing their frameworks.