Task: Execute Testing
Perform the planned testing activities to test the solution. Types of testing include Systems Integration Testing (SIT), Regression, and User Acceptance Testing (UAT).
Disciplines: Quality Management Discipline
Purpose

To:

  • Ensure that all related systems exchange data seamlessly, verifying a system’s ability to operate as expected with other systems within the same environment.
  • Ensure that new code changes have not introduced any new defects and the end-to-end system functionality is working as per the expectations.
  • Provide confidence that the delivered system meets the business requirements of both sponsors and users.
  • Properly account for, track and providing status updates and reporting on all defects found during testing cycles.
Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory:
    		Optional:
    • None
    Outputs
      Main Description

      Systems Integration Testing (SIT) requires close coordination across all applications to ensure that all systems have been integrated successfully. This is done by verifying the cross application/system data transfers and subsequent functionality of each application/system have produced the expected results.

      Regression Testing is performed to ensure that existing functionality of application is working as expected and new changes have not introduced any new defects.

      User Acceptance Testing is conducted by a select group of business user to ensure that the delivered system meets the approved business requirements and functions as expected. Upon completion it is expected that approval/signoff will be given by the Business Owner and the Sponsor. The UAT phase may also act as the final quality gateway, where any quality defects not previously detected may be uncovered. QA will assist in UAT activities as needed.

      All defects will be maintained in the Test Management Tool and reported to the project team throughout the project lifecycle. The defect metrics are captured and reported on the QA Standard Dashboard. The QA Lead can produce a detailed defect log, for the project team as needed.

      The TMT captures various details of the defect including:

      • Detected on Date
      • Detected By
      • Status
      • Severity
      • Description
      • Reproducible
      • Subject
      • Responsible Tester
      • Assigned To
      • Vendor Tracker - if 3rd party tracking system is used
      • Priority
      Steps
      Previous test results

      When appropriate, obtain test results from the previous test cycle. For example, if conducting regression testing, obtain testing results from Systems Integration (SIT) testing.

      This may involve obtaining confirmation from the development team that all the code changes are delivered to QA and the QA environment can be locked down from accepting any further changes.

      Conduct testing

      Using previously developed test cases and test scenarios, execute testing on software.

      A pre-defined set of test cases will be executed as part of testing to cover the new system functionality, and/or end-to-end system functionality.

      In the case of User Acceptance Testing, the Application owner is responsible for identifying the testing resources, developing, and executing test cases.

      Create defect report

      Defects will be logged if any test case fails or if unexpected behavior or functionality is noticed. Defects will be reviewed and prioritized on a regular basis.

      It is Business or BA’s responsibility to prioritize and/or defer any defects coming out of Systems Integration Testing (SIT)/Feature, Regression, and User Acceptance Testing (UAT) testing phases.

      QA team has the ability to enter defects directly into the TMT.

      Other members of the project team involved in testing will report their defects by documenting on the Defect Report Template, and forwarding the template to the QA lead

      The QA lead will upload the Defect Report Template to the TMT as needed

      More Information
      Guidelines

      Version and Release

      Unified Life Cycle (ULC): 5.1, November 3, 2014
      Phase Gates: 1.1, May 27, 2014
      Process Engineering Process (PEP): 1.1, May 27, 2014