Quality Assurance Testing Lifecycle Process

Start of the Workflow/Process.

Retrieve the approved Test Plan entry from the Test Management data model.

Create a new Test Cycle entry to track the current testing execution period.

Retrieve all Test Case entries associated with the specific Test Plan.

Create a task for the QA Engineer to begin executing the identified test cases.

Update the status of individual Test Case entries to 'In Progress' or 'Passed/Failed'.

Create a new Defect/Bug entry when a test case fails.

Create a task for the Developer to investigate and resolve the logged defect.

Update the Defect entry status to 'Resolved' once the fix is implemented.

Retrieve the linked Defect entry to trigger re-testing.

Create a task for QA to perform regression testing after the bug fix is deployed.

Aggregate Test Case entries to calculate the percentage of passed vs. failed tests.

Aggregate Defect entries to count the total number of open vs. closed bugs.

Execute a formula comparing executed test cases against total planned test cases.

Create a summary report containing the aggregated pass/fail metrics and defect counts.

Send an email to the Project Manager and Product Owner if the failure rate exceeds a threshold.

Send an email to the Release Manager when the Test Cycle is marked as 'Completed'.

Update the Test Cycle entry status to 'Closed' or 'Finished'.

Delete any temporary or draft Test Case entries that were not part of the official execution.

End of the Workflow/Process.