Using Javascript injection to create atomic tests can speed up testing, but one thing is for sure: running tests can be a slow process. It can get even slower as teams look to increase test coverage by testing across more operating systems and browser configurations. Yet, doing so will extend test execution time, which is the opposite of what teams are looking to accomplish.
The solution to this is parallel testing, aka running two or more tests at the same time. With parallel testing, teams are able to decrease the amount of time a test suite takes to run, increase coverage, and test continuously with more confidence.
In this exciting episode of Best Practices of Automated Testing, Nikolay Advolodkin, Solutions Architect, introduces test parallelization. One of the requirements to start is to have the Maven Surefire plugin, so be sure to have that handy. Nikolay walks you step-by-step through what is needed and introduces a new and important command to the BasePage class.
By the end, you will see production-ready code leveraging all the best practices that can be utilized immediately to help you achieve ultimate test automation results.
Stay tuned for the final video!
Don’t want to wait? Access all eight videos in this Best Practices for Automated Testing series.
