UMN Testing process: QC Estimation: 80 hours total While testing the R1S release for UMN, below are

the bullet points which we consider while performing testing the application Testing approach Testing process (Form level) Form , workflow, eMails and reports What are the aspects / functionality that is being tested Specific features like Updates view / Related comments / cross module functionality (component wise) Regression testing Integration testing

1. Testing approach: We are differentiating the testing approach in various aspects like functionality working as per spec, Impact analysis, finding complex scenarios and considering performance of the application (Form level and workflow level). Functionality coverage: Taking the requirement docs as base, validating the application in and out. Preparing positive and negative test scenarios and test cases. Impact analysis: Identifying dependent areas / sections in form and work flow level. For eg. Cross checking whether linear view applied to existing IACUC form, Print view of all the forms. Direct Impact/changes Indirect

Performance: Calculating the time taken to load each section in IACUC form. 2. Testing process: Verifying IBC and CS forms: Validating form, considering existing functionality like, Page CFC validations, Enablement of sections based on selection in Activities Include section. Generating PDF from Print view, Event History and GetPDF. Validating CFC pop up (Whether impacted the required functionality for IACUC form) Validating View Attachments in Print view pop up Cross checking whether linear format applied for the pop up information Verifying existing IACUC form: Administrative submission functionality should be stayed as is Linear format should not be there for Species, Procedure and Euthanasia sections.

Existing functionality for CFC pop up Generating PDF from Print view, Event History and GetPDF. Text box and text area questions should not accept only special characters as input data.

Verifying IACUC_V2 form: Species section, Procedures and Euthanasia sections should be in linear format. Indentation for each section in CFC pop up PDF from Print view, Event History and GetPDF. Text box and text area fields should not accept only Special characters as input data. Interface of the sections should be as specified in functional design documents

3. Form , workflow, eMails and reports: Form:24 man hours Validation messages (Page and CFC level) Funding section Input data I. Entering Special characters as input data II. Testing the text boxes and text areas by applying boundary value analysis III. Copy and paste the data into the application Cross checking, whether the dependent questions are getting enabled based on the selection of the questions after implementing new requirement (Eg: Post-operative Care questions should be in enable state to answer based on the selection Survival in Surgery section Cross check whether the impacts are applied for Approved forms the Amendment and Continuing review forms (Existing and newly created forms)

Workflow: Meeting agenda Related comments Batch DMR process(1 hour) Panel and Committee members functionality

eMails: Mail should be triggered while submitting the protocol form, to Secondary Investigator and Additional Staff personnel, for whom Copied on email from IACUC? selected as Yes Scheduler mails

Send reminder mail in Meeting Agenda DMR Agenda email

Reports: (10 hours) All the IACUC specific reports Verify whether the data displayed properly in the reports for existing and R1S form Generic report

4. Specific features like Updates view / Related comments / cross module functionality() Updates View(10 hours) UI of the current cycle changes Current response, Previous response and Track change description for Text box / Text area questions For Previous cycle changes, existing functionality should work as is Related comments(8 hours): Follow up comments check box functionality Write comments, Edit, Delete, Save & Add Comment and Show all comments button functionality Reassigning reviewers Notes information in comments page Adding comments to meeting agenda through Cross module functionality(16 hours): Dependency between Planned attendees tab and Meeting attendees tab Default meeting time and location for each panel, based on the configuration Voting information by selected panel members in meeting attendees tab Assigning studies to meeting date without assigning reviewers Actions that can be taken (In meeting agenda) on protocols those are assigned to meeting date without assigning reviewers 5. Regression testing(5 hours) Form submission Return form by Intake coordinator or Panel manager Resubmission of returned protocol Review decision process (DMR process) Assign panel Reassign panel

Assign reviewers Reassign reviewers Comment review cycle process Taking Actions in meeting minutes Creating Amendment and continuing review forms eMails for all events

6. Integration testing On an integrated system, testing will be performed starting with Smoke testing. If the system passes the smoke testing, brief testing will be done before getting into details, keeping in mind critical scenarios for the deliverables in the release.