Acceptance Test Plan and Cases (ATPC)

Transcription

1 Acceptance Test Plan and Cases (ATPC) Version 1.1 Acceptance Test Plan and Cases (ATPC) Leamos Team 7 Name Address Primary Role Secondary Role Monty Shah montysha@usc.edu Project Manager Life Cycle Planner David Wiggins dgwiggin@usc.edu IIV&V Off-campus Shaper Pragya Singh pragyasi@usc.edu System Architect Prototyper Shantanu Sirsamkar sirsamka@usc.edu Requirements Engineer Feasibility Analyst Suchita Doshi suchitad@usc.edu Prototyper Operational Concept Engineer Swapnil Savdekar savdekar@usc.edu Life Cycle Planner System Architect 11/30/2011

2 Acceptance Test Plan and Cases (ATPC) Version 1.1 Version History Date Author Version Changes made Rationale 11/21/11 Wiggins 1.0 Modifications for Initial Draft Initial draft 11/30/11 Wiggins 1.1 Added test cases for addition of new courses and conversion of old ones Mapped test cases to CRs instead of WCs Need for additional test cases ii

3 Acceptance Test Plan and Cases (ATPC) Version 1.1 Table of Contents ACCEPTANCE TEST PLAN AND CASES (ATPC)... 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 Test Identification Test Identifier TC Test Identifier TC Test Identifier TC Test Identifier TC Test Identifier TC Resources and schedule Resources Staffing and Training Needs Schedule iii

4 Acceptance Test Plan and Cases (ATPC) Version 1.1 Table of Tables Table 1: Requirements Matrix... 8 Table 2: TC Forgot Password Function and Login... 9 Table 3: TC Buying a license as a partner site Table 4: TC Buying a license as an independent site Table 5: TC Buying a license as an independent user Table 6: TC Admin Adds Student Account Table 7: TC Admin Views Student Account Table 8: TC Admin Edits Student Account Table 9: TC Admin Generates Report Table 10: TC Flash to HTML5 conversion Table 11: TC Addition of new course content Table 12: Testing Schedule A

5 Acceptance Test Plan and Cases (ATPC) Version 1.1 Table of Figures No table of figures entries found. A

6 1. Introduction The Acceptance Test Plan is identifies a test execution plan to ensure that the clients requirement documented in the Win Conditions, which the stakeholders have agreed upon, are fulfilled by the product being developed. Test cases will be traced to those win conditions and designed to clearly define weather the win condition is fulfilled or not. The Test Plan will further identify any necessary actions needed in order to execute the planned cannon of tests. The environment will attempt to emulate the expected user environment as much as is feasible. Since the product is a combination of both NDI integration and some agile development, testing will have to be planned at both the system and software levels. Some win conditions will be satisfied through tests planned in this document while others will have to be demonstrated to the client and checked off with the client s approval. 6

7 2. Test Strategy and Preparation << Describe the project s test strategy with respect to such options as: Agile test-first Agile continuous integration Boundary and exit/entry criteria between unit testing and integration testing Integration order-of-build Value-based test prioritization Test environment preparation Requirements-test traceability >> 2.1 Hardware preparation <<Describe the procedures needed to prepare the hardware for the test, including support hardware (e.g., test equipment). Reference any operating manuals, if applicable. Provide the following as applicable: Specification of each hardware that will be used in testing and number (if applicable) Purpose of each hardware item, security and privacy considerations. >> 2.2 Software preparation << Describe the procedures needed to prepare the software for the test, including test scaffolding and support software (e.g., input generators, simulators, data recording/reduction software, test output orales). Reference any software manuals, if applicable. Provide the following as applicable: The specific software to be used, identified by name and, if applicable, version number Purpose of each software item, security and privacy considerations Type and description of test data>> In order to begin testing a premade tester account will need to be loaded into the database to fulfill preconditions of initially testing login functionality which all other tests depend on. 2.3 Other pre-test preparations << Describe any other pre-test personnel actions, preparations, or procedures needed to perform the test not accounted for in 2.1 or 2.2 above. >> 7

