Acceptance Test Plan. Stake holder: Dawn Gulick Group members:

Transcription

1 Acceptance Test Plan by Advisor: Santiago Ontañón Stake holder: Dawn Gulick Group members: Matt Hinkle (Computer Science) Steven Hershey (Computer Science) Dylan Kenny (Computer Science) Steven Hansen (Computer Science) Austin Blakeslee (Computer Science) Alexy Thomas (Computer Science)

2 TABLE OF CONTENTS 1. DOCUMENT HISTORY DOCUMENT INFORMATION REVISION HISTORY OVERVIEW PROJECT BACKGROUND PROJECT SCOPE SCOPE OF THE DOCUMENT REFERENCES GLOSSARY TEST PROCEDURE INTRODUCTION TEST OBJECTIVES TEST STRUCTURE TEST APPROACH TEST EXECUTION TESTING ROLES AND RESPONSIBILITIES INTRODUCTION TEAM ROLES TRAINING REQUIREMENTS REPORTING PROCEDURES Reporting Failed Tests Generating Test Reports ENTRY AND EXIT CRITERA INTRODUCTION ENTRY CRITERIA EXIT CRITERIA TEST ASSUMPTIONS AND EXCLUSIONS INTRODUCTION TEST ASSUMPTIONS TEST INCLUSION TEST EXCLUSIONS TEST CASES INTRODUCTION TEST CASES FOR ALL USERS ADMINISTRATIVE MOBILE APP INTEROPERABILITY ADMINISTRATIVE CLIENT Credenetials Dialog Tests Read Error Dialog Start Screen

3 7.4.4 Special Test View Select Test Dialog Mobilization Test View ADd New Test Dialog New Test Group Dialog Add Image Dialog Add Video Dialog Add Reference Dialog Menu Bar Upload Confirmation Dialog Uploading Dialog Add Image Dialog Upload Failure Dialog Promotion Confirmation Dialog Finished Promotion Dialog Select File Dialog MOBILE APPLICATION Root Screen Test Table Navigation Screen Tests Video Screen Tests TRACEABILITY MATRIX TEST MATRIX

4 1. DOCUMENT HISTORY 1.1 DOCUMENT INFORMATION Title: Author: Reviewers: iortho+ Project: Acceptance Test Plan Mike Hershey Mike Hershey 1.2 REVISION HISTORY Version: Date: Editor: : 1.0 1/7/13 Mike Hershey Initial draft 1.1 1/9/13 Alexy Thomas Revised Tenses 1.2 1/15/13 Steven Hansen Updated to reflect meeting with Dawn 1.3 1/26/13 Dylan Kenny Additional Tests Added 1.4 1/30/13 Austin Blakeslee Updated Traceability Matrix 1.5 2/1/13 Mike Hershey, Alexy Thomas, Steven Hansen, Dylan Kenny Big meeting to finalize the document for submission 3

5 2. OVERVIEW 2.1 PROJECT BACKGROUND iorthoplus is an educational mobile application for reviewing and assessing physical therapy test strategies. The application, available on both ios and Android platforms, is primarily used in the academic realm to help facilitate learning amongst physical therapy students. Currently, the iorthoplus application is difficult for the administrator to maintain content and issue new tests or updates quickly and cost-effectively. Releasing new information requires an administrator to not only generate the initial content, but also send it to the developer, who then resubmits it to the Apple and Play (Android) stores. The latter part of this process can take over two weeks to complete, which is simply unacceptable for this situation. This procedure severely limits the administrator's ability to upload information to the application and further degrades the reliability and versatility of the product to the user. The new iorthoplus system includes an administrative client, which circumvents the majority of the publication process, updated mobile applications, as well as a reliable back-end framework to support the new implementation. The administrative client is responsible for enabling an iorthoplus official to create, format, and publish new or edited content directly from their personal computer, without having to contact any third parties. The back-end framework stores, maintains, and catalogues the updated content for acquisition from the mobile client applications. The mobile applications are the users' gateway to the content hosted on the framework. The mobile software queries the remote content manager for the test it seeks, and verifies if the device should be updated. This process removes any developer-intervention as well as any interaction with the mobile market-places, while still allowing for dynamic content to be accessed by the end-user. 2.2 PROJECT SCOPE The goal of the project is to manipulate the existing mobile applications to be compliant with a dynamic content management system, thereby requiring a regular loading of the index of tests. Furthermore, this project standardizes code-trees between the different mobile platforms to enable easier modifications for future developers. The userinterface of the mobile software is changing to better suit the needs of the client, using basic principles of humancomputer interaction. The administrative client is built completely stand-alone and operating system-independent, while using minimal resources. The software allows the administrator to perform basic text editing within the application. Furthermore, the application provides the ability for the user to generate, edit, preview, and publish test information to the remote storage. The test format is crafted to mirror typical user-interfaces the user is likely familiar with. Rather than having hardcoded test designs, the new system allows for a predefined template to be used within the applications, enabling easy redesign of existing and future tests alike. 2.3 SCOPE OF THE DOCUMENT This document is designed to describe the functional testing that will be executed to determine if our final product conforms to the requirements document and will cover the following pieces of software: The admin client 4

