NGForms. Acceptance Test Plan. v1.1. Drexel CS Senior Design Dan DeCamillo Hung Dinh Julian Lico Raymond Ross, Jr.

Transcription

1 NGForms Acceptance Test Plan v1.1 Drexel CS Senior Design Dan DeCamillo Hung Dinh Julian Lico Raymond Ross, Jr. Trung Tran 1

2 Contents 1 Introduction User Acceptance Definition Background Purpose References Testing Procedures Reporting Device Specific Attributes Test Responsibilities Test Assumptions and Exclusions Assumptions Exclusions Test Strategy Entry Methods Form Files Form Browser Archiving Form Submission Deployment Security Requirements Form Browser User Interface Form Generation User Interface Test Log

3 1 Introduction 1.1 User Acceptance Definition User Acceptance Testing should ensure that the application performs at an acceptable level for the Customer. 1.2 Background This document provides the plan for testing the NGForms software project. This document does not require that the reader to understand the implementation details of the program. The document assumes the reader is familiar with the Software Requirements Specifications of the NGForms software project. 1.3 Purpose The document defines the tests that are to be performed and passed for the NGForms software to be considered acceptable for the Red Cross Emergency Services to use. 1.4 References Software Requirements Specifications for the NGForms software project. 3

4 2 Testing Procedures 2.1 Reporting Testers shall fill out a Test Log document (attached) that lists all tests and specify the test's failure or success. All problems that are encountered need to be documented and reported to the NGForms team. When the system is considered acceptable, both parties will sign off on this document. 2.2 Device Specific Attributes NGForms is not being built for a specific device. Each Input Methods are Device Dependent. Please read the device's manual to find out if the device supports the feature. 2.3 Test Responsibilities Role Name Responsibilities Project Lead Hung Dinh Communicate with Red Cross Managers to agree on the Specified Tests for each requirement. Test Coordinator Clifton Salas Ensure that test plan is available for testers Ensure that bugs are indentified in Test Log. Project Test Lead Dan DeCamillo Assist Red Cross testers with running the Test Plan. 3 Test Assumptions and Exclusions 3.1 Assumptions The Acceptance Test Plan is intended to test the following: Requirements specified in the Software Requirements Document. Usability and functional use of the Software. 3.2 Exclusions Before performing the Acceptance Test Plan, all unit tests need to have been preformed and passed. The Acceptance Test Plan is not intended to test the following: Non-functional requirements of the Software Requirements Document. Software Security. 4

5 4 Test Strategy This section outlines tests that verify that each requirement s expected result is met after performing the test method. Tests scenarios in this document are outlined as follows: Requirement (s) Description Pre- requirement (if any) Test Method Requirement number(s) in SRS Description of the requirement as describe in the SRS. Requirements needed for a test to be run Steps that are to be performed by the tester Conditions that should be met for the Requirement to be satisfied 4.1 Entry Methods Requirement (s) Description Typing - Fields can be filled in by either physical or virtual keyboards. Pre-requirement Device needs to have Physical or Virtual Keyboard Test Method - Use keyboard to type into text fields - Both the physical and virtual keyboards should allow input into text fields in the form. Requirement (s) Description GPS information can be used to fill out the location field. Pre-requirement Device needs to have GPS capability Test Method - Check to see if the location field is filled in automatically by the internal GPS. - Check to see if the automated entry by the GPS is correct. - The GPS should enter an accurate location automatically in the location field. Requirement (s) Description Voice Recognition - Fields can be filled in by recognizing the user's voice. Pre-requirement Device needs to have voice input. Test Method - Make sure the device microphone is working properly. - Check to see if the field accepts speech to text input. - Check to see if the text generated is accurate to what was actually spoken. - The spoken information is properly transcribed into text in the respective field. Requirement (s) Description Image Scanning - Images can be taken by the smart phone's camera and 5

