Unit Regression Testing (URT)

Here, we are going to test only the changes.

In Build B01, a bug is found and a report is sent to the developer. The developer fixes the bug and also sends along some new features developed in the 2^nd build B02. The TE tests only if the bug is fixed. 

For ex, 

When developer gives the above application for testing in the 1^st build – the TE finds that clicking on the submit button goes to a blank page – this is a bug and is sent to the developer for defect fixing – when the new build comes in along with the defect fixes – the TE tests only the submit button. Here we are not going to test the other features of the 1^st build and move to test the new features sent in the 2^nd build. We are sure that fixing the submit button is not going to affect other features – so we test only the fixed defect.

Testing only the modified features is called Unit Regression Testing.When developer gives the above application for testing in the 1^st build – the TE finds that clicking on the submit button goes to a blank page – this is a bug and is sent to the developer for defect fixing – when the new build comes in along with the defect fixes – the TE tests only the submit button. Here we are not going to test the other features of the 1^st build and move to test the new features sent in the 2^nd build. We are sure that fixing the submit button is not going to affect other features – so we test only the fixed defect.

Testing only the modified features is called Unit Regression Testing. 

Let us consider another example, 

For the above application, in the 1^st build – the developers develop a “search” field which accepts 1-20 characters. The TE test the search field using test case design techniques.

Now, the customer makes some changes in the requirements and requests that the “search” field be able to accept 1-40 characters. The TE tests only the search field to see if it accepts 1-40 characters and doesn’t test for any other feature of the 1^st build.