Regression testing in Agile Methodology

Regression testing efficiently checks the previous functionality along with the working in relation to the current changes and the working along with that in regression testing testers have to see weather no new bugs are introduced in the process of changements. Since there are abundant dependency in the new added functionalities if become compulsory to verify that new code is compatible with old code and the unmodified code is not affected. Since there are many build cycles so regression testing becomes frequent.

For effective testing in agile development it is important that a regression suit is built from the initial stage of development and continue as the sprints add up. A few things to be kept in mind before building regression test plan

1. Identify test case that should be executed

2. Identify the improvements that must be included in test-cases

3. Identify the execution time

4. Outlining the requirements for automating regression test plan

5. Analyzing the outcome of regression testing

Along with these check

list even the performance testing should be taken into account to ensure that the performance is not negatively affected due to changes implemented on code.

In Agile environment, Regression is tested under two categories

1. Sprint level Regression: In this the testing is mainly focused  on the new implemented functionalities since the previous release.

2. End to End Testing: In this testing the main focused areas are from the start point to the end point irrespective of sprints

Taking build Scenarios in account it is hard to perform regression in short time span. Adding the Regression suits to the continuous flow also helps as this prevents the developers to check in new cose before automatically evaluating the proper functioning of existing functionalities

Following approaches can be adopted for the Regression testing:

1. The Traditional Testing Approach

2. Delayed Week Approach

3. Delayed Sprint Approach