Regression Testing definitions with example

Regrestion Testing Definition:

Def1:

• Regression testing is achieved after the bug fixed, means testing the operation whether the fixed defect is affecting remaining functionality of the application or not. 
• Usually in regression testing bug fixed module is tested. 
• During regression testing tester always check the entire system whether the fixed bug make any adverse affect in the existing system or not. 
• Regression testing is the re-testing of features to make safe that features working earlier are still working fine as desired. 

Def2:

• When a bug is amend (fixed) by the developer squad, testing the other features of the applications which could be affected by the bug fix is known as regression testing. 
• 
  
• Regression testing will be conducted after any bug amends (fixed) or any functionality changed. 

Def3:

• Regression Testing is type of testing carried out to ensure that changes made in the fixes or any enhancement changes are not impacting the previously working functionality. 
• It is executed after enhancement or defect fixes in the software or its environment. 
• It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. 
• It is a verification method & mainly done in system testing but it applicable to all levels of software testing (Unit testing, Integration testing, System testing and Acceptance testing.) 
• Good Regression tester need to aware of what all features to be focus on changes in the software application. “The main aim of regression testing to make sure that changed component is not impacting the unchanged part of the component”. 

Def4:

• Regression testing is always done to verify that modified code does not break existing testing functionality, and works within the requirements of the system. 
• 
  
• There are mostly two strategies to regression testing, 
• to run all tests and 
• always run a subset of tests based on a test case prioritization technique. 

Def5:

• Regression testing at a particular phase of the discharge cycle (Alpha, Beta) establishes the exact state of the product by liberal clear picture of issues existing in the product. It helps management adjust the discharge dates for the product accordingly. 

Def6:

Checking that fixed bug do not affect the other sections of the modules by checking the functionality and other scenarios of testing on different modules and within the similar module in which bug is fixed is known as regression testing.

Def7:

Regression-testing

Every time after making changing in the existing working code, a suite of test case have to executed to ensure that changes are not breaking working features and not introduced any bugs in the software.

It is essential to prepare such test suite & executed on every newer version of software.

Also to automate the regression testing this test suite will help to create a automated testing script.

Def8:

• In the Software regression testing, tester has to do only the execution of previously executed test cases & compare the result with previously test execution result. If there is not conflict between results then we can say that the regression testing is passed. 
• In this type of testing new test cases are not created but previously created test suite is executed to find regression defects. 
• Regression testing is done in two situations.. 
• One is after fixing the bug and second one is if a new change request will come from client.. 
• Here we have to verify whether already existing functionality can getting defects ... 

Def9:

Regression testing is re-execution of some subset of test cases that have already been conducted to ensure that changes have not propagated any unintended funcationality. Regression test pack contains following class of test cases -

• representative test cases that will exercise all major functions of system under test. 
• sample tests that exercises the software functions that are likely to be affected by change. 
• tests that exercises the software functionality that have been changed. 

This process should be defined step by step

1.tester test the application and raise the defect

2.developer agree s the defect and change the code ( i.e noting but a bugfix)

3.after this stage the same application come s to tester side to test that one again is their any new defects are ariseing for this code change this noting but a regression testing

Def10:

Regression test: A test that was written when a bug was fixed. It ensure that this specific bug will not occur again. The full name is "non-regression test".

The selective retesting of a software system that has been modified to ensure that any bugs have been fixed and that no other previously working functions have failed as a result of the reparations and that newly added features have not created problems with previous versions of the software.

Also referred to as verification testing, regression testing is initiated after a programmer has attempted to fix a recognized problem or has added source code to a program that may have inadvertently introduced errors.

It is a quality control measure to ensure that the newly modified code still complies with its specified requirements and that unmodified code has not been affected by the maintenance activity.

Def11:

Regression Testing - Testing the application after a change in a module or part of the application for testing that is the code change will affect rest of the application.

Def12:

Regression means retesting the unchanged parts of the application. Test cases are re-executed in order to check whether previous functionality of application is working fine and new changes have not introduced any new bugs. This test can be performed on a new build when there is significant change in original functionality or even a single bug fix.

This is the method of verification. Verifying that the bugs are fixed and the newly added features have not created in problem in previous working version of software.

Testers perform functional testing when new build is available for verification.

The intend of this test is to verify the changes made in the existing functionality and newly added functionality.

When this test is done tester should verify if the existing functionality is working as expected and new changes have not introduced any defect in functionality that was working before this change. Regression test should be the part of release cycle and must be considered in test estimation. Regression testing is usually performed after verification of changes or new functionality. But this is not the case always.

For the release taking months to complete, regression tests must be incorporated in the daily test cycle. For weekly releases regression tests can be performed when functional testing is

Note: Do not confuse regression testing with re-testing because in re-testing tester only test whether the fixed bug is getting fixed or not by re-testing it.

