Don’t be the bottleneck.
Testing is rarely a one-and-done exercise. The rise of agile and DevOps modes of working requires continuous releases—and continuous testing. To keep up with the pace of DevOps, you have to streamline testing. Which means automating and parallelizing as much of your testing as possible—because time to market is critical for the business. But you also need to ensure high quality, great performance, and an exceptional UX, despite the ever-shrinking window to get an app out there.
In many use cases, testing is so continuous that it’s becoming synonymous with monitoring. You can perform tests continuously on a running application in production to monitor its performance and functionality, not just to test it prior to production. For example, to provide geographically distributed users with a first-rate UX, a telecommunications company might continuously run tests on a mobile application in production from different locations to ensure that UX elements, including reliable network and application responsiveness, are performing at the highest levels.
To make this happen, testing teams need to:
- Automate as much of the test process as possible—including not just test execution but test creation and test-result analysis.
- Easily—and even automatically—modify these tests as new application releases evolve.
- Parallelize as many of the automated tests as possible to squeeze testing into the shortest possible time frame.
- Run these types of tests continuously and turn them into a form of continuous monitoring.
- Test across different OS and browser combinations.