Analysis on Execution plan

Daily Status Report update.

1.       Who are all stakeholders
2.       Which stakeholder needs what data
3.       Collect the information from the all stakeholder interested on
4.       Create a template and share with the stakeholders to get the signoff.
5.       If there is a need to improve or change in the reporting style, need a confirmation from the Business/TCS Managers.

Daily status report : Information Interested on : Ideal Scenario: All test cases/scripts are passed and all defects to be closed before the EOD of test execution cycle.
1.       How much work is completed/how much is pending
2.       Whether we can complete the task in time
3.       What is the percentage of the pass test scripts when compared to the base line plan
4.       Execution plan vs Actual Plan ie Baseline plan VS Forecast plan(have we complete the execution as per the plan, else how much is pending + how much needs to be completed tomorrow= is our target to complete)
5.       Execution plan VS Passed execution Actual
6.       Note: Rework is not interested by the client but as consultancy services we need to take care of this effort (Retest effort, rework effort, number of times executing the failed test scripts,
7.       What is the efficiency of test scripts/application development
8.       Overall/Cumulative test execution summary report: Number of test cases executed: Passed + Failed, number of descoped, No-run and Not completed
9.       Detailed information on each application
10.   Detailed information on each application/each module wise
11.   Overall Execution percentage (passed +Failed Test Scripts), Overall Completion percentage(passed Test Scripts)
12.  
13.  

Defect Reporting:
Always managers/Stakeholders are interested to see the product with defect free.

1.       Application vs Defects Severity
2.       Application vs Defects Status
3.       Application vs Defects aging
4.       Defects Severity vs Defects Status
5.       Application vs open defects (Apart from Closed defects, rest of all the status will be moved to open defects).

Analysis on Test Steps for Execution plan.

1. Count the number of Clicks, Enters and validation/verify
2. Count the number of test Steps
3. Number of test cases, calculate the risk of the module
4.

Analysis on Execution plan
1.      What is the percentage of the execution is passed
2.      What is the percentage of the execution can be achieved
3.      What is the forecast plan of the work to be achieved to complete the daily target.
4.      What is the execution percentage (Passed + Failed)
5.      What is the completion percentage(Passed)
6.      What is Descoped test scripts: Features not to be tested, Out of scope features
7.      What is blocked test scripts: Due to defect, due to dependency on the external application, due to the data dependency, due to time dependency
8.      What is not completed test scripts: which may be able to complete or continue the execution due to data security.(Data protection act).

Ultra Testing: Business end users who is going to consume the application can be validated in any phase of the testing.
To find the defects at early stages and track those defects in the Test management/Defect tracking system for further analysis between the business Analysers and Designers.



Comments

Popular posts from this blog

Terminal Emulation – QTP Automation Testing

HP QC SQL Queries

HP ALM-QC Daily report extraction