6 The ios mobile app* The Android mobile app* * The mobile apps will both be functionally the same, so both of these softwares will jointly be referred to as mobile apps and the tests for mobile apps shall be performed and evaluated on both mobile apps. In addition to the authored or modified pieces of software our tests will ensure that all applications can handle 3 rd party service outages reasonably well. This document will not cover unit code-testing or any form of automated testing. 2.4 REFERENCES This document follows the Software Requirements Specification for iortho+ to show how each requirement will be tested. Tests will list the requirement number from the Software Requirements Specification for iortho+ to indicate which requirement is being evaluated by each test. 2.5 GLOSSARY Apple Apple Inc., formerly Apple Computer, Inc., is an American multinational corporation headquartered in Cupertino, California that designs, develops, and sells consumer electronics, computer software, and personal computers Play Store Google Play is a digital entertainment hub, similar to Apple's itunes Store, where you can purchase a whole range of different media products Administrator A person responsible for managing the content available to the application Administrative client The application for the administrator the edit the content available to the mobile application Mobile application The applications available on mobile platforms such as ios and Android phones and tablets S3 a scalable, high-speed, low-cost Web-based service designed for online backup and archiving of data and application programs The Internet The Internet (or internet) is a global system of interconnected computer networks that use the standard Internet protocol suite (TCP/IP) to serve billions of users worldwide Tests may refer generically to mobilizations or special tests which all have references, pictures and videos Mobilizations a test that contains the following fields: contacts, indication, and technique Special Tests a test that contains the following fields: purpose, technique, and interpretation S3 Access Key Id an alphanumeric text string that uniquely identifies user who owns account. No two accounts can have same AWS Access Key S3 Secret Access Key plays role of password. It's called secret because owner only knows it, that's why when you type it in given box, it s displayed as asterisk or dots. A Password with Access Key forms a secure information set that confirms user's identity Test Tree A collection of tests kept in tree form for organizational clarity 5

7 HTML HyperText Markup Language (HTML) is the main markup language for creating web pages and other information that can be displayed in a web browser Android an open mobile phone platform that was developed by Google and, later, by the Open Handset Alliance. Google defines Android as a "software stack" for mobile phones. ios a mobile operating system developed and distributed by Apple Inc. Originally released in 2007 for the iphone and ipod Touch, it has been extended to support other Apple devices such as the ipad and Apple TV Staging Area/Bucket a location for storing test content in order to provide an intermediary area to view tests without allowing them to be publicly available Production Area/Bucket a location for storing test content to be publicly available for the mobile applications iphone a line of smartphones designed and marketed by Apple Inc. It runs Apple's ios mobile operating system, known as the "iphone OS" until mid-2010, shortly after the release of the ipad ipad a line of tablet computers designed and marketed by Apple Inc., which runs on Apple's ios operating system Java a general purpose, concurrent, class based, object oriented computer programming language that is specifically designed to have as few implementation dependencies as possible API a protocol intended to be used as an interface by software components to communicate with each other. An API may include specifications for routines, data structures, object classes, and variables 6

8 3. TEST PROCEDURE 3.1 INTRODUCTION This section outlines the way this document presents tests and the procedure that shall be used to execute tests. 3.2 TEST OBJECTIVES These tests serve as the verification that our final product conforms to and meets all of the requirements set forth in Software Requirements Specification for iortho+. A product that passes each of these tests is considered functionally complete. 3.3 TEST STRUCTURE This Acceptance Test Plan defines a series of procedures that shall be executed to verify that the referenced requirement is satisfied in the product being tested. Each test will provide a set of preconditions, actions, and post conditions. The tests are broken up into groups and arranged logically so each piece of software can be tested in parallel with other parts of the system. 3.4 TEST APPROACH The tests are designed to be easy to follow and executed by anyone allowing the client to easily perform all the tests and verify that the software works and passes each test if they wish to. The team will also provide the clients with a Test Report generated according to the procedure defined by the following section Roles and Responsibilities. The tests are designed to be run manually; developers may also provide automated testing but they will not be considered for the purposes of verifying that the software is functionally complete as the automated testing may be faulty. 3.5 TEST EXECUTION To perform a test the tester begins with the application in a state such that all preconditions are met. The tester then performs the actions described in order. If the application then meets all of the post conditions the test is considered successful and passing. If a test does not meet the post conditions after the actions are performed then the test has failed and the tester will follow the procedure described in Roles and Responsibilities to properly report the deficiency. 7

