regression test code example

Example 1: what is regression testing

Regression testing is testing existing 
software applications to make sure that
a change or addition hasn’t broken any 
existing functionality. Its purpose is 
to catch bugs that may have been accidentally
introduced into a new build or release candidate, 
and to ensure that previously eradicated 
bugs continue to stay dead.

Example 2: how many test case in your regression

It depends on the project.
In my current project out of 1200 test cases 
in regression suite around %70 is automation.
We use 6 vm to perform parallelexecution it takes
3 hours to execute depends on the test data.

Example 3: regression test

Regression Test
To check if the new functionality works with the old ones.
Regression testing is testing existing 
software applications to make sure that
a change or addition hasn’t broken any 
existing functionality.
Regression also happens when there is a major bug fix.
Around 300 feature files and 700 scenarios. 
Regression tests are kicked off by Jenkins. 
Tests are executed on the Jenkins server (VM). 
The latest run took more than 5 hours. 
The maven command includes that tag name: 
mvn test -D cucumber.options =”--tags @Regression”. 
At the end of the execution, jenkins generates 
HTML report with detailed tests steps and screenshots

Example 4: how to create test plan for regression test

in Jira test plan is nothing but grouping tests
(and labeling them )so that they are regression,
smoke or both. All you need to do is create
a test plan name is Regression and add tests
to this test plan by linking those tests with
the test plan you have just created.
So question which scenario goes to regression:
we decide it together as a team, mostly
positive scenarios go to regression,
the ones that needs repeated execution,
retesting once a new build is added.

Example 5: regression suite

It depends on the project.
In my current project out of 800 test cases 
in regression suite around %90 is automation.
We use 10 vm to perform parallelexecution it takes
2 hours to execute depends on the test data.

Example 6: effective regression test

The regression tests should be wide and 
detailed enough to allow catching defects.
You can also eliminate duplicate test
cases, merge test cases and automated tests as feasible.