Test Planning Guide Summary: The purpose of this document is to define and document requirements in order to create and execute a test plan. Process: 1. Follow the guideline for each of the document below: a. Requirement Traceability Matrix b. Process Flow c. Process Procedure d. Wireframe/Site Map (Optional) e. Document Versioning 2. Execute the test cases. 3. Provide documentation set to Project Manager. 4. SQA will conduct usability testing based on the documentation provided in step 3. Benefits: Project Manager can utilize this documentation to track that all business requirements are properly implemented and tested. Increase testing efficiency from the ability to prioritize testing efforts in the most important functional areas of the application. Assist Project Manager and developer to validate the software before the Final Acceptance deliverable is packaged. Assist the development team to articulate the project manager perspective on the complex areas of application during the development task. This will help the tester to understand the application better resulting in a more through test. Easy maintenance of test scripts for future web application testing submittals. Requirements Traceability Matrix Create the matrix to trace and map functional requirements of test parameters required to meet expected business deliverables and confirm the test coverage. Requirement matrix parameters: Reg ID: Each requirement needs to be uniquely numbered with Req ID (e.g., R_01_01) for traceability. Sub Process: The process flow number. Requirement: Description of the capability of the application to meet the business needs Data Source: Reference of the input data. Dependency: Requirement that needs to be executed before executing the current requirement. Usage Frequency: how often a function or feature is used in scale of 1-3 below 1: function in application that users will always come in contact with. 2: function in application that frequently will be used. 1
3: function in application that occasionally used. Impact: How critical this functionality is to the application; rate in High (1), Medium (2), or Low (3) Releases: Specific application version number and stage of the application (e.g. Beta and Final). Test Case ID: provide the test case ID link after test cases are developed. Assumption: Precondition of the requirement. NOTE: For future release make sure to use the same traceability matrix and continue to add new requirements. Please update the document versioning. Req ID L_1.1 S-1 L_1.2 S-1 L_1.3 S-1 P_1.1 S-1 P_1.2 S-1 Below is one example showing a functional requirements table: Sub- Process Requirement "My Tasks" will display orders that require the salesperson's attention. Left-clicking on any order will direct the user to the order's Order Summary Page. When the salesperson has acted on the order, it will no longer be displayed in the "My Tasks" grid. will display all customers assigned to the salesperson as identified in the A- Lead file as well as favorites. To add customers to the grid, search for a company name. in the search box below the grid. Relevant results will display as the user is entering a company name. Left-click on the "Add" button to add the customer to the "My Customers" grid. The grid will refresh to display newly added customer. Project sections can be expanded or collapsed by clicking on the caret (sector, research area, and program titles). Order Line Item Status Definitions: "Funded" projects are items that the customer is currently committed to (contract currently exists in SAP). Data Source ( Execution Data Requirement) Order table. Contract table Dependency Order Creation component Usage Frequency Impact Releases Test Case ID Assumption 1 1 TS1_AP- 1_OM_PortfolioPage Sales person accesses via Member Center 2
SAP Pricing Portf_UI Process Flow Create a Process Flow diagram to illustrate the business process flow in a sequence of actions that represent business use cases to elaborate the requirement. The process flow number will be utilized in the Sub Process number in Requirement Traceability Matrix. S-1 1. Create new order Pricing Portfolio Sales Person Pricing Portal Create new order New Order Contract Order Management S-2 [Test] [Test] 3
Process Procedure 1. Test Environment Provide description or list of hardware and software where testing will be performed. E.g.: Microsoft office is recommended to be installed to convert the output data into csv file. Windows 7 or 8 or 10 operating system - 64bit is required to run the system. 2. Test Exclusion List the functionalities or features that are excluded in testing. E.g.: The data loader only work at certain function. The language translation has not fully developed in the administration functions. 3. Test Case Provide test cases and scenarios for testing the flow of the web application. Each script needs to provide the following information: Req ID: Requirement ID from Traceability Matrix. Test Script ID: A unique ID used to identify the traceability test case to the requirement. Test Scripts Description: Explain the objective and scope of the test case. Step Name: Name the step with number in sequence. Step Description: Detail the exact steps that a tester must follow to complete the step. Expected Results: Define the corresponding expected result for each test step. Status: Meeting the expected results will lead to a pass otherwise a fail. Comment: provide comment or additional note if needed. Req ID Test Script ID Test Scripts Description TS1_AP- Create new order: 1_OM_PortfolioPage role: quote approver - werwt08 Dev url: http://abcded01/ TS2_AP- 1_OM_CreateOrder Create new order: role: Restricted Editor werwt08 Dev url: http://abcdef01/ Step Name Step1: Step 2: Step 3: Step 4: Step1: Step 2: 4 Step Description Expected Results Status Comment Log into Pricing "My Tasks" and "My Portal. Customers grid" are displayed Navigate to My Customers grid Click on "Create Order for Customer" icon Verify the content of portfolio page Each customer line will have a "Create New Order for Customer" icon. Portfolio page will be displayed. The following items will be displayed: 1. Order Summary 2. Portfolio Funding 3. My Metrics 4. My Nuclear Metrics tables 5. Full portfolio list of Non-Nuclear Supplemental projects.
Step 3: Step 4: Step 5: Wireframe/Site Map (Optional) Visual guide that represents the skeletal framework of the web application. While this map is optional, it is highly recommended for complete software documentation of the web application. Document Versioning Version: The version of the requirement. Date: The date of new update deliverable. Updates: Short description of the update. Owner: Person who prepared the deliverables of the update. Version Date Updates Owner May 2, 2016 Created Business requirement Document James Dean 5
1.1 June 20, 2016 1.2 July 1, 2017 Added assumption that there shall be now new pricing Altered pricing requirement for member with subscription Anne K Anne K 6