9 4. TESTING ROLES AND RESPONSIBILITIES 4.1 INTRODUCTION This section describes the various roles that each participant will perform and the procedure for handling test results including how to report failed tests and how to create a Test Report. 4.2 TEAM ROLES Testing Team Leader: Team Members: Client Tester: Alexy Thomas Steven Hansen, Steven Hershey, Dylan Kenny, Matthew Hinkle, Austin Blakeslee Dawn Gulick 4.3 TRAINING REQUIREMENTS Testers must be familiar with the function of the application and the Software Requirements Specification for iortho+ however no specific programming or technical knowledge is required to execute this test plan. 4.4 REPORTING PROCEDURES Ad-Hoc execution of tests require no reporting unless there are tests which have not passed or you want to generate Test Report to give to the client as documentation that all tests have succeeded or an updated status report to the team REPORTING FAILED TESTS If a test fails to pass then the tester begins by taking detailed notes on the exact conditions that caused the test to fail and any errors that are thrown by the app. The tester then runs the app from console if possible to see any additional logging or stack traces that may help the developers identify the issue and include those with the other information. The tester should then rerun the test under the exact conditions that are believed to have caused the error and make sure that the error occurs again. If the error does not occur again the tester should make a reasonable effort to reproduce the error and narrow in on the conditions required to reproduce the error. Regardless of reproducibility the tester will inform the test team leader of the failed test and as much information as possible. The lead tester will then verify the issue and bring it up at a team meeting GENERATING TEST REPORTS A test report is a report that is used as documentation that all tests have been executed. A test report contains the dates that the tests were executed, the latest revision numbers (and software version numbers if applicable), and the results from each test. Failures will be thoroughly documented for the sake of reporting failures via the procedure described above. A passing test report will be provided along with the final product to the client. 8

10 5. ENTRY AND EXIT CRITERA 5.1 INTRODUCTION This section describes the conditions that must be met before starting this Acceptance Test Plan and the conditions that must be must to consider testing complete. 5.2 ENTRY CRITERIA It is appropriate to begin this test plan when the following conditions are met: iortho+ is considered fully implemented by the developers after each has indicated that their work is complete. An appropriate testing environment is created. A copy of the Software Requirements Specification is finalized and agreed on by all parties. The S3 accounts are transferred from our testing account to the account provided by the client 5.3 EXIT CRITERIA The Acceptance Test Plan is considered complete after the following conditions are met: All tests corresponding to priority 1 requirements are completed successfully and each test passes. The client agrees that all tests pass successfully At least one priority 1 requirement failed their test 9

11 6. TEST ASSUMPTIONS AND EXCLUSIONS 6.1 INTRODUCTION This section provides additional details about which features of the system will be covered by the Acceptance Test Plan, and which will not be covered. 6.2 TEST ASSUMPTIONS It is assumed that the implementation was previously addressed by unit tests, integration tests and system tests of iortho+. Exclusions from this test process are addressed by these previous tests. 6.3 TEST INCLUSION The Acceptance Test Plan covers: Functionality defined and required by the SRS document Usability of the system 6.4 TEST EXCLUSIONS The Acceptance Test Plan does not cover: Functionality not described or required by the SRS document The non-functional requirements of the system described by the SRS document Structural integrity of source code 10

12 7. TEST CASES 7.1 INTRODUCTION The following test cases cover the functionality described in the Software Requirements Specification. Each test has the following format: Requirement(s) Precondition(s) Action(s) Postcondition(s) [Test care number] [Test ] [Corresponding requirements that are being tested] [A short description of the test] [A set of preconditions required to start the test] [A sequential list of actions to perform for the test] [The conditions that must be true for the test to pass] 7.2 TEST CASES FOR ALL USERS The following test cases are for both end users and the administrator. The tests will be performed on the mobile applications. 7.3 ADMINISTRATIVE MOBILE APP INTEROPERABILITY TC-1 Publish Test Requirements Precondition(s) Publish/update a test without having to deal with Apple or Play markets. The admin client is open. A test is either chosen to be created or edited. The required fields for a test have been filled out. Action(s) Click Upload button. Click Upload to Staging 11

13 Postcondition(s) The test is on the remote storage server and is accessible. TC-2 Staging Test Visibility Requirements , A test published to the staging area should be available to the mobile application beta version, but not the standard mobile application. Precondition(s) The admin client is open. A test is either chosen to be created or edited. The required fields for a test have been filled out. The staging area has been selected for publication. Action(s) Postcondition(s) Click Upload button. Click Upload to Staging button. The test is on the remote storage server, in the staging area, and is accessible to only the beta mobile application. The test is not available to the standard mobile application. TC-3 Production Test Visibility Requirements ,

14 A test published to the production area should be available to the mobile application version and the standard mobile application. Precondition(s) The admin client is open. A test is either chosen to be created or edited. The required fields for a test have been filled out. The production area has been selected for publication. Action(s) Click Upload button. Click Promote Staging to Prod button. Postcondition(s) The test is on the remote storage server, in the production area, and is accessible to the beta mobile application. The test is on the remote storage server, in the production area, and is accessible to the standard mobile application. 7.4 ADMINISTRATIVE CLIENT CREDENETIALS DIALOG TESTS TC-4 Credential Dialog layout Requirement(s) , , Verifies that the layout of the Credential Dialog is accurate Precondition(s) The application is not running 13

