The document discusses test planning for automated testing using QuickTest. It provides guidance on extracting necessary information from test cases, distinguishing different types of test data, and identifying strategies for creating test data. The key steps are to: 1. Gather relevant test information such as user actions, expected results, and valid data. 2. Determine the types of data needed - master, input, or prepared data - and strategies for obtaining them. 3. Prepare for automated testing by verifying the application and test case steps before recording tests.

1. Test Planning QTP6FUND-STUDENT-01A

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

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

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

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

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

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

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

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. 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. Test case

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

11. Lab Exercise