Testing_124 : Retesting and Regression Testing

After fixing the issues of 1.0v of application and completed coding of 2.0v. Developer sends 2.0v for testing.
So Tester will test 2.0v of application and retest the defects of 1.0v. For Checking the integration of the application 2.0v with 1.0v, tester have to test the whole application. For this situation we used automation testing tools.

Retesting and Regression Testing :-

What is Retesting ?

Retesting of the application to verify whether defects have been fixed or not.

What is Regression Testing ?

• It is Re-execution of some or all test cases of a testing activity for each build to verify that changes or fixes made have not introduced new errors.
• 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.
• Regression testing is one type of retest, where we can retest the application after bug fixes or any new functionality is added.

Release 2.0 execution process :-

Step 1 : After receiving release 2.0 from development team, as a QA we need to perform smoke testing.

Step 2 : Understand the release note documents and perform re-testing for the fixed defects (if any).

Step 3 : After Re-testing, the defect status should be updated in tracking tool and also prepare a retesting report and send to management.

Step 4 : As per the release note document based on new functionality, perform the functionality testing, by executing test cases.

Step 5 : After completion of new functionality testing, then perform regression testing based on old releases.

Retesting Template :-

Retesting Reporting Example :-

For Detail on Execution Process Click on link : Release wise Execution Process

Testing_123 : Status Report

Purpose :

• Part of Project Management.
• Monitoring and Managing the Project Deliverables.
• Part of SEI CMMI Level 2.

Types of Status Reports :

• Daily Status Reports
• Daily Defect Reports
• Weekly Status Reports
• Retesting Report
• Build Summary Report.

Here are the templates and example of each report.

Daily Status Report Template :

Example of Daily Status Report :

Daily Defect Report Template :

Example of Daily Defect Report :

Weekly Status Report :

Project Code :-	Fb-1234	Release :-	1.0v
Customer :-	XYZ Inc.	Week Ending :-	3/10/2016
Project Manager :-	Test Lead_1	Tester :-	Tester_1

1) High Level Summary :-

          Provide a high level test summary on test status. Summarize the project matrices here.

2) Major Accomplishments since Last Reporting Period :-

          List out major accomplishments since Last Reporting Period.

3) Item not Completed as Planned :-

          List any items that were planned in the past reporting period but, were not completed.

4) Project matrices :-

a) Major Project Deliverables :

Deliverable	% Complete	Actual End Date :-	Target End Date (If not complete)
Test Plan	100%	2/10/2016	N/A
Test Cases	67%	3/10/2016	10/10/2016
Test Scenarios	100%	2/10/2016	N/A

b) Defect Summary By Severity :

Defect	Severity	Current # of opened defects	# of Defects	# of Closed Defects	Total Defect Opened	Defect Closed
1-Critical
2-Major
3-Moderate
4-Minimal

c) Test Coverage :

Priority	Total # of Test Cases	Total Executed	# of Test Cases Passed	# of Test Cases Failed	# of Test Cases Blocked	# of Test Cases to be Executed
P-1
P-2
P-2
P-4

d) Effort Summary :

Activity	Planned	End Date	Balance

5) Risk And Issues :-

Serial No.	Description	Probability (1 to 5)	Impact (1 to 5)	Risk Exposure	Mitigation Plan

6) Items Planned for Next Reporting Period :-

          List all activities planned for next reporting period.

          Note : Weekly Status Report Handled By Test Lead / Dev Lead.