15 Action(s) Start the Admin Client application Postcondition(s) The Credentials Dialog is be centered on screen The Credentials Dialog has a text field for the S3 Access Key Id The Credentials Dialog has a text field for the S3 Secret Access Key The Credentials Dialog has a check box labeled Save Credentials The Credentials Dialog has an OK confirmation button TC-5 Save Credentials Requirement(s) , , If the checkbox labeled Save Credentials is checked when the confirmation button is pressed that client writes the access and secret key to an encrypted file and prepopulate the credentials on the next restart Precondition(s) The application is running and the Credentials Dialog is displayed Text is present in both the Access Key and Secret Key text field. Action(s) Check the checkbox labeled Save Credentials Hit the confirmation button and wait for the Main Screen to fully load Close the application Restart the application Postcondition(s) The Credentials Dialog is be centered on screen The Credentials Dialog has the text that you entered previously prepopulated into the Access Key and Secret Key text fields. There is a file in the iortho+ hidden folder in your home directory which contains cyber text of the Access Key and Secret Key The save credentials checkbox is checked TC-6 Don t Save Credentials 14

16 Requirement(s) , If the checkbox labeled Save Credentials is unchecked when the confirmation button is pressed that client removes any saved credentials and no persist them for the next application start Precondition(s) The application is running and the Credentials Dialog is displayed Text is present in both the Access Key and Secret Key text field. The Access Key and Secret Key have been previously saved and there is the file with cyber of text both present in the iortho+ hidden folder Action(s) Uncheck the checkbox labeled Save Credentials Hit the confirmation button and wait for the Main Screen to fully load Close the application Restart the application Postcondition(s) The Credentials Dialog is be centered on screen The Credentials Dialog has no value in the Access Key and Secret Key text fields. There is no file in the iortho+ hidden folder in your home directory containing cyber text of the Access Key and Secret Key TC-7 Confirmation Button pressed Requirement(s) Clicking the Confirmation Button with the text OK loads the Main Screen with all available tests Precondition(s) The application is running and the Credentials Dialog is displayed Correct S3 Access Key and Secret Keys are entered into the corresponding text fields Amazon s S3 service is operating normally The S3 staging bucket is appropriately bootstrapped Action(s) Click the Confirmation Button Wait for the dialog to finish loading and open 15

17 the Main Screen Postcondition(s) The Main Screen is open and maximized containing all tests in the staging bucket The left side of the main screen contains a list of the tests that currently exist in the staging bucket The Test Tree is fully expanded on the initial load, displaying all of the tests and test groups The root of the tree has no indentation while subsequent levels of the tree has increased indentation relative to their parent The content pane displays the components for a Special Test with all of the UI components disabled READ ERROR DIALOG TC-8 Read Error Confirmation Dialog Requirements , , If an error occurs, a message should appear to let the user know along with a confirmation button. Precondition(s) The admin client is open. An error occurs trying to read the test file or index. The read error dialog is open to inform the user of the error. Action(s) Postcondition(s) Press the confirmation button. The application exits START SCREEN 16

18 TEST TREE TC-9 Test Tree UI Requirements , , , , Precondition(s) Action(s) Postcondition(s) The styling of the tree should consistent with that specified in the requirements. The admin client is open. Log in to the client. The tree is expanded and all subcomponents are exposed. The root folder has no indentation. All other items are indented. Body part items are capitalized with a document icon if empty, or a folder if not empty. Test groups are represented with the test name and a folder icon. Tests are represented with the test name and a document icon. TC-10 Selecting a Test (mobilizations) Requirement(s) When the user selects a test, the information related to the test is loaded into the Test Screen Precondition(s) The application is running and the Main Screen is displayed No test is selected in the Test Tree Action(s) Select a mobilizations test in the Test Tree Postcondition(s) The Mobilization Test View is displayed and the display matches the SRS description All fields in the Mobilization Test View reflect the information for the test selected 17

19 TC-11 Selecting a Test (special tests) Requirement(s) When the user selects a test, the information related to the test is loaded into the Test Screen Precondition(s) The application is running and the Main Screen is displayed No test is selected in the Test Tree Action(s) Select a special test in the Test Tree Postcondition(s) The Special Test View is displayed and the display matches the SRS description All fields in the Special Test View reflect the information for the test selected TC-12 Selecting a Test Group Requirement(s) When the user selects a test group, the tests under it are expanded Precondition(s) The application is running and the Main Screen is displayed There is a test group that has not been expanded Action(s) Click the Expand arrow Postcondition(s) The correct tests are shown under it. TC-13 Add Test Button Requirement(s) Clicking the Add Test Button opens the Add New Test Dialog 18

20 Precondition(s) The application is running and the Main Screen is displayed Action(s) Click the Add Test Button Postcondition(s) The Add New Test Dialog is now shown The Add New Test Dialog matches the description described in the SRS TC-14 Delete Test Button Requirement(s) , Clicking the Delete Test Button deletes the currently selected test Precondition(s) The application is running and the Main Screen is displayed A test or test group is selected in the Test Tree Action(s) Click the Delete Test Button Postcondition(s) The tree has updated and any reference to the selected test are removed TC-15 Delete Test Button (test group) Requirement(s) , Clicking the Delete Test Button deletes the currently selected test and all sub tests when a test group is selected Precondition(s) The application is running and the Main Screen is displayed A test group is selected in the Test Tree Action(s) Click the Delete Test Button 19

