Test Plan and Cases (TPC)

Transcription

1 Test Plan and Cases (TPC) United Direct Marketing Team 9 Fall Semester Chun-Ling Chen Project manager/ Prototyper Chun-Pei Su Lifecycle Planner Shao-yen Cheng System Architect Yuan-Chang Chang Feasibility Analyst Stewart Allen IIV&V/ Requirements Engineer Yen-Kuo Kao Operational Concept Engineer Spring Semester Chun-Pei Su Trainer / Document Maintainer Shao-yen Cheng Chief Developer Stewart Allen Tester / IIV&V / Quality Focal Point Kelvin Zhu Project Manager / Developer 3/31/2013

2 Test Plan and Cases (TPC) Version 2.1 Version History Date Author Version Changes made Rationale 11/24/2012 Stewart Allen 11/25/2012 Stewart Allen 1/27/2013 Kelvin Zhu 2/19/2013 Stewart Allen 3/31/2013 Stewart Allen 1.0 Created starting point from template Needed to get document started 1.1 Created test cases Defined test cases and filled in sections for 12/10 deadline for 2 semester project 1.2 Fixed spelling and grammar Correcting typos typos throughout document Updating with new team roster Updated team member list with members from Spring semester 2.0 Fix document from comment Need updated documentation for RDC during ARB. Duplicate WCs Added section 4 to complete the document for RDC 2.1 Update to reflect changes for IOC1 Delivery of IOC1 ii

3 Test Plan and Cases (TPC) Version 2.1 Table of Contents TEST PLAN AND CASES (TPC)... I VERSION HISTORY... II TABLE OF CONTENTS... III TABLE OF TABLES... V TABLE OF FIGURES Introduction PURPOSE SCOPE, FOCUS, AND TYPE OF TESTING Test Strategy and Preparation Hardware preparation Software preparation Other pre-test preparations Requirements Test Identification TC-01 Create Micro Website TC-02 Content Management System (CMS) TC-03 User Access and Accounts TC-04 Miscellaneous Website Visualization Resources and schedule Resources Staffing and Training Needs Schedule iii

4 Test Plan and Cases (TPC) Version 2.1 iv

5 ATPC_RDCP_F12a_T09_V2.0.doc Version 2.0 Table of Tables Table 1: Requirements (Win Condition) Matrix... 9 Table 2 TC Create Project Micro Website (Nominal) Table 3 TC Hit Count of Micro Website Table 4 TC Random Value Generated for Micro Website URL Table 5 TC View the Micro Website Table 6 TC Create Project Micro Website (Database Error) Table 7 TC Modify the website content Table 8 TC Modify the micro site content Table 9 TC Modify the website content library Table 10 TC User Log-in Table 11 TC Incorrect User Log-in Table 12 TC User Log-in Database Error Table 13 TC Subscribe to web system content Table 14 TC View list of subscribers Table 15 TC Content Library view and search Table 16 TC View web system in multiple browsers Table 17: Testing Schedule ATPC_RDCP_S13b_T09_V1.2.doc v Version Date: 1/27/2013

6 Table of Figures 6

7 1. Introduction 1.1 Purpose The Acceptance Test Plans and Cases (ATPC) document s the plan for testing the United Direct Marketing (UDM) web system against the requirements and Win Conditions located on the teams WinBook site. The detailed tests in this document are intended to test the satisfactory completion of the capability, interface, and level of service Win Conditions from WinBook as well. The items that will not be tested as part of this document are the schedule and budget constraints. 1.2 Scope, Focus, and Type of Testing The scope of this test plan and set of test cases is to document the satisfactory completion of the Win Conditions as documented in Win Book. The team will not use this plan to test integration testing items or other automated software testing practices outlined in the Quality Management Plan (QMP). Please review the QMP for additional information on other types of testing being performed, including verification and review of documents. 7

8 2. Test Strategy and Preparation The team will be using the Value-based test prioritization strategy for testing the cases outlined in this document. In this strategy the test cases are analyzed and subsequently prioritized prior to going through the test cases in this document. Therefore, a supplement to this document is the Acceptance Test Procedure and Report (ATPR) that identifies and prioritizes, as well as documents the success of the test cases during the actual acceptance test. 2.1 Hardware preparation The tests will be performed using a web server from a third party vendor called NewTek. This is also the location of the live web system deployment. There is no need to prepare the hardware. 2.2 Software preparation The software that will be used for testing will be the latest revision of the UDM web system. The software will need to be hosted in the test folders. 2.3 Other pre-test preparations NA 2.4 Requirements Below is a matrix of the Win Conditions to the Test Case and the Verification Type. The Win Conditions have been taken from the team s WinBook page and further documented in the latest Operational Concept Description (OCD) section 3.2. The Test cases are described in section 3 of this document. The types of verification may be: Testing, Demonstration, Analysis, Simulation, or Inspection. 8