On the other hand in regression testing tester only tests that fixed bug do not affect the other parts of the effective modules and do not bother and take less stress about whether the bug is fixed or not.

Regression Testing Meaning is given below: Regression Meaning is relapse or reverting so meaning of regression testing is “relapse testing” means it is done in two situations or you can shortly say in two conditions.
First condition is after fixing the bug by checking and ensuring that fixed bug does not affect the other parts and functions of the modules.
Second condition deals with change in requirements means when client change the previously done requirements than tester have to test that changing requirements do not affect the other requirements of the application which are done means completed.
Example of regression testing is explain below

Considering example there are three modules in the project one is admin module other is PIM and last one is employment module and suppose bug occurs in the admin module like on admin module user is not always capable to login so testing team sends the bug detail to the developer team and when the developer team fixes the bug, than the testing team see that fixed bug does not affect the remaining functionality of the modules (admin, PIM, employment) and also the functionality of the same module (admin), than this is the regression testing.

It is executed when any new build comes to QA, which has bug fixes in it or during release cycles (Alpha, Beta or GA) to always originate the endurance of product.

QA team performs the fixed bugs regression to see if the bugs are really fixed in the build and fix of any bug has not caused any working areas to break or re-opened already fixed bugs in that area.

During release cycles, QA team performs the regression testing in which tense test cases are executed for the earlier working legacy features to confirm that features are still working elegant and no new issue has been incorporated in them with the development of new areas.
Significant Approach of Regression Testing

Regression Testing Approach is given below:

• As you know there are two approaches for integration testing like top down integration and bottom up integration similarly we have the two approaches for regression testing. 
• First approach is doing the regression testing when bug is fixed. 
• Second approach is doing regression testing when change in requirements of the client. 

Build verification Testing

Build verification Testing[BVT]:

• Build verification testing is also called as smoke testing. 
• Build verification is a set of tests run on new build to verify that whether the build is testable for further testing. 
• It is done priorly by test team before build pass to testing team for further testing. 
• This testing is mainly done for build validation and build acceptance. 
• This test contains pre-defined Test Cases which focus on the core functionality of software application to make sure that build is stable or not to start with actual testing.

Test Cases For Date field

Test Cases For Date Field:

They may be many cases if the text box is editable or not purpose of the date field used etc .

Test Cases if the Date field is not text box:

1. Ensure that calendar window is displayed and active when the calendar is invoked by pressing the calendar icon. (Once we faced an issue the calendar window is in minimized state when we invoked the calendar.) 
2. Ensure that calendar date is defaulted to system date 
3. Ensure that when a date is selected in the calendar (double click or some other method) the selected date is displayed in the text box and calender should be disappered from there. 
4. Check for the format as per requirement i.e.mm-dd-yy 
5. Check for the list of years by click on down arrow displayed years of selected year before and after 10 years 
6. Check for the list of 12 months by click on month down arrow 
7. Check for the clear of date by click on clear text link in the calender what before selected 
8. Check for the month changed to previous month by click on Prev text link 
9. check for the month changed to after months by click on next text link 
10. check for the today date highlighted or not by click on today text link 

Test Cases if the Date field is editable text box:

• enter the valid date ,month, year 
• enter the invalid blank space and valid month invalid blanck space 
• enter the invalid blank space and invalid blank space and invalid blank space 
• enter the zeros in date and invalid blank space and zeros in year. 
• enter alphabetic,alphanumeric data in the field. 
• enter special characters. 
• enter decimal point. 
• Enter valid date,invalid blank space in month,invalid blank space in year 
• Enter invalid date,valid month and invalid blank space in year. 
• Enter invalid date,invalid blank space in month and valid year. 
• enter the invalid date and valid month and valid year 
• enter the valid date and valid month and invalid year 
• enter the valid date and invalid month and valid year 
• enter the valid date and invalid month and invalid year 
• enter the invalid date and invalid month and invalid year 
• enter the invalid date and valid month and invalid year 
• Leave blank spaces for all the fields. 
• Check whether the year entered is leap or ordinary year. 
• For ordinary year the max limit of number in day field in the month Feb should be 31. 
• For leap year the max limit of number in day field in the month Feb should be 29. 
• With respect to the corresponding alternate months corresponding numbers in day field i.e 30/31 should be accepted. 
• Enter the date below/beyond the range, i.e 32 or 0 etc. 
• Enter the month below/beyond the range,i.e 13 or 0... 
• Enter zero before the single digit number in date/month. 
• Check without entering zero before the single digit. 
• Enter valid date,valid month and only last two digits of year. 
• Enter any alphabets in these fields. 
• Enter special characters and check. 
• Enter zeroes in all the fields. 
• Check whether the control passes on to the month field after entering date. 
• Also check whether the control passes to year field after entering date and month. 
• Check the format of date,month and year. 
• Check whether it is accepting date in date field,month in month field and year in corresponding field. 
• should not accept 000000 as a date.