8 2.4 Requirements Table 1: Requirements Matrix Win Conditions Description Verification Type CR-1: Authentication and authorization CR-2 : HTML5 lessons CR-3: Sales websites, account creation, Management of the Students by the organizations. CR-4: Adding new lessons and documentation We will need to write code in PHP as part of the client login functionality which will authenticate and authorize the client. Also for students we will implement the forgot password page. We will convert the existing FLASH files to HTML5 to be rendered in browsers on mobile devices. The sales website will be created using PHP and the backend will be MySQL. This will then call the Course Merchant services which will then pass the control back to us, post which we will create account for customer and enable him to create/manage student accounts based on the number of licenses he bought. We will manually add new lessons to Moodle using PHP and MySQL and we will document how to do it so that the maintainers can follow the steps and add new lessons on their own. Demonstration, Testing Testing Testing Demonstration, Testing Test Case ID (if applicable) TC-01 TC-04 TC-02, TC-03 TC Test Identification 3.1 Test Identifier TC-01 TC-01-Forgot Password Functionality and Login Test Level The testing will be performed at the system item level Test Class Correctness Test 8

9 3.1.3 Test Completion Criteria As a result of using the forgot password function -: - the user can retrieve or reset their password easily without needing to interact with Leamos staff Test Cases Table 2: TC Forgot Password Function and Login TC Forgot Password Function and Login Login and forgot password functionality The user must have an account registered with Leamos or A premade test user is loaded into the DB. The user successfully resets or is reminded of their password and logs in to the system using that password. Username: premadeuser, Password: password, Answers to security questions for the account. User logs into the Leamos system successfully. User resets their password by answering security questions. User successfully logs on to the system after resetting their password. User can still logon to the system without using the password reset function if they know their password. Tester can t think of a better way to further minimize clicks in order to simplify the interface. Password complexity requirements are enforced. CR Test Identifier TC-02 TC-02-Attaining a Leamos License Test Level The testing will be performed at the system item level Test Class Correctness/Erroneous Test 9

10 3.2.3 Test Completion Criteria From the home page of the sales website -: - the user can buy a Leamos website as a partner site, independent site, or Independent user. After payment -: - the user is provided with a username and password to the system Test Cases Table 3: TC Buying a license as a partner site TC Buying a license as a partner site Sales Website license attainment User has a valid form of payment. User will be provided with the License(s) with a username and password. Customer Name: Bubba, Admin Username: Admin123, Admin Password: iamsuperuser, LeamosTester@gmail.com, Payment Information for the course merchant (developed by third party) User receives a partner site license after submitting payment through the course merchant. User can login using their admin account, take Spanish course, navigate the site, create learner accounts, manage students. CR-3 Table 4: TC Buying a license as an independent site TC Buying a license as an independent site Sales Website license attainment User has a valid form of payment. User will be provided with the License(s) with a username and password. Customer Name: Bubba, Admin Username: Admin123, Admin Password: iamsuperuser, LeamosTester@gmail.com, Payment Information for the course merchant (developed by third party) User receives an independent site license after submitting payment through the course merchant. User can login using their admin account, take Spanish course, navigate the site, create learner accounts, manage students. 10

11 CR-3 Table 5: TC Buying a license as an independent user TC Buying a license as an independent user Sales Website license attainment User has a valid form of payment. User will be provided with the License(s) with a username and password. Customer Name: Bubba, Username: Kelly123, Password: mynameiskelly, Payment Information for the course merchant (developed by third party) User receives an independent user license after submitting payment through the course merchant. User can login using their account, take Spanish course, navigate the site. CR Test Identifier TC-03 TC-03-Student Management Test Level The testing will be performed at the system item level Test Class Correctness/Erroneous Test Test Completion Criteria After admin has logged in -: - student accounts can be created, viewed, or edited - reports can be generated 11