21 CONTENT PANE TC-16 Saving Tests Requirement(s) Any action performed to edit the state of a test will save the new state in memory Precondition(s) The application is running and the Main Screen is displayed A test is selected and the Content Pane shows the corresponding test view with all information accurately displayed Action(s) Edit any part of the Test Click away to a new test Click back to the test that you edited Postcondition(s) The state that you changed is accurately reflected in the Content Pane SPECIAL TEST VIEW TC-17 Special Test View Title Requirements Precondition(s) The title of the test should match that specified at test creation. The admin client is open. Tests exist in the test tree. Action(s) Postcondition(s) Select a special test to view. The title of the test is that specified by the user during test creation. 20

22 TC-18 Special Test View Purpose Requirements Precondition(s) Action(s) Postcondition(s) The user should be able to fill in the Purpose field. The admin client is open. Tests exist in the test tree. Select a special test to view. Enter data into the Purpose field. The Purpose field contains the characters sent by the user. TC-19 Special Test View Technique Requirements The user should be able to fill in the Technique field. Precondition(s) The admin client is open. Tests exist in the test tree. Action(s) Select a special test to view. Enter data into the Technique field. Postcondition(s) The Technique field contains the characters sent by the user. TC-20 Special Test View Interpretation Requirements

23 The user should be able to fill in the Interpretation field. Precondition(s) The admin client is open. Tests exist in the test tree. Action(s) Select a special test to view. Enter data into the Interpretation field. Postcondition(s) The Interpretation field contains the characters sent by the user IMAGES TC-21 Images Box Requirements , Precondition(s) Adding an image and verifying the information is correct. The application is showing the Add Image Dialog. An image had been added in this dialog, and all information has been filled out. Action(s) Postcondition(s) Click OK to add the image. There has been a new entry added to the Images Box. The name of the newly added image matches the name given in the Add Image Dialog. TC-22 22

24 Add Image Button Requirement(s) , , , , , , Pressing the Add Image Button Precondition(s) The application is running and the Main Screen is displayed A test is selected and the Content Pane shows the corresponding test view with all information accurately displayed Action(s) Click the Add Image Button Postcondition(s) The Add Image Dialog is displayed The Add Image Dialog is exactly as described in the SRS TC-23 Delete Image Button Requirements Precondition(s) Pressing the Delete Image Button. The application is running and the Main Screen is displayed. A test is selected and the Content Pane shows the corresponding test view with all information displayed. The test has had at least 1 image added to it. Action(s) Select the image to be deleted from the list of images. Click the Delete Image Button. Postcondition(s) The deleted image is no longer in the list of images. 23

25 VEOS TC-24 Videos Box Requirements , Precondition(s) Adding an image and verifying the information is correct. The application is showing the Add Video Dialog. A video had been added in this dialog, and all information has been filled out. Action(s) Postcondition(s) Click OK to add the video. There has been a new entry added to the Videos Box. The name of the newly added video matches the name given in the Add Video Dialog. TC-25 Add Video Button Requirement(s) , , , , , , , , Pressing the Add Video Button 24

26 Precondition(s) The application is running and the Main Screen is displayed A test is selected and the Content Pane shows the corresponding test view with all information accurately displayed Action(s) Click the Add Video Button Postcondition(s) The Add Video Dialog is displayed The Add Video Dialog is exactly as described in the SRS TC-26 Delete Video Button Requirement(s) , Pressing the Delete Video Button Precondition(s) The application is running and the Main Screen is displayed A test is selected and the Content Pane shows the corresponding test view with all information accurately displayed There is at least 1 video added to the test Action(s) Select an video from the list Click the Delete Video Button Postcondition(s) The selected video is no longer in the list of videos STATISTICS TC-27 Statistics Box 25

27 Requirements Precondition(s) Adding text to the Statistics Box and verifying it updates test. The application is running and the Main Screen is displayed. A test is selected and the Content Pane shows the corresponding test view with all information displayed. Action(s) Type information into the Statistics Box. Postcondition(s) The text in the statistics box saves and is there when the test information is reloaded. Loading the test in the app shows the correct statistics information as it was entered before REFERENCES TC-28 References Box Requirements , Precondition(s) Action(s) Adding a reference and verifying the information is correct. The application is showing the Add Reference Dialog. All of the information has been filled out for the new reference. Click OK to add the reference. 26