6 Pre-requirement Test Method stored. Device needs to have camera - Take a picture. - Attach the picture to a form. - The picture should be stored on the device and attached to the chosen case file. Requirement (s) Description Handwriting Recognition - Field can be filled by hand writing. Pre-requirement Device needs to have handwriting ability Test Method - Client should be able to select a field. Using a stylus or their finger the user should write the information that is to be inputted into the field. The handwritten information should be transcribed to text and placed in the respective field. - The handwritten information should be accurately converted to text and placed in the selected field. 4.2 Form Files Requirement (s) , Sub Requirements , , , Description General 1. The software will allow a form to have multiple fields. 2. The software will allow each field to have the capability of having multiple "AltInputs". 3. The software will allow each field the option of specifying a default value. 4. Fields can be marked with a validation type. Test Method - Check to see if forms have multiple fields. - Check all requirements from section for input methods. - Check to see if the required fields contain default values. - Check that specified fields are checked for validity. - The form should be complete with all fields and inputs working correctly and accurately. All data that needs to be verified should be verified. Requirement (s) , Sub Requirements , , , , , , , Description Validation Types 1. Numerical Field Field must be numerical. 2. Date Field Field must be in the Gregorian Date Format. 3. Non-Empty Field Field must have a value. 4. Member in Pre-defined Field Field must exist in a pre-defined list for example state abbreviations must belong to an array populated by state 6

7 Test Method abbreviations. 5. Form Characters - Only characters in A-Z, 0-9 range. 6. Field Field must be numerical, field must be less than max and greater than min. 7. Valid Format Field must be in a valid format name@domain.com. 8. Regular Expression Field must pass regular expression. - Enter numerical data and check to see that it is verified as numerical data. - Enter alphabetical data and make sure that this data is rejected. - Enter a date into a date field. Check to see if it is in Gregorian date format. If it is not in this format reject the data. - Leave a required field empty. Check to see if this empty field is rejected. - Select a drop down or check box list. Check to see if the options are automatically populated by predefined arrays. - Enter characters that do not belong to the A-Z or 0-9 character range. These will be rejected. - Check that fields have a numerical length by using inputs of varying size. - Enter an address in an field in the form name@domain.com. - Input a regular expression into a field. Numerical Data will be accepted and alphabetical data will be rejected. - Gregorian format dates will be accepted and non-gregorian format dates will be rejected. - Required fields left empty will be rejected. - Predetermined lists and arrays are correctly displayed as choices. - Only characters A-Z and 0-9 are accepted. - All lengths between the min and max are accepted. - addresses of valid format are accepted. - Correctly inputted regular expressions are identified and accepted. Requirement (s) Description Failed Validation - If validation fails, user must be alerted of error in the Form Browser. Test Method - Enter non-accepted data into any field. - An error should appear on the screen related to the incorrect data input. Requirement (s) , Sub Requirements , , , , , Description Adding Pages to the Form 1. The software will show all available Entry methods in an "Entry method" panel. 2. The software will display a main canvas that displays a sequential list of "form pages". 3. The software will allow each "form page" to display only a single data field. 7

8 Test Method 4. The software will allow an "AltInput" icon to be dragged into a "Form page" to allow for the use of an alternative form of input. 5. The software will set the "Form page" entry method when the entry method is dragged over. 6. The software will display the page number on the bottom right corner of each "form page". - Select the entry method panel and check to see if all of the input methods are listed there. - Select the main menu and make sure that all of the forms are presented there. - Select a form page and check to see if there is at least one data field. - Drag the Alt-Input icon onto a new form. - Drag a specified entry type onto a field. - Open a form and look for a page number in the bottom right hand corner. - All entry methods should be displayed. - All forms should be displayed. - Selected form should contain visible data fields. - The Alt-Input icon should move to the form it is dragged to. - The entry type that is dragged onto a field should be the entry type accepted. - Pages numbers should be listed on the page in the bottom right hand corner. Requirement (s) , Sub Requirements , , , , , , , Description Editing Existing Forms 1. The software will allow the "AltInput" option to be changed when the option is selected. 2. The software will change the option when the Change button is selected. 3. The software will allow pages to be moved up or down in the total sequence. 4. The software will allow pages to be removed from the total sequence. 5. The software will show a confirmation popup when the page is to be changed in the sequence or removed. 6. The software will be able to save the "Form project" to a.form file. 7. The software will be able to load a previously saved.form file into the project. 8. The software will allow each field to have a validation method. Test Method - Select the Alt-Input Option. - Select the Change Option. - Move Pages up and down. - Remove a page from the form. - Remove a page or change it in the sequence and accept it on the pop-up. 8

