Challenges while executing the test cases for large project

    1. Defects are in Closed status but the test scripts in either Not Completed or Failed or Blocked Status. Based on the conversation with Program Director regarding this, we have followed this method to get more productivity
      1. Identify the defects which are closed and find the linked test scripts. Moved those to No Run status by updating the comment section in the test plan>>Run suite.
    2. Identified the test scripts which are in the Not completed status for more than two or three days

      1. Check the test steps status and if there is an update on those ie more than 50% of the test steps has been executed in that case need to check with the concerned tester for further update.

      2. Else move the test script to no run status.

      3. Possibility of no action on the test scripts due to concern tester is moved out of the portfolio or left the company or not feeling well or any emergency
Defect is in "closed" status, so the test script is moved to "No Run" status to re-run.

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

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

Post a Comment

Popular posts from this blog

Terminal Emulation – QTP Automation Testing

Terminal Emulation – QTP Automation Testing Topics to be covered 1. Basic understanding of the terminal emulator 2. Emulation terminology 3. Configuring the QTP to work with TE application 4. Automation testing methodology Basics of Emulator • Duplicates the functions of one system using a different system, so that second system behaves like a first system. • Computer simulation Example: AS400 and mainframes is a dark green color screen AS400 is introduced in the year of 1988 by IBM, formally renamed as IBM iseries but still called as AS400 is mid range server for the small business and large enterprises. It will work good within distributed network and web based applications for execution it uses OS400 ie operating systems. TN5250 Terminal emulation protocol IBM owned iseries access by TN5250 with WRQ’s reflection, humming bird’s host explorer, Cybele software’s Z scope Express 5250. AS400 is also a Mainframe which are used for large organizations, for critical applic
Read more

HP QC SQL Queries

Test-lab: SELECT CY_CYCLE AS "Test Set",        TS_NAME AS "Test Script Name",        TC_ACTUAL_TESTER AS "Tester",        TC_STATUS AS "Execution Status",        LEFT(CONVERT(VARCHAR,TC_EXEC_DATE,20),10)  AS "Execution Date" FROM TEST, TESTCYCL, CYCLE WHERE CY_CYCLE_ID = TC_CYCLE_ID AND   TS_TEST_ID = TC_TEST_ID AND CY_CYCLE_ID IN (cycleid) Test-Summary: SELECT CY_CYCLE,        TC_STATUS,        COUNT(TS_NAME) FROM TEST, TESTCYCL, CYCLE WHERE CY_CYCLE_ID = TC_CYCLE_ID AND   TS_TEST_ID = TC_TEST_ID AND CY_CYCLE_ID IN (cycleid) GROUP BY CY_CYCLE, TC_STATUS ORDER BY CY_CYCLE, TC_STATUS Run-rate: SELECT CY_CYCLE,        TC_ACTUAL_TESTER,        TC_STATUS,        LEFT(CONVERT(VARCHAR,TC_EXEC_DATE,20),10),        COUNT(TS_NAME) FROM TEST, TESTCYCL, CYCLE WHERE CY_CYCLE_ID = TC_CYCLE_ID AND   TS_TEST_ID = TC_TEST_ID AND CY_CYCLE_ID IN (cycleid) GROUP BY CY_CYCLE, TC_ACTUAL_TESTER, TC_STATUS, TC_EXEC_
Read more

HP ALM-QC Daily report extraction

SIT Test Lab will extract the Test Set, test case name, executed on, Executed by and it status. SELECT CY_CYCLE AS "Test Set",        TS_NAME AS "Test Script Name",        TC_ACTUAL_TESTER AS "Tester",        TC_STATUS AS "Execution Status",        LEFT(CONVERT(VARCHAR,TC_EXEC_DATE,20),10)  AS "Execution Date" FROM TEST, TESTCYCL, CYCLE WHERE CY_CYCLE_ID = TC_CYCLE_ID AND   TS_TEST_ID = TC_TEST_ID AND CY_CYCLE_ID IN (Cycleids) High level summary of the metrics SELECT CY_CYCLE,        TC_STATUS,        COUNT(TS_NAME) FROM TEST, TESTCYCL, CYCLE WHERE CY_CYCLE_ID = TC_CYCLE_ID AND   TS_TEST_ID = TC_TEST_ID AND CY_CYCLE_ID IN (cycleids) GROUP BY CY_CYCLE, TC_STATUS ORDER BY CY_CYCLE, TC_STATUS SIT Execution Rate/Run Rate SELECT CY_CYCLE,        TC_ACTUAL_TESTER,        TC_STATUS,        LEFT(CONVERT(VARCHAR,TC_EXEC_DATE,20),10),        COUNT(TS_NAME) FROM TEST, TESTCYCL, CYCLE WHERE CY_CYCLE_ID = TC_CYCLE_ID
Read more