9 Table 1: Requirements (Win Condition) Matrix Requirement ID Verification Type Test Case ID (if applicable) WC-1548: View Subscriber list on the Inspection TC website WC-1542: Select categorized case Demonstration TC studies for each microsite WC-1539: Configure user Testing TC address on the web system subscription WC-1536: Obtain login credentials for Testing TC the web system WC-1535: Modify existing micro Testing TC website WC-1534: View hit rate of the micro Demonstration TC websites WC-1529: Generate a random value for Demonstration TC the micro website url WC-1381: User may view from Testing TC Chrome, IE8, and IE9 WC-1375: Manage the content of the Testing TC-02-01, TC website using a Content Management System (CMS) WC-1374: View micro website of my Demonstration TC proposal WC-1373: Generate a micro website for Testing TC a project proposal WC-1372: Post related project content Testing TC on the micro website WC-1371: Attach promotional material Testing TC to the project micro website WC-1370: Search content on the Demonstration TC resources page WC-1366: Web system will send an Testing TC link of the micro website WC-1360: View example projects on a micro website Demonstration TC Test Identification 3.1 TC-01 Create Micro Website Test Level 1. Software Item Level Test Class 1. Functionality Test 2. Erroneous Test 9

10 3.1.3 Test Completion Criteria The test for the micro website will be completed when: 1. An administrative user creates a micro website, attaches project content to it, associates a category, and can send it to a user via an system 2. A user receives an containing a randomly generated url link from the web system 3. A user can navigate to the micro website url and see the micro website with the project content attached 4. An administrative user may navigate to the web system hit counter and see that the user visited the site 5. The administrator receives an appropriate error message if the micro website creation step fails Test Cases Table 2 TC Create Project Micro Website (Nominal) TC Create Project Micro Website (Nominal) This tests that the micro website can be created and ed out to a potential client. The administrative user is logged into the web system The micro website content is saved to the web system database. address for the micro website to be sent to. Content to upload to the micro website. A newly created micro website in the database The administrator can click a link to create a new micro website from the system The administrator can assign a categorized case study to the micro website. The micro website url was received by the user in their . The micro website url contains the generated micro website and related content attached. TC User Log-in WC-1542, WC-1371, WC-1372, WC-1373, WC

11 Table 3 TC Hit Count of Micro Website TC Hit count of micro website This tests that the micro website hit count can be seen in the micro website list and increases when a micro website is viewed The administrative user is logged into the web system A micro website has been created and is in the management list and viewable Micro website url The micro website hit count increases The micro website hit count on the microsite list view increases when the micro website is visited. TC User Log-in, TC Create Project Micro Website WC-1534 Table 4 TC Random Value Generated for Micro Website URL TC Random Value Generated for Micro Website URL This tests that the micro websites are created using a random url value so that the links are not easily found The administrative user is logged into the web system A micro website has been created and is in the management list and viewable The micro website hit count increases The micro website url has been generated with a random number and/or character sequence TC User Log-in, TC Create Project Micro Website WC-1529 Table 5 TC View the Micro Website TC View the Micro Website This tests that the micro websites can be viewed by a user or potential client of the UDM administrator. And that the micro website contains the project material and associated content. The micro website url has been generated A micro website url The micro website url is visible from a non logged in user. The micro website contains project related content. TC User Log-in, TC Create Project Micro Website WC-1374, WC

12 Table 6 TC Create Project Micro Website (Database Error) TC Create Project Micro Website (Database Error) This test is intended to capture the error that may occur during the creation of the micro website if the system is unable to communicate with the database, the user login has been timed out, or the server had an error sending the micro website link to the user. Could Have The user is logged in as an administrator System displays an error message that the database error occurred, or an error occurred. address for the micro website to be sent to. Content to upload to the micro website. An error message indicating that a database error occurred or an server error occurred. The system displays an appropriate error message if a database error occurs or an error occurs with sending the link of the micro website. The service is unavailable or able to be turned off, and the database is unavailable or able to be turned off TC User Log-in 3.2 TC-02 Content Management System (CMS) Test Level 1. Software Item Level Test Class 1. Functional test Test Completion Criteria The test for the Content Management System (CMS) will be completed when: 1. An administrative user can modify the website content 2. An administrative user can add or remove content from the content library 3. An administrative user can modify or delete the micro website content Test Cases 12