28 Postcondition(s) There has been a new entry added to the References Box. The name of the newly added reference matches the name given in the Add Reference Dialog. TC-29 Add Reference Button Requirement(s) , , , Pressing the Add Reference Button Precondition(s) The application is running and the Main Screen is displayed A test is selected and the Content Pane shows the corresponding test view with all information accurately displayed Action(s) Click the Add Reference Button Postcondition(s) The Add Reference Dialog is displayed The Add Reference Dialog is exactly as described in the SRS TC-30 Delete Reference Button Requirement(s) , Pressing the Delete Reference Button Precondition(s) The application is running and the Main Screen is displayed A test is selected and the Content Pane shows the corresponding test view with all information accurately displayed There is at least 1 reference added to the test Action(s) Select an reference from the list Click the Delete Reference Button 27

29 Postcondition(s) The selected reference is no longer in the list of references ASSOCIATIONS POSITIVE ASSOCIATIONS TC-31 Positive Associations Box Requirements , Precondition(s) Adding a positive association and verifying the information is correct. The application is showing the Select Test Dialog. A test has been selected. Action(s) Postcondition(s) Click OK to add the association. There is a new test under positive associations. TC-32 Add Positive Associations Button Requirements Precondition(s) Pressing the Add Positive Association Button. The application is running and the Main Screen is displayed. A test is selected and the Content Pane shows the corresponding test view with all information displayed. 28

30 Action(s) Postcondition(s) Click the Add Positive Association Button. The Select Test Dialog is now shown. The Select Test Dialog matches the description described in the SRS. TC-33 Remove Positive Associations Button Requirements Precondition(s) Pressing the Remove Positive Association Button. The application is running and the Main Screen is displayed. A test is selected and the Content Pane shows the corresponding test view with all information displayed. The test has had at least 1 positive association added to it. Action(s) Select the association to be removed. Click the Remove Positive Association Button. Postcondition(s) The positive association is no longer in the list. NEGATIVE ASSOCIATIONS TC-34 Negative Associations Box Requirements ,

31 Precondition(s) Adding a negative association the test that verifies if the information is correct. The application is showing the Select Test Dialog. A test has been selected. Action(s) Postcondition(s) Click OK to add the negative association. There is a new test under negative associations. TC-35 Add Negative Associations Button Requirements Pressing the Add Negative Association Button. Precondition(s) The application is running and the Main Screen is displayed. A test is selected and the Content Pane shows the corresponding test view with all information displayed. Action(s) Click the Add Negative Association Button. Postcondition(s) The Select Test Dialog displays the test view with all its corresponding information. TC-36 Remove Negative Associations Button Requirements

32 Precondition(s) Action(s) Pressing the Remove Negative Association Button. The application is running and the Main Screen is displayed. A test is selected and the Content Pane shows the corresponding test view with all information displayed. The test has at least one negative association added to it. Select the association to be removed. Click the Remove Negative Association Button. Postcondition(s) The negative association is no longer in the list SELECT TEST DIALOG TC-37 Select Test Dialog Requirements , , Precondition(s) Select the test from the Test Dialog The application is showing the Select Test Dialog. The main content of the Select Test Dialog is the test list that shows up on the screen. Action(s) Select a test in the test list by clicking on test name. Press the Select Button. Postcondition(s) Pressing the Select Button, selects the test highlighted in the Test List. 31

33 TC-38 Title Requirements , Precondition(s) User enters the title of the test for the test created. The application is showing the screen with the option to add a new test. Action(s) Click Add Test to add a new test. On creating a new test, add the title of the test in the test area.. Postcondition(s) A new test gets added to the Test List with its corresponding name. TC-39 Select Test Dialog Cancel Requirements , , Precondition(s) Select the test from the Test Dialog The application is showing the Select Test Dialog. The main content of the Select Test Dialog is the test list that shows up on the screen. Action(s) Select a test in the test list by clicking on test name. Press the Cancel Button. 32

34 Postcondition(s) Pressing the Cancel Button, closes the Test List MOBILIZATION TEST VIEW TC-40 Indication Requirements Precondition(s) Enter what a particular test indicates. The application is showing the screen with all the contents displayed in the content pane. A test is selected from the test list. Action(s) Add description to the text area that explains what the particular test indicates. Postcondition(s) On clicking the Add Test the indication gets added to the selected test as a part of description. TC-41 Technique Requirements Enter a technique that corresponds to a particular test. 33

35 Precondition(s) The application is showing the screen with all the contents displayed in the content pane. A test is selected from the test list. Action(s) Add description to the text area that explains the technique for the selected test. Postcondition(s) On clicking the Add Test the technique gets added to the selected test as a part of description. TC-42 Contacts Requirements Precondition(s) Action(s) Enter what body parts are involved in a particular test. The application is showing the screen with all the contents displayed in the content pane. A test is selected from the test list. Application is showing text area for contact. Adding description to the text area that explains what body parts are involved in a particular test. Postcondition(s) On clicking the Add Test the contact gets added to the selected test as a part of description IMAGES 34

