Regression Test 101 - 2 - Define Test Target

This is one topic in the regression test 101 series. In this series, I will cover the following topics:

• Selenium Introduction
• Test Target
• Test Design
• Parrallel Execution
• Test Information collection & Visualization
• Challenges

Today’s topic is Regression Test Target.

According to Test Pyramid¹, we should have fewer tests in high-level like UI. So it’s not recommended to add too many UI tests.

Smoke Test

The first step might be to add some “Smoke Test”. The smoke test is a set of minimun test cases which covers the basic functionality of the appliation. It will not go to deep into the application functionalites.

Smoke tests usually run fast(keep it less than 10 minutes), it can be triggered for each commit.

Full Regression Test.

If the smoke tests are not enough, the next step might be adding more detailed regression tests. UI test usually run slow, it is not recommended to run for every commit. Other than triggerred every commit, it can be triggered periodically, such as daily, or every n hours.

The regression tests should be focusing on the functionality other than page layout, otherwise, the test can become very unstable and difficult to maintain.