13 Table 7 TC Modify the website content TC Modify the website content This is to test that the primary website content may be modified using a Content Management System (CMS) The user is logged in as an administrator The content of the website has updated in the database. An updated webpage with the new content The system displays the modified content on the website TC User Log-in WC-1375 Table 8 TC Modify the micro site content TC Modify the micro website content This is to test that the micro websites generated by the administrators can be modified and deleted. The user is logged in as an administrator The content or removal of the micro website has updated in the database. An updated micro webpage with the new content, or a removed micro website The system displays the modified content on the micro website The system removes the micro website from the micro website list if the deletion is selected TC User Log-in WC-1535 Table 9 TC Modify the website content library TC Modify the website content library This is to test that the web system enables the users to add or remove content from the library that is displayed on the resources page. The user is logged in as an administrator The content to be added or removed has updated in the systems database New content to upload An updated resources page with the new or removed content The system displays the modified content on the resources page The system removes the content from the resources page TC User Log-in WC

14 3.3 TC-03 User Access and Accounts Test Level 1. Software Item Level Test Class 1. Functional test 2. Error test Test Completion Criteria The test for the User Log-in test will be completed when: 1. Each type of user can log-in to the system 2. When the user is logged in, the appropriate options are available on the web system 3. The administrative user is able to add, modify, and delete account information 4. A visitor to the website can subscribe to content on the web system 5. The administrator can view a list of the subscribed users 6. The system notifies the user with the appropriate error message if the user login information is incorrect 7. The system notifies the user with an appropriate error message if the database is unavailable for the user to log-in Test Cases Table 10 TC User Log-in TC User Log-in This is to test that the different types of users may log-in, and that the proper options are displayed when they log in. User log-in information for the system User logged in and the appropriate options are available Username, password Display with the appropriate menu options on the web system The system displays the appropriate options when the user of each type logs in WC

15 Table 11 TC Incorrect User Log-in TC Incorrect User Log-in This is to test that the user will receive an appropriate error message when the log-in information is incorrect Should Have Appropriate error message is displayed Invalid Username and/or password Display with the appropriate error message The system displays an appropriate error message Table 12 TC User Log-in Database Error TC User Log-in Database Error This is to test that the user will receive an appropriate error message when the database is unavailable to log in Should Have Appropriate error message is displayed Username and password Display with the appropriate error message The system displays an appropriate error message The system database is unavailable for this test Table 13 TC Subscribe to web system content TC Subscribe to web system content This is to test that a visitor to the web system may subscribe to the system address Database contains the new subscription information address of the visitor subscribing to the site The database system will update with the appropriate information The system will update with the new subscription content WC

16 Table 14 TC View list of subscribers TC View list of subscribers This is to test that an administrator may visit the web system and grab the list of addresses that has subscribed to the web system Administrator access The system will display a list of the subscribers The system will display the subscribers to the system TC WC TC-04 Miscellaneous Website Visualization Test Level 1. Software Item Level Test Class 1. Functional test Test Completion Criteria The test for the Content Library will be completed when: 1. A visitor to the website may visit the resources page to view and search library content Test Cases 16

17 Table 15 TC Content Library view and search TC Content library view and search This is to test that a visitor to the website can view and search library content on the resources page Content in the library to view and search Display with the appropriate content The system displays the resources page and the user is able to search the content. The user is able to download pdf files and other content from the web system TC WC-1370, WC-1364(duplicate removed) 17

18 Table 16 TC View web system in multiple browsers TC View the web system in multiple browsers This is to test that the web system may be viewed appropriately in Chrome, IE8, and IE9 The user has Chrome, IE8, and IE9 Display with the appropriate content in each browser The system displays each page, including administrative pages in each of the browsers WC Resources and schedule This section is identified in order to specify the people, time, budget, resources, and schedule allocated for testing the UDM Project. 4.1 Resources The following resources are required for the teams testing process. 1. Web Server Loaded with UDM Web System 2. Client Computer with Browser and access to the new system 3. Test Data Set a. Sample files to upload to the UDM Library b. Sample package to upload to the micro website c. Sample address for subscription and micro website features d. Sample files for related projects 4.2 Staffing and Training Needs The following list are those stakeholders responsible for managing, designing, preparing, executing, witnessing, inspecting, and resolving the test items. 1. Stewart Allen Tester 2. Samta Jain Client/Observer 3. Shao-yen Cheng (Optional) Developer 4. Chun-Pei Su - Trainer 4.3 Schedule 18

19 Table 17: Testing Schedule Date Test Identifier Responsible person Resources Training needs Iteration1: 3/20/2013 TC-01-01, TC-01-02, TC-01-03, TC-01-04, TC Stewart Allen Samta Jain Resources identified Iteration2: 4/13/2013 TC-02-01, TC-02-03, TC-03-01, TC-03-04, TC-03-05, TC-04-01, TC-04-02, Stewart Allen in 4.1 Samta Jain Resources identified in