1 / 1

User Acceptance Test Cases

QA Process – Ensuring Quality in caBIG Products Steve Hunter[1], Cliff Wong[2], Ye Wu[3], Tom Boal [4] [1] Ekagrasoft [2]NCICB [3]SAIC [4] NARTech. User Acceptance Testing. Ekagra. Production. Overview

duc
Download Presentation

User Acceptance Test Cases

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. QA Process – Ensuring Quality in caBIG Products Steve Hunter[1], Cliff Wong[2], Ye Wu[3], Tom Boal[4] [1] Ekagrasoft [2]NCICB [3]SAIC [4]NARTech User Acceptance Testing Ekagra Production Overview The caBIG’s Software Quality Assurance (QA) process starts at the inception of a project and continues all the way through the Software Development Life Cycle until the release of the application. During this life cycle, QA reviews requirements for testability, develops a test plan, writes test cases, and executes the plan. We also validate the installation process, ensure adherence to the internal technology stack, and ensure 508 (Disabilities Act) and 21 CFR Part 11 (electronic records and signatures) compliance. Additional Details Test Plan – The QA team writes the Test Plan by using the Scope Document. Use Case/Requirement Review – Requirements are reviewed by QA to make sure they provide sufficient details to write thorough test cases. Document/Code Reviews – QA ensures reviews are completed on code and other deliverables. Approval sections of documents track the reviews. Test Execution – The Test Plan is implemented and results are tracked and reviewed. Stage Testing – QA executes a small set of tests that touch major functionality (Smoke Test). UAT –The end user executes the UAT tests then provides feedback to the QA. End Users QA Team Go No Go Decision User Acceptance Testing (UAT) Diagram of Project Flow Test Plan Scope Document Scope Document • Outlines features for next release System Test Plan • Approach • Features to be tested • Features not to be tested • Responsibilities • Resources required • Schedule • Risks and contingencies System Test Plan Stage • Permission to proceed to Stage • Stage is built and deployed • Smoke Test Stage tier Stage Testing Production User Acceptance Test Plan Stage Testing • Same as above User Acceptance Test Plan • Same as above Use Case/Requirement Review Use Case/Requirement Review Use Case Document • Criteria • Complete • Correct • Unambiguous • Consistent • Non-compound Execute the Test Plan Document/Code Reviews Test Execution • Execution of Integration and System Testing • Post Defects in GForge Bug tracker • Triage defects Integration & System Testing Reviews System Test Cases Test Cases User Acceptance Test Cases • DEV team fixes defect • QA Verify fixes • Process Improvement/Defect Reduction • Regression Test

More Related