Regression Test Package (RTP)

Transcription

1 Regression Test Package (RTP) LEMA Pilot School Integrated Scheduling System Team Number 12 Name Primary Role Secondary Role David Wiggins Project Manager Developer Aakash Shah Prototyper Developer Kushalpreet Kaur Developer Developer Thammanoon Kawinfruangfukul Tester Developer Eunyoung Hwang Architect Developer Louis Demaria IIV&V Developer Mark Villanueva QFP Developer Sangik Park Developer Developer 04/26/12

2 Version History Date Author Version Changes made Rationale 04/08/12 MV 1.0 All sections Updates for Draft TRR Package 04/26/12 MV 2.0 Section 2. Tests to Run Updates for IOC Working Set #2, corrections for graded RTP ii

3 Table of Contents REGRESSION TEST PACKAGE (RTP)...I VERSION HISTORY...II TABLE OF CONTENTS...III TABLE OF TABLES...IV TABLE OF FIGURES...V 1. Introduction Purpose and Background of testing Scope of testing Focus of testing Type of testing Tests to run Regression Test Results... 8 iii

4 Table of Tables Table 1: Scenarios and Regression Test Cases (cross-referenced from ATPC)... 7 RTP_IOC2_S12b_T12_V2.0 iv 04/26/12

5 Table of Figures No table of figures entries found. RTP_IOC2_S12b_T12_V2.0 v 04/26/12

6 1. Introduction 1.1 Purpose and Background of testing The purpose of testing in the project is to verify that all the functional requirements of the LEMA Scheduling System have been implemented without defects. The team has been following multiple stages of testing. First, when capabilities are first implemented, the developer performs unit testing in his own development area. If more there are dependencies between components, the team also performs integration testing. Once that is complete, the tester role performs the appropriate acceptance test procedures from the ATPC. The software being tested is installed in a test environment on the server. Finally, testers perform regression testing after new functionality is developed. Future maintainers of the system will also need to perform regression testing as system administrators modify the system. Deployment testing activities will occur on a clean installation of the latest software build on the target server. 1.2 Scope of testing Functional requirements are matched with test cases and test cases are written in such a way that a passing test will verify that the win conditions associated with that test case have been met. In addition, some test procedures also exercise edge cases (invalid input, user error, etc.) thus ensuring the performance of the system. 1.3 Focus of testing The Regression testing verifies that existing capabilities of the system are still functional. In other words, regression testing validates that new changes to the system do not introduce defects to known working functionality. While the test cases test separate modules, we also need to consider test cases that test an end-to-end use case (thread testing). 1.4 Type of testing The team is using Boundary value testing with exit and entry criteria for continuous Unit and Integration Testing. Test cases are also prioritized utilizing the Value based Test Prioritization. 6

7 2. Tests to run Table 1: Scenarios and Regression Test Cases (cross-referenced from ATPC) System Change Scenario Test Case Number Rationale New student user added to/removed from the system New teacher user added to/removed from the system New administrator user added to/removed from the system TC ~ 04 TC ~ 04 TC-03-07b TC-04-01a TC ~ 04 TC TC-03-03, 07a, 11 TC ~ 04 TC ~ 11 These test cases deal with authentication of users: logging in and out of the system These exercise the privileges and capabilities of the student role Verifies Administrator access to new student information Verifies Counselor access to new student information These test cases deal with authentication of users: logging in and out of the system These exercise the privileges and capabilities of the teacher role Verifies Administrator access to new teacher information These test cases deal with authentication of users: logging in and out of the system These exercise the privileges and capabilities of the administrator role New counselor user added to/removed from the system TC ~ 04 TC ~ 03 These test cases deal with authentication of users: logging in and out of the system These exercise the privileges and capabilities of the counselor role The database is reinstalled from scratch/backup or the data is migrated to another database TC This test case verifies that the administrator can access and view the database s contents Users upgrade web browser or install another one altogether TC This test case verifies that the website behaves as expected across different web browser Administrator adds a new course list for an upcoming semester TC-03-03b, 04, 05, 09,10 These test cases cover all the functionality involving importing or modifying the course list information in the database 7

8 3. Regression Test Results The following results are from the first run of the Test Plan. As of the time of this version of the document, this is the only Regression Test that was run. We will run another regression test when all capabilities are implemented. This document will be updated accordingly as new regression tests are run. Regression Test #1 Test Case Number TC-01-* TC-02-01, TC-02-02, TC TC TC-03-01, TC-03-02, TC-03-03, TC-03-03a, TC-03-04, TC , TC-03-08, TC TC-03-06, TC-03-07, TC-03-07b, TC-03-10, TC-03-10a TC-04-01, TC-04-02, TC-04-02a TC TC TC TC TC TC-04-01a TC-04-02a TC-03-03b TC-03-08a TC Result N/A, not implemented N/A, not implemented N/A, not implemented N/A, not implemented N/A, did not test Fail, toggling between states did not preserve pre-existing selected checkboxes Conditional pass, if there is no data for the selected semester in the database, the user is redirected to a page noting the error. It should be a pop-up or the year should not be in the dropdown in the first place N/A, did not test 8