Test Plan and Cases (TPC)

Transcription

1 Test Plan and Cases (TPC) Software Quality Analysis as a Service Team 01 Aditya Kathuria Prototyper Aleksandr Chernous Life Cycle Planner Chris Harman Operation Concept Supicha Phadunsilp Feasibility Analyst Jincheng He Quality Focus Point Reza Khazali Software Architect George Llames IIV & V Kaur Requirement Analyst 4/27/2017

2 Version History Date Author Version Changes made Rationale 11/22/ Original template was changed as per the project 04/27/2017 George 2.0 Overhauled Section 3 (Test Cases) This is the first draft for TPC Update for test cases performed ii

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

4 Table of Tables No table of figures entries found. iv Version Date: 04/27/2018

5 1. Summary The purpose of this document is to provide an overview of the test plan. For the purposes of brevity and tidiness, this document will not provide all the artifacts related to testing. The system build contains the following artifacts: Final test suite (also embedded in this document). o Test Identification o Test Cases o Manual test instructions and procedures o Test Results Automated test files o Environment setup o Test instructions o.feature files identified by use case These are contained within the system build zip file: SYSTEM_ASBUILT_S18b_T01_V2.0.zip docs Automated Blackbox Final Test Suite containing Test Plan, test cases, and test results: Final Test Suite + Results xlsx The test cases are all linked to predefined requirements and expected behaviors, and both blackbox testing and whitebox testing checked against the requirements and for errors in expected behaviors. The test cases were performed on the deployed version of the SQUAAD web application. The tests were all successfully completed before transition and final delivery of the project. 5

6 2. Test Strategy and Preparation We use Agile Test-first methods, to generate the test cases even before the main code is actually written. The next phase of testing involves Agile Continuous-Integration methodology, in which each and every single unit of the code is tested as it is being written. And, in the end, we use the Requirements-Test Traceability method. This is done to make sure that each and every unit of the code has been properly developed and tested. 2.1 Hardware preparation The basic hardware requirements for testing are a personal computer with preferably 2GB of RAM to support web browsing on Google Chrome and an internet connection. This is sufficient hardware preparation for both blackbox and whitebox testing. 2.2 Software preparation The test environment will require using Google Chrome web browser. Blackbox testing only requires this, as the testing is performed on the deployed version of the web application. For whitebox testing, a specific test environment is required on the local machine. These are fully documented in detail in the testing documents in the System zip file as described in Section 1. To highlight, the test environment will require Ruby, Cucumber, Capybara, and Selenium Webdriver. Additionally, whitebox testing scripts are run at the command line, and can be performed on Linux, Windows, or Mac. On Linux and Mac, the test cases can be run at the terminal. For windows, it is recommended to use either Git-Bash for Windows, or Bash for Windows. 2.3 Other pre-test preparations N/A the preparations above are sufficient. 2.4 Requirements Traceability Table 1: Requirements Traceability Matrix 6

7 Win Condition ID / Requirement ID Requirement Verification Type Test Case Ids Add a functional page that would send a request to admin to grant access UC-6 to a user from a Request_to_Add_New_P WC_4424 contributor roject_contributor User shall be able to export to.csv / ascii file from the project analysis UC-12 See Project WC_4341 /statistics page Analysis Results There should be tabs to view list of projects, list of users, users in a particular project and projects accessible to a WC_4339 particular user Demonstration 20 users should be able to work with the system WC_4607 simultaneously. Simulation User should be able to see different graphs when a project is WC_4453 selected from Dashboard Demonstration Projects with no access UC-4 View Open Source WC_4338 should not be searchable Projects Project analysis view should load in less than WC_4609 or equal to 2 seconds. Analysis 7

8 Add a functional page that will have checkboxes user-project- WC_4300 access-ownership Demonstration Get HTTPS certificate and deploy the app for WC_4426 https Demonstration The system shall have a feature where user accounts can be WC_4503 deactivated. Users must be able to submit a request for UC-11 Request Project WC_4449 project analysis. Analysis The system shall be in WC_4553 react.js Inspection System registration triggers UC-1 Register as a WC_4450 notification. Collaborator The user must receive an after completing UC-1 Register as a WC_4337 sign up page. Collaborator User should be able to smoothly interact with the system scatterplot chart of the coevolution of a project with data points for up to 4 WC_4608 metrics. Simulation 8

9 Admin should be able to WC_4501 reset a user's password. The user dashboard should show all the projects contributed to or personal projects analyzed, with indicators if it is open or closed UC-4 View Open Source WC_4509 source Projects WC_4425 User should be able to reset password after pressing "Forgot Password" from sign in/sign on page UC-5 Reset Password Admin should UC-9 grant/deny request from Approve_Add_New_Pro WC_4452 Admin dashboard ject_contibutor_request Project contributors should be granted access to projects they UC-4 View Open Source WC_4499 contributed on. Projects Users should have access to open source projects UC-4 View Open Source WC_4508 within the system. Projects 9

10 3. Resources and schedule 3.1 Resources The resources involved in the testing effort are those highlighted in the section above regarding testing hardware and software. Aside from these physical resources, time resources will naturally have to be allocated for testing. 3.2 Staffing and Training Needs This job will be done by the identified testing team. For the items that will be provided to them will be the code and the software. These items will be provided to them by the other five members of the group. will also be provided with the test suite by the others, and then, they will proceed with the testing. 3.3 Schedule Table 5: Schedule Date Test Identifier Responsible person Resources Training needs 01/15/18-01/15/18 01/15/18-01/15/18 04/15/18-04/20/18 UC01-UC09 test suite N/A UC10-UC17 George Test suite N/A UC17-20 Reza and Sahar Test suite N/A 01/30/18- Working on Whitebox Test Code Needed N/A 02/12/18 Cases 10

11 02/13/18- Perform Whitebox Code Needed N/A 03/12/18 03/13/18- Repeat failed test cases Test case results N/A 03/26/18 03/27/18- Check for Updates on test Test Case Results N/A 04/09/18 cases and creating survey 04/10/18- Repeat failed and new test Test case results N/A 04/23/18 cases 04/24/18- Conduct and compile Coordination N/A 04/30/18 survey results with client 11