9 - Save the form. - Load a form file. - Check all validation methods in all fields. - The Option button should open up all of the input methods. - The input method is changed. - Pages should be moved in the correct direction. - Confirmation of the page being removed or changed in the sequence should be displayed. - Page will be removed. - A.form file should be created. - The respective form should be loaded. - All fields will be validated. 4.3 Form Browser Requirement (s) Description The software will show a welcome screen that displays a user-set logo when the application starts. Test Method 1. Open the application. - The welcome screen will be displayed. Requirement (s) Description The software will present the user with the "Start new Session" and "Open old Session" buttons. Test Method - Open the application and wait for the welcome screen to pass. - The open old session and start new session will be displayed. Requirement (s) Description The software will allow the user to search for the form title that is entered in the search field. Test Method - Enter the name of the form in the search. - The searched for form is displayed or the user is notified that the form is not valid. Requirement (s) Description The software will display a list of form types when the "Start new Session" button is pressed which will be clickable buttons. Test Method - Click start new session. - Buttons of all form types will be presented. Requirement Description The software will display a list of previously internally saved sessions that will be clickable buttons when the "Open Old Session" button is clicked. 9

10 Test Method - Click Start new Session. - New forms as well as recently edited local forms will be displayed for selection. Requirement (s) Description The software will display the last used "Form" at the top of the session display. Test Method - Open the application and look at the session display. - The most recently used form will be displayed at the top of the application. Requirement (s) Description The software will allow the user to search for a form with a full world search feature. Test Method - Select the Search Option and enter a form name. - The form that was searched for is displayed or the user is notified that the form is not valid. Requirement (s) Description The software will render each "Form page" on a single screen display. Test Method - Select a form. - The form will be displayed as one page. Requirement (s) Description The software will allow the forward button to be double clicked to jump two pages ahead. Test Method - Click the forward button. - Double Click the forward button. - The form will advance one page. - The form will advance two pages. Requirement (s) Description The software will go back to the previous page when the back button is clicked, and go ahead one page when the forward button is clicked. Test Method - Click the back button. - Double Click the back button. - The form will go back one page. - The form will go back two pages. Requirement (s) Description The software will display the page number at the bottom of the screen. Test Method - Check the bottom of the screen for the page number. 10

11 - The page number must be present. Requirement (s) Description The software will skip pages which have no fields to fill in (pre-filled). Test Method - Select a page with information that has no fields or automated fields. - The page should be skipped. 4.4 Archiving Requirement (s) Description The software will save the form session into a.form file after each page is filled. Test Method - Fill in a page. - The file will be saved. Requirement (s) Description The software will store all of the.form files in a "forms" folder on the device. Test Method - Save a form. - The file will be stored in the forms folder. Requirement (s) Description The software will store the user's current page number when in the.form file. Test Method - Save a form. - The page number will be stored. Requirement (s) Description The software will proceed to the.form page number when a form is reopened. Test Method - Open a form file. - The file will open on the last page that was worked on. 4.5 Form Submission Requirement (s) Description The software will present the user with a confirmation window when a form is completed. Test Method - Complete a form. - A confirmation window will appear. Requirement (s)

