Acceptance Test Plan and Cases (ATPC)

Transcription

1 Acceptance Test Plan and Cases (ATPC) LADOT Scanning Team No: 8 Anirudh Govil: Project Manager / Life Cycle Planner Aditya Kumar: Feasibility Analyst / Project Manager Corey Painter: IIV & V / Shaper Jeffrey Colvin: Prototyper / Software Architect Niraj Brahmkhatri: Operational Concept Engineer / Requirements Engineer Nisheeth Joshi: Software Architect / Life Cycle Planner 12/03/2011

2 Version History Date Author Version Changes made Rationale 10/24/11 NJ 1.0 Completed all the Sections Initial draft for use with LADOT Scanning 10/31/11 NJ 1.1 Completed all the Sections Made correction as per the bugs marked by den student 11/21/11 NJ 2.0 Completed all the section Made changes after meeting the developer and looking at the system 12/03/11 NJ 2.1 Completed all the section Fixed bug marked by DEN student ii

3 Table of Contents TEST PLAN AND CASES (TPC)... I VERSION HISTORY... II TABLE OF CONTENTS... III TABLE OF TABLES... IV TABLE OF FIGURES... V 1. Introduction Test Strategy and Preparation Hardware preparation Software preparation Other pre-test preparations Requirements Traceability Test Identification Test Identifier Test Identifier Resources and schedule Resources Staffing and Training Needs Schedule iii

4 Table of Tables Table 1: TC-01 Error checking/validation on the work order code... 8 Table 2: TC-02 User Log in... 9 Table 3: TC-03 User Log out Table 4: TC-04 Valid Variation code Table 5: TC-05 Valid Locating code Table 6: TC-06 Log issue report Table 7: TC-07 Values input at the front end must be entered automatically at the backend field.13 ATPC_TRR_F11a_T08_V2.1 iv Version Date: 12/03/2011

5 Table of Figures Figure 1: <Figure Title>... ATPC_TRR_F11a_T08_V2.1 v Version Date: 12/03/2011

6 1. Introduction This Acceptance Test Plan and Cases (ATPC) document describes the testing procedures for the LADOT Scanning in the University of Southern California s CSCI 577a. The LADOT Scanning system involves many crucial documents and information, so proper operation is mandatory. With limited features on the system, this APTC include test cases for each operation concept from the SSRD and SSAD. The scope of the testing is to ensure that all the functionality that will be implemented on the laptop is working properly. Since the project involves many critical data of the field employee, proper validation procedure need to be established. The focus of the test is given on worker performing job in the field and their information is stored in a laptop placed on the truck. Authenticating whether a genuine employee is entering his data and ensuring that a comprehensive data is stored are the prime focus of this document. Type of testing we are implementing in this project involves: manual testing that cover all the basic functionality on the system. For the validation of system features, we provide a demonstration of the website and performance testing will be a combination of demonstration and tester checklist. 6

7 2. Test Strategy and Preparation The strategy involves thorough testing of the entire functionality or capability requirement that are based on win-win condition 2.1 Hardware preparation Since we are only implementing the truck system, the project doesn t have high hardware requirements; only basic computer or a laptop is required. 2.2 Software preparation For functionality testing or capability requirement testing, a minimum of XP Window operating system is needed. 2.3 Other pre-test preparations There are no pre-test preparation required before implementing section 2.1 and section Requirements Traceability Table 1: Requirements Traceability Matrix Requirement ID Verification Type Test Case ID (if applicable) OC 1 Demonstration and TC 01, TC 04, TC 05 Testing OC 2 Demonstration and TC 02 Testing OC 3 Demonstration and TC 03 Testing OC 4 Demonstration and TC 06,TC 07 Testing OC 5 Demonstration 3. Test Identification 3.1 Test Identifier TC-01: Error checking/validation on the work order code 7

8 3.1.1 Test Level Software item level Test Class Erroneous test Test Completion Criteria Correct work order code/number - The system accept the work order number - The data/information of the field worker is stored in the database Test Cases Table 2: TC-01 Error checking/validation on the work order code Test Case Number Test Item Test Priority Pre-conditions Post-conditions Input Specifications Expected Output Specifications Pass/Fail Criteria Assumptions and Constraints Dependencies Traceability TC-01 Error checking/validation on the work order code Work order code/number Must (M) The user must be logged in to enter correct work order code/number The system validate the work order code Work order # : work order code/number The system accept the work order code User logs in successfully User selects the work order number : 10000, 20000, 30000, 40000, 50000, 60000, 70000, 80000, The system accept the work order code User has the knowledge of their work order code/number TC-02 User Log in CR-01: Error checking/validation on the work order code 3.2 Test Identifier TC-02: Log in Page Test Level Software item level 8

9 3.2.2 Test Class Authentication test: test if field worker/ employees with proper employee id could log into the website successfully Test Completion Criteria After successful log in -: - The application redirects to the welcome page of a particular field worker - For an incorrect log in, the user needs to re-enter the data Test Cases Table 2: TC-02 User Log in Test Case Number TC-02 User Log in Test Item Test log in Test Priority Must (M) Pre-conditions The user must have an account registered with LADOT Post-conditions The user is logged in Input Specifications Username: 0 5 by 1 Password : test Expected Output Specifications User view the welcome page/home page Pass/Fail Criteria User id 0 Password - test User logs in successfully User view welcome page Assumptions and Constraints Dependencies Traceability CR-2 : Log in 3.3 Test Identifier TC-03: Log out Page Test Level Software item level 9