12 3.3.4 Test Cases Table 6: TC Admin Adds Student Account TC Admin Adds Student Account Student Management by admin user Admin navigates to the Add Student tab. Admin enters new student information in all the fields and clicks the Add button. A new student account is added. Number of licenses remaining is decremented. Name: Bill, Address: NW Wallaby Ct, Date of Birth: 12/12/1981, Gender: Male, Phone Number: , Course Type: Advanced, Username: mynameisnotbob, Password: passwd A new student can login and view course material using the newly created account. A new student can login and view course material using the newly created account. Duplicate Username is not allowed. Password complexity requirements are enforced. Number of licenses remaining is decremented. Reset button on the GUI clears all fields. I can login: mynameisnotbob with pw: passwd TC-02-01, TC CR-3 Table 7: TC Admin Views Student Account TC Admin Views Student Account Student Management by admin user There already exists a student account to view. Admin navigates to the View Student tab. Admin views information associated with a student s account. Admin views information associated with a student s account. Admin views information associated with a student s account. Account information accurately represents what s stored in the database. TC-02-01, TC-02-02, TC CR-3 12

13 Table 8: TC Admin Edits Student Account TC Admin Edits Student Account Student Management by admin user There already exists a student account to edit. Admin navigates to the Edit Student tab The admin can verify changes were made to this student s profile on the View Student tab. Name: Bob, Address: NW Wallaby Ct, Date of Birth: 11/11/1983, Gender: Female, Phone Number: , Course Type: Basic, Username: mynameisbob, Password: password Selected Student info is updated when the update button is clicked. Selected Student info is updated when the update button is clicked. Password field enforces password complexity requirements. Clicking cancel makes no changes to the Database. Remaining number of licenses is unchanged. I can login: mynameisbob with pw: password I can t login as mynameisnotbob I can t login with the old password TC-02-01, TC-02-02, TC CR-3 Table 9: TC Admin Generates Report TC Admin Generates Report Student Management by admin user Admin navigates to the Generate Report tab User sees a report on student progress. User sees a report on student progress. Admin can generate the report Admin can search and filter the report TC-02-01, TC CR Test Identifier TC-04 TC-04-Flash to HTML5 conversion Test Level The testing will be performed at the system item level 13

14 3.4.2 Test Class Correctness Test Test Completion Criteria After running the chosen tool to convert a swf file to HTML5 -: - The HTML5 runs smoothly and without errors or missing content Test Cases Table 10: TC Flash to HTML5 conversion TC Flash to HTML5 conversion Ability to convert SWF flash files to HTML5 SWF file: Each of the 40+ SWF lesson files from the client. Each SWF file is converted flawlessly We watch each of the lessons to ensure all are converted without errors. No content is lost in conversion. Lessons are now compatible in standard browsers. none CR Test Identifier TC-05 TC-05-Addition of new Courses Test Level The testing will be performed at the system item level Test Class Correctness Test Test Completion Criteria After adding a new course to the system -: - The new course is available from the appropriate selection menus. - The new course plays all the way through smoothly without crashing 14

15 3.5.4 Test Cases Table 11: TC Addition of new course content TC Addition of new course content The addition of a new course to the system. Should (S) New course content provided by Leamos. A new course is added to the system. We watch each of the lessons in the course to ensure they have no errors. No content is lost. Lessons are compatible in standard browsers. None CR-4 15

16 4. Resources and schedule <<In this section, specify the people, time, budget, resources and schedule allocated for testing, etc. >> 4.1 Resources << Identify all resources need for testing, such as test data set, software, budget, and etc >> 4.2 Staffing and Training Needs << Identify the stakeholders responsible for managing, designing, preparing, executing, witnessing, inspecting and resolving test items. In addition, provide the groups responsible for providing items to be tested. Specify test-staffing needs by skill level. Identify training options for providing necessary skills. >> 4.3 Schedule Table 12: Testing Schedule Date Test Identifier Responsible person Resources Training needs 01/02/09 TC to TC John Smith Report test data sets, N/A JUnit 16