36 TC-43 Image title Requirement(s) An image should be represented by its given title in the image list of a test. Precondition(s) The app is at the main window. A test is selected in the test list tree. Action(s) Click the Add Image button. Fill in the required information for the Add Image Dialog, setting the image title to Image Test and click the confirmation button. Postcondition(s) The image list should contain an added entry Image Test TC-44 Add image button. Requirement(s) Pressing the add image button will open the add image dialog. Precondition(s) The app is at the main window. A test is selected in the test list tree. Action(s) Press the add image button in the content pane. Postcondition(s) The Add Image Dialog should open. TC-45 Delete Image Requirement(s) An image should be removed from the image list when the remove image button is pressed and an image is selected in the image list. 35

37 Precondition(s) The app is at the main window. A test is selected in the test list tree. The selected test has at least one image associated with it. Action(s) Select an image in the image list. Press Remove Image Postcondition(s) The image list should not contain the image that was selected by the tester before pressing Remove Image VEOS TC-46 Video title Requirement(s) A video should be represented by its given title in the video list of a test. Precondition(s) The app is at the main window. A test is selected in the test list tree. Action(s) Click the Add Video button. Fill in the required information for the Add Video Dialog, setting the video title to Video Test and click the confirmation button. Postcondition(s) The video list should contain an added entry Video Test REFERENCES TC-47 36

38 Reference title Requirement(s) A reference should be represented by its given link in the reference list of a test. Precondition(s) The app is at the main window. A test is selected in the test list tree. Action(s) Click the Add Reference button. Fill in the required information for the Add Reference Dialog, setting the reference link to Reference Test and click the confirmation button. Postcondition(s) The video list should contain an added entry Reference Test ADD NEW TEST DIALOG TC-48 Add Test Button Requirement(s) , , , , , Clicking the Add Test Button creates a new test with the given parameters Precondition(s) The application is running and the Add New Test Dialog is open Action(s) Select the parameters for the type of test that you wish to select (test with varying paramaters) Click the Add Test Button Postcondition(s) The Test Tree is updated and contains the new test fulfilling the given criteria TC-49 37

39 Add Group Button Requirement(s) , , , , , Clicking the Add Group Button opens the New Test Group Dialog Precondition(s) The application is running and the Add New Test Dialog is open Action(s) Click the Add Group Button Postcondition(s) The New Test Group Dialog is displayed and has the specifications given by the SRS TC-50 Cancel Button Requirement(s) Clicking the Cancel Button closes the window without creating a new test Precondition(s) The application is running and the Add New Test Dialog is open Action(s) Click the cancel button Postcondition(s) The Add New Test Dialog is now hidden The Test Tree is unmodified NEW TEST GROUP DIALOG TC-51 Confirmation Button Requirement(s) Clicking the Confirmation Button will create a new Test 38

40 Group Precondition(s) The application is running and the New Test Group Dialog is open There is some text in the New Test Group Dialog Action(s) Click the OK Confirmation Button Postcondition(s) A new test group is added to the Test Tree with the given name that was in the text field The Add New Test Dialog is now focused TC-52 Cancel Button Requirement(s) Clicking the Cancel Button closes the window without creating a new test group Precondition(s) The application is running and the New Test Group Dialog is open There is some text in the New Test Group Dialog Action(s) Click the Cancel Button Postcondition(s) The New Test Group Dialog is now hidden No new test group is created ADD IMAGE DIALOG TC-53 Confirmation Button Requirement(s) , , , , Clicking the Confirmation Button will create a new image Precondition(s) The application is running and the Add Image 39

41 Dialog is open The Add Image Dialog is completely filled out Action(s) Click the OK Confirmation Button Postcondition(s) The Add Image Dialog is now hidden A new image with the given parameters is present in the image list TC-54 Cancel Button Requirement(s) Clicking the Cancel Button closes the window without creating a new image Precondition(s) The application is running and the Add Image Dialog is open The Add Image Dialog is completely filled out Action(s) Click the Cancel Button Postcondition(s) The Add Image Dialog is now hidden No new image is in the image list ADD VEO DIALOG TC-55 Confirmation Button Requirement(s) , , , Clicking the Confirmation Button will create a new video Precondition(s) The application is running and the Add Video Dialog is open The Add Video Dialog is completely filled out Action(s) Click the OK Confirmation Button 40

42 Postcondition(s) The Add Video Dialog is now hidden A new video with the given parameters is present in the video list TC-56 Cancel Button Requirement(s) Clicking the Cancel Button closes the window without creating a new video Precondition(s) The application is running and the Add Video Dialog is open The Add Video Dialog is completely filled out Action(s) Click the Cancel Button Postcondition(s) The Add Video Dialog is now hidden No new video is in the video list ADD REFERENCE DIALOG TC-57 Confirmation Button Requirement(s) , , Clicking the Confirmation Button will create a new reference Precondition(s) The application is running and the Add Reference Dialog is open The Add Reference Dialog is completely filled out Action(s) Click the OK Confirmation Button 41

43 Postcondition(s) The Add Reference Dialog is now hidden A new reference with the given parameters is present in the reference list TC-58 Cancel Button Requirement(s) Clicking the Cancel Button closes the window without creating a new reference Precondition(s) The application is running and the Add Reference Dialog is open The Add Reference Dialog is completely filled out Action(s) Click the Cancel Button Postcondition(s) The Add Reference Dialog is now hidden No new reference is in the reference list MENU BAR ADVANCED TC-59 Reset All Tests Menu Option Requirement(s) , , , , Clicking the Reset All Tests menu option opens the Reset All Tests Confirmation Dialog Precondition(s) The application is running and the menu bar is visible Action(s) Click the Advanced -> Reset All Tests 42

