QA Valley formally records all the individual procedures and steps for each Test Case that is executed as part of a Test Cycle. The recording process may be Video Capture, Screen Capture, and Event Capture, encompassing the entire user interaction with the software or application. The dialogue between user and system includes, but are not limited to keyboard strokes, mouse movement, mouse overs, click events, and other behavior. This granular approach to recording user and system interaction ensures that all Test Case executions are saved for subsequent review.
Test Case Execution Recordings are stored, categorized, and linked back to the respective Test Cases, which simplifies subsequent review and audit following the completion of test cycles. Clients, users, and other QA personnel frequently replay recordings to reconfirm software and application transactions when it is dubious regarding the fulfillment of requirements. Stakeholders can access the recorded test cycle archives to satisfy their curiosity, or to perform random audits as they police the robustness and completeness of the test cycles and enforcement of best QA Practices.
It is a standard practice for QA Valley to store and retain Test Case Execution Recordings for several software versions and releases. In rear instances, it is sometimes necessary to have recordings in the archives that may be traced to legacy generation of the software. This history enables Project Managers and QA Testers to trace the completion of requirements several sprints or software versions backwards. This capability allows stakeholders to retroactively confirm when disputed requirements or defects were first addressed, tested, recorded, and user accepted.
As part of a Project Acceptance and Closure, QA Valley grants remote access to Test Case Execution Recordings, and in cases where access cannot be accommodated, the recordings are transmitted to Clients, Users, and Auditors. This is a standard operating procedure observed in Acceptance and Closure that minimizes or eliminates the possibility of disputes between the original Requirements, Test Cases, and Executed Results. When a project is pronounced Closed, Clients can be certain that they have recorded test cases confirmation the delivery of all user requirements.