Intro 1 Plan

Slide 1: Test Planning QTP6FUND-STUDENT-01A

Slide 2: 2 Lesson Objectives Given a manual test case, a student will be able to:  Extract information that will be used to create a basic test script  Distinguish the types of data to use as sample test data  Identify two strategies for creating test data

Slide 3: 3 QuickTest Workflow Automated 1 2 3 Plan Create Enhance Gather relevant test Create the basic Enhance the basic information test: test: 2.1 Record user - Add automatic actions verification with 2.2 Verify checkpoints successful - Create a data- playback driven test - Create modular test

Slide 4: 4 Planning Review: Document Business Process Properties Obtain necessary information to create tests:  User actions  Expected results of each user action  Alternate paths and optional screens  Valid data to use  Possible exceptions

Slide 5: 5 Planning Step by Step: Complete for Each Recording 1. Document business process properties 2. Determine the visual cues to verify  That transaction completed successfully  To meet other specific test requirements 3. Determine which data to use  Master Data  Transactional Data (or Input Data) 4. Investigate possible exceptions  Optional pop up messages or screens  Configuration not complete/known problems

Slide 6: 6 Determine Sample Data to Use There are three types of data you may use as test data:  Master data  Input data  Prepared data in the database

Slide 7: 7 Obtain Master Data  Fixed data about products or users, deposited in the database or application Fixed list of cities in the Flight Application  Can be imported from a database database in QuickTest or imported from a spreadsheet (1-10) Import from a database to QT directly Import from a file

Slide 8: 8 Create Input Data  Editable data used to complete a business transaction  Consist of valid and invalid values ( 1-10)

Slide 9: 9 Prepared Data  Data that is created and consumed during a test execution  Data is added in the database prior to test execution Test Objective: Delete Flight Transaction Testing Goal: Check that all flight orders for input name entered are deleted from the database. Test case Name: jojo Password: bean Database: Transaction_1 Database Admin: Sara O’Reilly Functional Expert: James Scurry Initial Requirements: Make sure Transaction_1 contains records to delete.

Slide 10: 10 Prepare for Automated Testing  Check that the application under test is stable and ready for testing  Go through the test case steps on the application to verify that all steps are listed in the correct order  Check that the provided data to use is valid for recording the basic test  Check that the testing environment standards (test directory, naming conventions, test standards) are adhered to  Check that QuickTest and the add-ins, if any, are installed and running without errors

Slide 11: 11 Lab Exercise