Profound
Uploaded by
12 SLIDES
121 VUES
120LIKES

Chap 7 - Test Execution

DESCRIPTION

Chap 7 - Test Execution

1 / 12

Télécharger la présentation

Chap 7 - Test Execution

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Test Execution

  2. What is Test Execution ? ● It's a process of executing an Application based on Test cases and observe the actual result(s) to evaluate the Application ● It's Dynamic testing as Application is executed ● PURPOSE:- ● Test Execution is carried out in order to collect the data by which the organizations can access the quality of the product under test ● The information obtained from this should be used for inprocess tracking to determine the need for corrective action during a project's appropriate test life cycle phase ● It helps to capture actual result 2

  3. Approach for Test Execution New title ●Following activities are involved in Test Execution Validate the test environment Selection of Test cases for execution Run Test Cases and observe Log Defects Retesting and Regresion Test Closure 3

  4. Validate the Test Environment ● When validating a test environment: Ensure availability of required Hardware, Software, operating system, Network configuration Deployment of correct build Build - Is a set of executable program handed over to Tester for purpose of Testing - Its a version of program which is still in Testing stage Availability and access to Test Data     ● Ensure that the test environment is mirror of your production environment as closely as possible 4

  5. Smoke / Sanity Testing ● Purpose is to check whether build received is supporting basic functionalities Also known as Build Acceptance Test Build is good enough to start actual Test Execution Subset of designed Test cases which cover basic functionality and cover breadth (end to end functionality) of the Application are selected Smoke testing terminology has come from Hardware industry If smoke test fails; build is rejected stopping further Test Execution      5

  6. Test Case Selection ●Selection of Test Cases for Execution depends on following criteria  Cycle 1 of execution  All planned Test Cases are selected for execution  Cycle 2 of execution  Select Test Cases based on cycle 1 results i.e. Module / functionality where more Defects are found  Critical functionality of the Application 6

  7. Run Test Cases ● Also known as actual Test EXecution Prioritize Test Cases Test Cases on critical functionalities are executed first Other Test cases will follow once critical functionalities are tested Also helps when there is insufficient time for Testing     ● Execute identified Test Cases Execute the Application i.e perform the steps as per Test Case Observe the response of the Application Record the response in Actual Result column Check whether Expected Result and Actual Result match? Pass or Fail Test Cases / Update “Status” column as Pass /Fail      ● Sometimes Test Case can not be executed completely i.e. till the last step due to presence of a defect; in case of such test case Status column is updated as “In- complete” 7

  8. Log Defects ●For each failed test case / test condition defect is logged ●Based on Defects found may have to increase the scope of testing / Test Cycles 8

  9. Retesting and Regression ● Retesting To check whether developer has given correc fix for the logged defect Test case which was failed due to presence of defect is re-executed once the Application build with defect fix is available After re-execution, Actual result is observed again    ● Regression To check whether unchanged part of the Application is working correctly and changed component has not impacted the already working functionality / unchanged part As defect fixes are given or Application functionalities get added as they get developed there is possibility of having impact of these on existing functionality which was working Previously Passed test cases are executed again    9

  10. Testing Principles ●Pesticide Paradox  Same Test Cases will no longer find any new defects if same test cases are executed again and again  Test cases need to be regularly reviewed and revised  Helps in exercising different test conditions to find more defects 10

  11. Challenges in Test Execution ●Build not available as per time schedule ●Poor build quality leads to more Test Cycles needed than planned as per Test Plan Impacting Test Schedule 11

  12. Test Closure ●Test Closure Report  Test Manager produces Test Closure report summarizing  Test coverage achieved  Any variance in actual vs planned as per Test Plan  Test Exit criteria MET / Not MET  Any known defects ●Ensure presence of all Test deliverables / artifacts in configuration management tool ●Planned deliverables are handed over to maintenance team for future reference 12

More Related