44 Postcondition(s) The Reset All Tests Confirmation Dialog is displayed as described in the SRS UPLOAD TC-60 Upload to Staging Menu Option Requirement(s) Clicking the Upload to Staging Button opens the Upload Confirmation Dialog Precondition(s) The application is running and the menu bar is visible Action(s) Click the Upload -> Upload to Staging Postcondition(s) The Upload Confirmation Dialog is displayed as described in the SRS TC-61 Promote Staging to Prod Menu Option Requirement(s) Clicking the Promote Staging to Prod menu option opens the Promote Confirmation Dialog Precondition(s) The application is running and the menu bar is visible Action(s) Click the Upload -> Promote Staging to Prod Postcondition(s) The Promote Confirmation Dialog is displayed as described in the SRS 43

45 UPLOAD CONFIRMATION DIALOG TC-62 Upload Confirmation Dialog, confirmed. Requirement(s) , The upload confirmation dialog should be displayed when the menu option Upload to Staging is selected. When confirmed it should open the Uploading Dialog. Precondition(s) The app is at the main window. Action(s) Tester selects Advanced from the menu bar and chooses Upload To Staging. Tester presses the confirmation button. Postcondition(s) The message displayed to the tester should alert them that they are uploading the current set of tests to staging. The Uploading Dialog should display. TC-63 Upload Confirmation Dialog, cancelled. Requirement(s) , The upload confirmation dialog should be displayed when the menu option Upload to Staging is selected. When cancelled it should close the dialog. Precondition(s) The app is at the main window. Action(s) Tester selects Advanced from the menu bar and chooses Upload To Staging. Tester presses the cancel button. Postcondition(s) The message displayed to the tester should alert them that they are uploading the current set of tests to staging. The dialog should close and return the user to the main window. 44

46 UPLOADING DIALOG MESSAGE TC-64 Uploading Dialog Requirement(s) , Clicking the Confirmation Button in the Upload Confirmation Dialog displays the Uploading Dialog Precondition(s) The application is running and the Upload Confirmation Dialog is open There is some text in the Uploading Dialog Action(s) Click the Confirmation Button Postcondition(s) The Uploading Dialog is displayed and has the specifications given by the SRS TC-65 Message Requirement(s) , A string of text describing the current step in the upload process is displayed Precondition(s) The application is running and the Uploading Dialog is open There is some text in the Uploading Dialog Action(s) Direct attention to the Uploading Dialog 45

47 Postcondition(s) The Uploading Dialog is displayed and has the specifications given by the SRS TC-66 Initial Message Requirement(s) The initial message is the first message displayed in the Uploading Dialog when it appear Precondition(s) The application is running and the Uploading Dialog is open There is some text in the Uploading Dialog Action(s) Direct attention to the Uploading Dialog Postcondition(s) The content of Message is displayed and has the specifications given by the SRS TC-67 Saving Index Message Requirement(s) The message displayed after Initial Message in the Uploading Dialog 46

48 Precondition(s) The application is running and the Uploading Dialog is open There is some text in the Uploading Dialog Action(s) Direct attention to the Uploading Dialog Postcondition(s) The content of Message is displayed and has the specification given by the SRS TC-68 Rendering Tests Message Requirement(s) The message displayed after Saving Index Message in the Uploading Dialog Precondition(s) The application is running and the New Test Group Dialog is open There is some text in the Uploading Dialog Action(s) Direct attention to the Uploading Dialog Postcondition(s) The content of Message is displayed and has the specification given by the SRS ADD IMAGE DIALOG 47

49 TC-69 Uploading Tests to S3 Message Requirement(s) The message displayed after Rendering Tests Message in the Uploading Dialog Precondition(s) The application is running and the New Test Group Dialog is open There is some text in the Uploading Dialog Action(s) Direct attention to the Uploading Dialog Postcondition(s) The content of Message is displayed and has the specification given by the SRS TC-70 Finished Uploading Test to S3 Message Requirement(s) The message displayed after Uploading Tests to S3 Message in the Uploading Dialog Precondition(s) The application is running and the New Test Group Dialog is open There is some text in the Uploading Dialog Action(s) Direct attention to the Uploading Dialog 48

50 Postcondition(s) The content of Message is displayed and has the specification given by the SRS PROGRESS BAR TC-71 Progress Bar Requirement(s) A bar representing the number of steps completed divided by the number of steps total in the Uploading Dialog Precondition(s) The application is running and the Uploading Dialog is open There is a Progress Bar displayed within the Uploading Dialog Action(s) Direct attention to the Uploading Dialog Postcondition(s) Progress Bar is displayed and is filled according to the specification given by the SRS TC-72 Empty Requirement(s)