From the course: Software Testing Foundations: Continuous Testing and DevOps

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Order of test execution

Order of test execution - Jenkins Tutorial

From the course: Software Testing Foundations: Continuous Testing and DevOps

Start my 1-month free trial

Order of test execution

- [Instructor] Once you're ready to start running your tests in a continuous integration solution, it's time to consider the order of execution. I find it's ideal to run tests in this order. Unit tests first, integration tests second, and workflow tests last. The reason that I think tests need to be run in this order is they start out simple, and then increase in complexity with each new category. This way, if something breaks at a basic level, you don't have to waste any time testing more complex functions afterwards. If something's wrong with the application at a basic level, for example, if a function isn't returning the output it should, you want to know about that first and halt further test execution. If there are multiple functions that refuse to work in concert despite working well alone, or if there are services that aren't reachable, or if there are REST API's that are no longer compatible with the way your…

Contents