12 Description Test Method The software will not submit the form when the cancel button is clicked. - Click the cancel button. - The user will be returned to the form. Requirement (s) Description The software will submit the form to headquarters when the OK is clicked. If an internet connection is not available the form will be stored until it is able to be submitted at a later time. Test Method - Click OK - The form will be submitted if there is a valid connection or stored to be submitted later. 4.6 Deployment Requirement (s) Description The form generation software will be installed with a Windows installer. Test Method - Run the installer - The program will be installed using a Windows installer. Requirement (s) Description The form generation software will be added into the Start Menu. Test Method - Install the software - The icon should appear in the start menu once the installation is complete. 4.7 Security Requirements Requirement (s) 3.3 Description To ensure that each form comes from the person that we originally intended to fill it out, there will be two things we will do. We will send the MAC address of the device and each form will have a signature field. Test Method - Submit a form - Enter a valid electronic signature - The MAC address and signature will be checked to validate the forms origination point. 4.8 Form Browser User Interface Requirement (s) Description Welcome Screen The screen will contain the following elements: The logo and three buttons (open new case, load old case, and exit). 12

13 Test Method - Open the application. - The welcome screen with the options listed above should be present. Requirement (s) Description Opening a Form File a opens up a new window with a list of buttons that each opens a different form. Test Method - Open a form file. - A page will be displayed with a window that has a list of buttons on it. Requirement (s) Description Forms On each form page there are the following buttons: Home, Forms, Back, Forward and Exit. Also within the form body there should be fields, a signature area, a submit button and a save button. Test Method - Open a form or create a new form. - The page should display the appropriate buttons and features as listed above. 4.9 Form Generation User Interface Requirement (s) Description The main user interface is the first screen that will be displayed when the application is launched, see (figure 10) for the illustration. Test Method -Open the form generation application. - The appropriate buttons and features should appear as guided by the figure 10 of the SRS. - The application should contain a toolbar, two tabs, and multiple buttons. Requirement (s) Description Toolbar - The toolbar is located at the top left of the main interface. - The toolbar contains the following four menu items: File, Views, Format, and Help, see (figure 10) to see all these option expand. - The File menu consists of the following six options to choose from: Create New Form, Open Form, and Save Form, Save as, Most Recently Used, and Exit option. Views - The File view menu consists of the following three options to choose from: General, Mobile and Device view. Android view see (figure 9). - The Format tab consists of the following three options to choose from: Font, Layout and Background. - The Help tab displays the information about the software version and developers. 13

14 Test Method - Open the form generation application and click on the toolbar. - Open the form generation application and look at the different available views. -The above listed features should be included on the toolbar. Requirement (s) Description Tabs - The tab is located at the right of the main interface. - The tab consists of two elements. Control - The control tab contains a list of items that allow the user to drag and drop things in the form field. It consists of GPS, Voice Recognition, Image scanning, Handwriting Recognition, Text box, Rich text box, Drop-Down List Box, Combo Box, Date Picker, Check box, table, and section. - The Data Source Tab will allow the user to change some settings on the input data in to the form. Test Method -Open the form generation application and click on the tabs. -The above listed features should be included in the tabs. Requirement (s) Description Buttons - There are a total of four buttons to help the user move the form around. - The Delete Slide button will delete the current form from the application; the program will ask the user to save the form, if the form is not a blank. - The Add New Slide button will add a new slide to the current form on the application. - The << button will allow user go back to the previous slide of the form. - The >> button will allow user go to the next slide of the form. Test Method - Open the form generation application and click on the buttons and examine their layout. - The above listed features should be included in the buttons. 14

15 Test Log Instructions Read section 5 of the Acceptance Test Plan for recommended testing procedures. If the test passes, fill out the 'Date of Test Pass' column. If necessarily, write additional comments in 'Comments' section. Any additional issues identified that is not fit a requirement should be added to the 'Open Issues' section. Requirement Date of Test Pass Comments

16 Open Issues Issue Comments Additional Comments Document Sign Off By signing this document, you verify that the NGForms system is acceptable for use. X Clifton Salas American Red Cross 16 X Hung Dinh Project Lead