10 3.3.2 Test Class Success test: test only the field worker/ employees who are logged in can successfully logged out Test Completion Criteria After successful log out -: - The application redirects to log in page Test Cases Table 3: TC-03 Log out Test Case Number Test Item Test Priority Pre-conditions Post-conditions Input Specifications Expected Output Specifications Pass/Fail Criteria Assumptions and Constraints Dependencies Traceability TC-03 User Log out Test log out Must (M) The user is logged in The user is logged out successfully Logout button/link User view the logout page User successfully logged out User redirect to log in page TC-02 User Log in CR-3 : Log out 3.4 Test Identifier TC-04: Valid Variation code Test Level Software item level Test Class Erroneous test 10

11 3.4.3 Test Completion Criteria Correct variation code -: - The system accept the variation number - The data/information of the field worker is stored in the database Test Cases Table 4: TC-04 Valid task code Test Case Number Test Item Test Priority Pre-conditions Post-conditions Input Specifications Expected Output Specifications Pass/Fail Criteria Assumptions and Constraints Dependencies Traceability TC-03 Valid Variation code Test Valid Variation code Must (M) The user is logged in The system validate the variation code variation order # : variation code/number The system accept the variation code User logs in successfully User selects the variation number 100,200,300,400,500,600,700,800 and 900 The system accept the variation code User has the knowledge of their variation code/number TC-02 User Log in CR-01: Valid Variation code 3.5 Test Identifier TC-05: Valid location code Test Level Software item level Test Class Erroneous test 11

12 3.5.3 Test Completion Criteria Correct location code -: - The system accept the location code - The data/information of the field worker is stored in the database Test Cases Table 5: TC-05 Valid location code Test Case Number Test Item Test Priority Pre-conditions Post-conditions Input Specifications Expected Output Specifications Pass/Fail Criteria Assumptions and Constraints Dependencies Traceability TC-03 Valid location code Test Valid location code Must (M) The user is logged in The system validate the location code variation order # : location code The system accept the location code User logs in successfully User selects the location code : 0 Figuroa &29 th 1 Figuroa & 30 th 2 Figuroa &1 st 3 Figuroa & 25 th 4 Grand & 29 th 5 Broadway & 30 th 6 Main & 29 th The system accept the location code User has the knowledge of their location code TC-02 User Log in CR-01: Valid location code 3.6 Test Identifier TC-06: Logs issue report Test Level Software item level 12

13 3.6.2 Test Class Success test: test only the field worker/ employees who are logged in can log the job or can report the job performed by them Test Completion Criteria After reporting the job-: - The worker click on the job completion tab Test Cases Table 6: TC-06 Logs issue report Test Case Number Test Item Test Priority Pre-conditions Post-conditions Input Specifications Expected Output Specifications Pass/Fail Criteria Assumptions and Constraints Dependencies Traceability TC-06 Logs issue report Test Logs issue report Must (M) The user is logged in The user click the log completion tab Drop down option to select job User successfully report the job into the system User logs in successfully User selects the correct location code User selects the correct variation code User selects the correct order code User completes the task User has the knowledge of their location code, work order code and variation code TC-02 User Log in CR-5 : Logs issue report 3.7 Test Identifier TC-03: Values input at the front end must be entered automatically at the backend field Test Level Software item level 13

14 3.7.2 Test Class Success test: The value entered at the front end must matches with the field present at the backend Test Completion Criteria After data entered at the backend -: - The system saves the data on its database Test Cases Table 7: TC-07 Values input at the front end must be entered automatically at the backend field Test Case Number Test Item Test Priority Pre-conditions Post-conditions Input Specifications Expected Output Specifications Pass/Fail Criteria Assumptions and Constraints Dependencies Traceability TC-07 Values input at the front end must be entered automatically at the backend field t Test Values input at the front end must be entered automatically at the backend field Must (M) The user is logged in Log of days work generated in XML file Submit report button All the data entered by the user will be stored at the backend User logs in successfully User selects the correct location code User selects the correct variation code User selects the correct order code User completes the task User click the submit button and data stored at the backend The value on the front end matches with the value present at the XML file TC-02 User Log in and TC-06 Logs issue report CR-4 : Export file 4. Resources and schedule 14

15 4.1 Resources Below are the list of required resources for completing the acceptance test plan and test case. Test Data -: - User input Hardware -: - Workable computer or laptop Software -: - Window laptop Budget -: - Laptop : already acquired by the LADOT management - Training the software to LADOT employees : 1 hour pay * 120 employees 4.2 Staffing and Training Needs The client Mr. Richard Harada, John Sam and Mony Patel, will be responsible for training the application to their employees after the development phase is completed. 4.3 Schedule Table 3: Testing Schedule Date Test Identifier Responsible person Resources Training needs 11/22/11 TC -01, TC-02 and Nisheeth Joshi 11 / 31/11 TC-03 15