Acceptance Test Plan For HCDocs Version 1.0 Prepared by: Somil Parikh Min Yaung Dhruv Salhotra Gregory Bajgier Bernard Wolff Drexel University
Document Information Title Authors Reviewers Healthcare Document Management Acceptance Test Plan Somil Parikh, Min Yaung, Dhruv Salhotra, Gregory Bajgier, Bernard Wolff Jeff Salvage, Somil Parikh, Min Yaung, Dhruv Salhotra, Gregory Bajgier, Bernard Wolff Revision History Name Jeff Salvage, Somil Parikh, Min Yaung, Dhruv Salhotra, Gregory Bajgier, Bernard Wolff Date November 22, 2007 Reason for Changes Initial Version Version 1.0
1 Introduction 1.1 Background This document provides a series of test required to perform for the Acceptance Test Plan of HCDocs. HCDocs is a document management system which electronically stores, organizes and manages healthcare documents and provides fast, security-controlled access to the patients documents within the University of Pennsylvania Health System. The greater details about the HCDocs are described in the Software Requirements Specification for HCDocs. 1.2 Structure of the Document Section 1 - Section 2 - Section 3 - Section 4 - Section 5 - Section 6 - Describes the introduction and the structure of the document Describes the overall approach to the Acceptance Test Plan process Describes in more details individual issues covered or not covered in the Acceptance Test Plan Describes the criteria which have to be satisfied for the Acceptance Test Plan Describes the roles and responsibilities of the project members involved in the Acceptance Test Plan Describes the test cases used during the Acceptance Test Plan 1.3 References Software Requirements Specification for HCDocs 1.4 Definitions, Acronyms, and Abbreviations Project Leader - Client s Representatives - The person in charge of the entire project. Client s Representatives are people who overlook the Acceptance Test Plan execution on behalf of the customers. Software Requirements Specification - A Software Requirements Specification is a document which describes the behavior of a system. Function Requirements - Unit Tests - Integration Test - Functional Requirements define the internal workings of the software. A procedure in the software development process to validate individual modules and other units of source code are working properly. Integration Test is a test Phase which is employed after the Unit Tests are validated and how all the different
modules of a software system fit and interact with each other. System Test - System Test is conducted after Integration Test has been conducted to evaluate the system s compliance with its specified requirements. 2 Test Approach and Constraints 2.1 Introduction This section describes the overall approach, particular techniques and testing tools that will be used during the Acceptance Test Plan of the HCDocs. 2.2 Test Objectives The Acceptance Test Plan process will assist the client to evaluate HCDocs and verify whether it performs in accordance with the client s requirements listed in the Software Requirements Specification. 2.3 Test Structure The Acceptance Test Plan will consist of a subset of test cases and methods that previously used when performing the Unit Tests, Integration Test and System Test on the HCDocs system. The test cases will be carefully selected and agreed upon by both the developer and the client, and will allow for the most adequate verification of the functional requirements as list in the Software Requirement Documents of the HCDocs without the extensiveness of the full-scale System Test. It is essential that all appropriate Unit Tests, Integration Test and the System Test were successfully performed for HCDocs prior to the Acceptance Test Plan and their results were reported to the client. 3 Test Assumptions and Exclusions 3.1 Introduction This section provides greater details about the issues and features of HCDocs that will be covered or not covered by the Acceptance Test Plan process. 3.2 Assumptions It is assumed that all issues covered by the Acceptance Test Plan were also previously addressed by the Unit Tests, Integration Test and System Test of HCDocs. The Acceptance Test Plan cover
The functional requirements of the system listed in the Software Requirements Specification Usability of the HCDocs system Consistency of the user related system documentation 3.3 Exclusions It is assumed that all issues not covered by the Acceptance Test Plan were previously addressed by Unit Tests, Integration Tests and System Tests of HCDocs. The Acceptance Test Plan does not cover The non-function requirements of the system listed in the Software Requirements Specification Structural integrity of the source code 4 Entry and Exit Criteria 4.1 Introduction This section lists the criteria which must be satisfied in order for the Acceptance Test Plan to begin, as well as the criteria which must be satisfied in order for the Acceptance Test Plan to stop. 4.2 Entry Criteria The Acceptance Test Plan can be initiated after the following preconditions are met HCDocs has successfully undergone Unit Tests, Integration Test and System Test. The testing environment which satisfies the System Requirements of Software Requirements Specification has been setup and inspected by the client s representative. A copy of the latest version of the Software Requirements Specification has been received A copy of the latest version of the user-related documentation has been received The latest released version of HCDocs has been appropriately resourced. Consent of the project leader has been obtained. Consent of the client has been obtained. 4.3 Exit Criteria The Acceptance Test Plan should be halted after either of the following All Priority 1 requirements were tested without any deviation from expected behavior. (Success) At least one Priority 1 requirement deviated from the documented specification. (Failure)
By mutual agreement between Client s Representative and the Tester, in which both parties supervisors should be notified and the Acceptance Test Plan should be rescheduled for a later date. (Failure) 5 Testing Participants 5.1 Introduction This section describes the roles and responsibilities of the staff members involved in the Acceptance Test Plan, as well as the procedure of reporting the test results and any problems that came up during testing. 5.2 Roles and Responsibilities For the Acceptance Test Plan the following roles were assumed by the following people Test Team Leader: Somil Parikh Client s Representative: A person in charge from the client s side who will overview the testing process. Tester: A person who will execute the use case tests. 5.3 Training Requirements All parties involved in the Acceptance Test Plan should be familiar with the use interface of HCDocs, as well as the system documentation and the Software Requirements Specification. 5.4 Problem Reporting Any problem pointed out by either the Client s Representative or the Tester must be documented and reported to the Project Leader and addressed during a periodic or urgent project members meeting depending on the severity of the problem. 5.5 Process Reporting The Acceptance Test Plan report will be complied once after testing process is finished by the project members and submitted to the Project Leader.
6. Testing Project Test Case 6.1 Introduction The test cases are distributed in sections covering functionality elements and use cases in the Software Requirements Specification. Each of the following test cases is in the format Name - The name of the test case - Conditions needed to initiate the test case The actions expected form a tester Post Conditions The expected outcome of the test case 6.2 Test Cases for All Users The following test cases are for all user accounts. 6.2.1 Start Up The tester has OpenOffice.org and HCDocs system installed on the computer The tester starts the Open Office program The tester is presented with the startup page which is a blank OpenOffice.org writer with the HCDocs icons on the tool bar 6.2.2 Logging in Correct username and password The tester has a login window opened by clicking on the HCDocs button on the tool bar The tester enters correct username and password in the appropriate fields and submits for verification The tester is logged into the HCDocs system. Incorrect username or password The tester has a login window opened by clicking on the HCDocs button on the tool bar The tester enters either correct username and incorrect password or incorrect username and correct password in the appropriate fields and submits for verification The verification is failed and tester is not logged into the HCDocs system. A message box will pop up and say Incorrect username or password.
Incorrect Username and Password The tester has a login window opened by clicking on the HCDocs button on the tool bar The tester enters incorrect username and password in the appropriate fields and submits for verification The verification is failed and tester is not logged into the HCDocs system. A message box will pop up and say Incorrect username or password. 6.2.2 Main Window The tester has logged into the HCDocs system None The tester is presented with the main window with the New, Open, Save, Search and Logout buttons at the tool bar 6.2.3 New Document Creating a new Document The tester is at the Main Window The tester clicks on the New button on the tool bar The tester is presented with a wizard that guides them in creating a new document. The first page of the wizard screen shows up and asks the user to select a template. Selecting a Template If the tester clicks on next without selecting a template The tester is at the select template page in the new document wizard. The tester clicks on one of the following options: Reset Next Reset The screen is refreshed and all selected items will be set back to the default selections. Next If there is no template is selected a message box pop up and say, Please select a template to continue. If the tester clicks on next after selecting a template
The tester is at the select template page in the new document wizard. The tester select one of the available templates and then select one of the following options: Reset Next Reset The screen is refreshed and all selected items will be unselected. Next The tester is taken to the Select Patient screen. Selecting a Patient If tester clicks on Find Patient without entering any search fields The tester is at the Select Patient screen in the new document wizard The tester clicks on Find Patient. The tester is presented with an error message asking them to enter at least one field to complete a search. The tester clicks on Find Patient after entering one valid field and leaving the rest of the fields blank. The tester is at the Select Patient screen in the new document wizard. The tester enters one valid field, leaves the rest of the fields blank and clicks on Find Patient. The tester is presented with the patient s information on the same screen if there is only one matching record. If there is more than one matching record, the tester is presented with a list of patients who matched the search criteria. The tester clicks on Find Patient after entering more than one valid field and leaving the rest of the fields blank. The tester is at the Select Patient screen in the new document wizard. The tester enters more than one valid field, leaves the rest of the fields blank and clicks on Find Patient. The tester is presented with the patient s information on the same screen if there is only one matching record. If there is more than one matching record, the tester is presented with a list of patients who matched the search criteria. The tester clicks on Find Patient after entering one or more invalid fields.
The tester is at the Select Patient screen in the new document wizard. The tester enters one or more invalid fields and clicks on Find Patient. The tester is presented with an error message, no matching record found according to the search criteria. The tester clicks on Find Patient after entering one valid field and one invalid field. The tester is at the Select Patient screen in the new document wizard. The tester enters one valid field, one invalid field and clicks on Find Patient. The tester is presented with an error message, no matching record found according to the search criteria. The tester clicks on Next after successfully selecting a patient from database. The tester is at the Select Patient screen in the new document wizard and the desired patient s information is displayed in an uneditable format. The tester selects one of the following options: Reset Back Next Reset The page is refreshed and the search criteria and patient information are cleared from the screen. Back The tester is taken to the Select Template screen. Next The tester is taken to the Select Physician screen. The tester clicks on Next without selecting a patient from database. The tester is at the Select Patient screen in the new document wizard and the desired patient is not selected. The tester selects one of the following options: Reset Back Next Reset The page is refreshed and the search criteria and patient information are cleared from the screen. Back The tester is taken to the Select Template screen. Next A message box will pop up on the screen and say Patient is not selected.
Selecting a Physician If tester click on Find Physician without entering any search fields The tester is at the Select Physician screen in the new document wizard The tester clicks on Find Physician. The tester is presented with an error message asking them to enter at least one field to complete a search. The tester clicks on Find Physician after entering one valid field and leaving the rest of the fields blank. The tester is at the Select Physician screen in the new document wizard. The tester enters one valid field, leaves the rest of the fields blank and clicks on Find Physician. The tester is presented with the physician s information on the same screen if there is only one matching record. If there is more than one matching record, the tester is presented with a list of physicians who matched the search criteria. The tester clicks on Find Physician after entering more than one valid field and leaving the rest of the fields blank. The tester is at the Select Physician screen in the new document wizard. The tester enters more than one valid field, leaves the rest of the fields blank and clicks on Find Physician. The tester is presented with the physician s information on the same screen if there is only one matching record. If there is more than one matching record, the tester is presented with a list of Physicians who matched the search criteria. The tester clicks on Find Physician after entering one or more invalid fields. The tester is at the Select Physician screen in the new document wizard. The tester enters one or more invalid fields and clicks on Find Physician. The tester is presented with an error message saying that no matching record found according to the search criteria. The tester clicks on Find Physician after entering one valid field and one invalid field. The tester is at the Select Physician screen in the new document wizard. The tester enters one valid field, one invalid field and clicks on Find Physician. The tester is presented with an error message saying that no matching record found according to the search criteria. The tester clicks on Next after successfully selecting a Physician from database.
The tester is at the Select Physician screen in the new document wizard and the desired Physician s information is displayed in an uneditable format. The tester selects one of the following options: Reset Back Next Reset The page is refreshed and the search criteria and Physician information are cleared from the screen. Back The tester is taken to the Select Patient screen. Next The tester is taken to the new document with Physician and physician data pre filled in their desired template. The tester clicks on Next without selecting a Physician from database. The tester is at the Select Physician screen in the new document wizard and the desire Physician is not selected. The tester selects one of the following options: Reset Back Next Reset The page is refreshed and the search criteria and Physician information are cleared from the screen. Back The tester is taken to the Select Patient screen. Next A message box will pop up on the screen and say Physician is not selected. 6.2.4 Save Document The tester is at the New Document Window The tester clicks on the Save button at the tool bar The tester is presented with a window which will verify that they want to save. The file will be saved to the system once the user clicks, ok. 6.2.5 Open Document The tester is at the Main Window The tester clicks on the Open button at the tool bar The tester is presented with a wizard that guides the tester to search a
document in the database. The steps include 1. Search the document that the tester wants to open using patient id, date of birth, patient s first and last name, physician id, physician s first and last name, a range of created dates and modified dates. 2. If the returned document lists are associated with multiple, the next window will display a list of patients. The tester can click on the patient name to get the list of documents associated with that patient. 3. If the returned document lists are associated with only one patient, the next window will display the entire list of search result. Searching a document (If tester click on Search without entering any search fields) The tester is at the Open Document screen in the open document wizard The tester clicks on Search. The tester is presented with an error message asking them to enter at least one field to complete a search. The tester clicks on Search after entering one valid field and leaves the rest of the fields blank. The tester is at the Open Document screen in the open document wizard. The tester enters one valid field, leaves the rest of the fields blank and clicks on Search. The tester is presented with the document s information on the same screen if there is only one matching record. If there is more than one matching record, the tester is presented with a list of patients who matched the search criteria. The tester clicks on Search after entering more than one valid field and leaves the rest of the field blank. The tester is at the Open Document screen in the open document wizard. The tester enters more than one valid field, leaves the rest of the fields blank and clicks on Search. The tester is presented with the patient s information on the same screen if there is only one matching record. If there is more than one matching record, the tester is presented with a list of patients who matched the search criteria. The tester clicks on Search after entering one or more invalid fields. The tester is at the Open Document screen in the open document wizard. The tester enters one or more invalid fields and clicks on Search. The tester is presented with an error message saying that no matching record found according to the search criteria. The tester clicks on Search after entering one valid field and one invalid field. The tester is at the Open Document screen in the new document wizard. The tester enters one valid field, one invalid field and clicks on Search.
The tester is presented with an error message saying that no matching record found according to the search criteria. The tester is at the Open Document screen in the open document wizard. The tester selects one of the following options: Reset Search Reset The page is refreshed and the search criteria are cleared from the screen. Search The tester is presented with the patient s information on the same screen if there is only one matching record. If there is more than one matching record, the tester is presented with a list of patients who matched the search criteria. 6.2.6 Admin Logging in Correct username and password The tester has HCDocs system administrator program installed on the computer, has the program started and the login window opened The tester enters their correct username and password in the appropriate fields and submits for verification The tester is logged into the Administrative module for the HCDocs System. Incorrect username or password The tester has HCDocs system administrator program installed on the computer, has the program started and the login window opened The tester enters either incorrect username and password in the appropriate fields and submits for verification The verification is failed and tester is not logged into the HCDocs system. A message box will pop up and say Incorrect username or password. Correct username but incorrect password The tester has a login window opened by clicking on the HCDocs button on the tool bar The tester enters correct username and incorrect password in the appropriate fields and submits for verification The verification is failed and tester is not logged into the HCDocs system. A
6.2.2 Admin Main Window message box will pop up and say Incorrect username or password. The tester has logged into the HCDocs system administrator program None The tester is presented with the main window which allows the tester to select the following options. 1. Manage Users Account 2. Manage Documents 3. Mange Templates 4. Logout 6.2.2 Manage Users Window The tester is at the Administrator Main Window The tester select the Manage Users Account option The tester is presented with the Manage Users window which allows the tester to select the following options. 1. Add Users 2. Modify/Remove Users 6.2.7 Add Users The tester is at the Manage Users Window The tester select the Add Users option The tester is presented with a form which allows the tester to add a new HCDocs system user. After the tester enters the users information in the appropriate field and clicks on Add button, the information will be validated to make sure the username is unique and other information is in the correct format. After the validation is successful, the new user will be added to the system. Adding a user (If tester click on Add User without entering all required fields) The tester is at the Add User screen. The tester clicks on Add User without entering all required fields. The tester is presented with an error message asking them to enter all required fields in order to add a new user. The tester clicks on Add User after entering all required fields. The tester is at the Add User screen. The tester clicks on Add User after entering all required fields. The tester is presented with a window which confirm that the user was successfully added to the HCDocs system. The username already exist in the system. The tester is at the Add User screen.
The tester clicks on Add User after entering all required fields but the username already exist in the system. The tester is presented with an error message asking them to enter a different username in order to add a new user. The user with the same first and last name already exists in the system. The tester is at the Add User screen. The tester clicks on Add User after entering all required fields but the user with the same first and last name already exists in the system. The tester is presented with an error message stating that the user with the same first and last name already exist in the system. Add User Window The tester is at the Add User screen. The tester selects one of the following options: Reset Back Next Reset The page is refreshed and all fields are cleared. Back The tester is taken to the HCDocs Manage User Window. Next The tester is presented with a window which confirms that the user was successfully added to the HCDocs system. 6.2.8 Remove Users The tester is at the Manage Users Window The tester selects the Modify/Remove Users option The tester is presented with a wizard which guides them to remove a user from the HCDocs system. The steps include: 1. Find a user in the system by using the username, user s first and last name, user s e-mail and user s primary department 2. The tester is presented a window with a list of users name and their related information those matched to the search criteria and the tester will able to select the users that he/she wish to remove from the system and click on the Remove User button. The removed user will be set to be disabled and the removed users will no longer have access to the HCDocs system. 6.2.9 Modify Users The tester is at the Manage Users Window The tester select the Modify/Remove Users option
The tester is presented with a wizard which guides the tester to modify a user credential in the HCDocs system. The steps include 1. Find a user in the system by using the username, user s first and last name, user s e-mail and user s primary department 2. The tester is presented a window with a list of users name and their related information those matched to the search criteria and the tester will able to select the users that he/she wish to modify and click on the Modify User button. 3. The tester is presented a window with the selected user s information and the tester will be able to modify the appropriate fields that he/she wish to modify and click on save button to save the new updated user information Finding a user (If tester click on Find User without entering any fields) The tester is at the Find User screen. The tester clicks on Find User without entering any fields. The tester is presented with an error message asking them to enter at least one field to complete a search. The tester clicks on Find User after entering one valid field and leaves the rest of the fields blank. The tester is at the Find User screen. The tester enters one valid field, leaves the rest of the fields blank and clicks on Find Physician. The tester is presented with the user s information on the next screen if there is only one matching record. If there is more than one matching record, the tester is presented with a list of users who matched the search criteria. The tester clicks on Find User after entering more than one valid field and left the rest of the field blank. The tester is at the Find User screen. The tester enters more than one valid field, leaves the rest of the fields blank and clicks on Find Physician. The tester is presented with the user s information on the next screen if there is only one matching record. If there is more than one matching record, the tester is presented with a list of users who matched the search criteria. The tester clicks on Find User after entering one or more invalid fields. The tester is at the Find User screen. The tester enters one or more invalid fields and clicks on Find User. The tester is presented with an error message saying that no matching record found according to the search criteria.
The tester clicks on Find User after entering one valid field and one invalid field. The tester is at the Find User screen. The tester enters one valid field, one invalid field and clicks on Find User. The tester is presented with an error message saying that no matching record found according to the search criteria. The tester clicks on Remove or Modify user after successfully selecting a user from database. The tester is at the Modify User screen in the modify user wizard and the desired user s information is displayed in an un-editable format. The tester selects one of the following options: Back Remove User Modify User Back The tester is taken to the Manage User Window. Remove User If a check box next to the user list is selected, a pop up window will be presented to the tester to confirm the removal of the selected user from the system. The system will just disable the user s account. It will not entirely remove the user from the system. Modify User If a check box next to the user list is selected, the tester will be presented with the next window which will display the detail information about the user and the tester will be able to modify the user s information in the text box. The tester clicks on Remove or Modify User after successfully selecting a user from database. The tester is at the Select Physician screen in the new document wizard and the desire Physician is not selected. The tester selects one of the following options: Back Remove User Modify User Back The tester is taken to the Manage User Window. Remove User If a check box next to the user list is not selected, a pop up window will presented to the tester and say Select a user which you want to remove. Modify User If a check box next to the user list is not selected, a pop up window will presented to the tester and say Select a user which you want to modify.
6.2.7 Reset Password The tester is at the Modify User Window The tester clicked on the Reset Password button A new password is randomly generated and e-mailed to the selected user and the tester is presented with a window which confirms that the password was sent to the user. After the tester does the desired modification to the user information. The tester is at the Modify User screen and made the desired modifications to the user information. The tester selects one of the following options: Reset Back Save Reset Password Reset The page is refreshed and all fields are cleared. Back The tester is taken to the previous searched user list. Save The modified user information will be saved to the system. Reset Password - A new password is randomly generated and e-mailed to the selected user and the tester is presented with a window which confirm the tester that the password was sent to the user. 6.2.10 Manage Documents The tester is at the Administrator Main Window The tester select the Mange Documents option The tester is presented with a wizard which guides the tester to search a document in the database. The steps include 1. Search the document that the tester wants to modify using patient id, date of birth, patient s first and last name, physician id, physician s first and last name, a range of created dates and modified dates. 2. If the returned document lists are associated with multiple, the next window will display a list of patients. The tester can click on the patient name to get the list of documents associated with that patient. 3. If the returned document lists are associated with only one patient, the next window will display the entire list of search result. 4. The tester can click on the document name that he/she wish to modify and he/she can change the document id, name, status, department, lock/unlock and remove/restore the selected document. Searching a document (If tester click on Search without entering any search fields)
The tester is at the Open Document screen in the manage document wizard The tester clicks on Search. The tester is presented with an error message asking them to enter at least one field to complete a search. The tester clicks on Search after entering one valid field and left the rest of the field blank. The tester is at the Open Document screen in the manage document wizard. The tester enters one valid field, leaves the rest of the fields blank and clicks on Search. The tester is presented with the document s information on the same screen if there is only one matching record. If there is more than one matching record, the tester is presented with a list of patients who matched the search criteria. blank. The tester clicks on Search after entering more than one valid field and left the rest of the field The tester is at the Open Document screen in the manage document wizard. The tester enters more than one valid field, leaves the rest of the fields blank and clicks on Search. The tester is presented with the patient s information on the same screen if there is only one matching record. If there is more than one matching record, the tester is presented with a list of patients who matched the search criteria. The tester clicks on Search after entering one or more invalid fields. The tester is at the Open Document screen in the manage document wizard. The tester enters one or more invalid fields and clicks on Search. The tester is presented with an error message saying that no matching record found according to the search criteria. The tester clicks on Search after entering one valid field and one invalid field. The tester is at the Open Document screen in the new document wizard. The tester enters one valid field, one invalid field and clicks on Search. The tester is presented with an error message saying that no matching record found according to the search criteria. The tester is at the Open Document screen in the manage document wizard. The tester selects one of the following options: Reset Search Reset The page is refreshed and the search criteria are cleared from the screen.
Search The tester is presented with the patient s information on the same screen if there is only one matching record. If there is more than one matching record, the tester is presented with a list of patients who matched the search criteria. 6.2.11 Manage Templates The tester is at the Administrator Main Window The tester select the Manage Templates option The tester is presented with a window which allows him/her to add more templates to current template list which allows user to use or remove from the current template from the list to stop using that template by the users. 6.2.12 Upload Templates The tester is at the Manage Template Window The tester clicked on the Upload New Template button The tester is presented a window which allow user to browse through the computer and select a template and upload new templates in xml format to the HCDocs system.