Saturday, 28 January 2017

Testing_125 : Execution Process

In this article, We understand how the Test Cases Execution Process Goes in the Projects....

Process to Execute the Test Cases (Based on Sprint Release) :-


Testing Process starts after the Release notes and Requirement Documents...

Version 1.0 => In Ver 1.0, We created 150 Test Cases. Then Executed 50 Test Cases from which 30 TCS Passed and 20 TCS Failed. Then you reported Defects to the Developer. Developer separates defects based on Priority. He fixed the major (P-1) one first.
1) Project Name :-
XYZ Inc.
7) # of Test Cases Blocked :-

2) Version :-
1.0v
8) # of Test Cases not Executed :-
100
3) # of Test Cases :-
150
9) of Defects Fixed

4) # of Test Cases Executed :-
50
10) # of Defects Closed :-

5) # of Test Cases Passed :-
30
11) # of Defects Found (Based on Priority) :-
P-1 = 10
P-3 = 5
P-4 = 5
6) # of Test Cases Failed :-
20
12) # of Defects Reopened :-


Version 1.1v => In Ver  1.1v, Developer fixes all priority based defects and send them to Test Team. We perform Retesting from which 3 Defects Reopened.  After Retesting we continue the remaining test cases. We Executed another 50 TCS from which 25 Passed, 20 Failed and 5 Blocked. Then you Reported Defects to the Developer. Developer separates Defects based on priority. He fixes major (P-1, P-2) one first.
1) Project Name :-
XYZ Inc.
7) # of Test Cases Blocked :-
5
2) Version :-
1.1v
8) # of Test Cases not Executed :-
50
3) # of Test Cases (Remaining) :-
100
9) # of Defects Fixed :-
10
4) # of Test Cases Executed :-
50
10) # of Defects Closed :-
7
5) # of Test Cases Passed :-
25
11) # of Defects Found (In 1.1v) :-
P-1 = 8
P-2 = 6
P-4 = 6
6) # of Test Cases Failed :-
20
12) # of Defects Reopened :-
3

Version 1.2v => In Ver 1.2v, Developer fixes all Priority based Defects (P-1 = 8, P-2 = 6 from 1.1v, P-3 = 5 from 1.0v and 3 reopened) and send them to Test Team. We perform Retesting (all Defects Closed). After Retesting we continue the execution of remaining 50 Test Cases (along with 5 Blocked which are now Fixed) from which 50 Passed and 5 Failed. Then you Reported Defects to the Developer.
1) Project Name :-
XYZ Inc.
7) # of Test Cases Blocked :-

2) Version :-
1.2v
8) # of Test Cases not Executed :-

3) # of Test Cases (Remaining) :-
50
9) # of Defects Fixed :-
22
4) # of Test Cases Executed + 5 blocked :-
55
10) # of Defects Closed :-
22
5) # of Test Cases Passed :-
50
11) # of Defects Found (In 1.2v) :-
P-2 = 5
6) # of Test Cases Failed :-
5
12) # of Defects Reopened :-


Version 2.0v => After developing the 2.0v, Developer send Release notes and SRS for Testing Team and Also previous fixed 16 Defects. After reading Requirements we created 100 Test Cases for 2.0v. But before execution of the 2.0v we have to perform Retesting on fixed Defects and also Perform Regression Testing on Old Functionality for checking whether its fully integrated with new functionality or not.
1) Project Name :-
XYZ Inc.
7) # of Test Cases for Regression Testing :-
150 (Old Functionality)
2) Version :-
2.0v
8) # of Test Cases Passed :-
130
3) # of Test Cases (of 2.0v) :-
100
9) # of Test Cases Failed :-
20
4) # of Test Cases Executed :-
100
10) # of Defects Fixed (of old Ver) :-
16
5) # of Test Cases Passed :-
70
11) # of Defects Found (In 2.0v) :-
50
6) # of Test Cases Failed :-
30
12) # of Defects Reopened :-
3

...And the process will continue until the project completed and Deliver to Customer.

No comments:

Post a Comment