Quality Assurance (QA) Testing Workflow

Начало на работния поток/процеса.

Create a new entry in the 'Bugs' data model when a defect is identified.

Update the specific Test Case entry to 'Failed' or 'Passed' based on execution results.

Create a task assigned to the relevant developer to investigate the reported bug.

Retrieve all requirement entries linked to the current Test Suite to ensure coverage.

Execute a formula to calculate the percentage of passed tests vs total tests executed.

Sum the number of 'Critical' and 'High' priority bugs to assess release risk.

Create a high-priority task for the QA team once a bug fix is deployed to the staging environment.

Send an automated email to the Product Owner when a critical blocker is identified.

Update the Bug entry status to 'Closed' once verification is successful.

Create a comprehensive PDF/Dashboard report summarizing the testing cycle results.

Get entries from the 'Environments' data model to verify if the staging server is active.

Send an SMS notification to the QA Lead if a P0 (Blocker) issue is detected during night builds.

Delete redundant bug entries that were identified as duplicates during the triage process.

Край на работния поток/процеса.