Skip to content

Create Test Execution Strategy document #318

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
iNileshW wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Create Test Execution Strategy document #318

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
812f73c
Create Test Execution Strategy document
iNileshW Jan 14, 2026
6bd7c06
Added formatting
iNileshW Jan 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
68 changes: 68 additions & 0 deletions quality-assurance/test-execution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,68 @@
# Test Execution

A Test Execution Strategy defines how testing will be carried out—covering environments, prioritization, entry/exit criteria, responsibilities, tooling, reporting, and risk handling. It ensures consistency, predictability, and quality across all test cycles.
Below is a comprehensive strategy for web, legacy, cloud‑migrated, or API-based systems.

## 1. Objectives of Test Execution

- Validate functional and non-functional requirements.
- Ensure system stability across environments.
- Detect defects early through automation and continuous integration.
- Verify readiness for release.


## 2. Test Execution Phases
### 🔹 2.1 Preparation Phase

- Review requirements, user stories, acceptance criteria.
- Finalize test scenarios, test cases, automation scripts.
- Document all the test cases in Azure DevOps Test Plans section with proper tagging (e.g. Smoke Tests, Regression Tests, etc.)
- Prepare test data (static, dynamic, synthetic, masked).
- Configure environments (Dev, QA, Staging, Pre-Prod).
- Validate CI/CD pipelines for automated tests (e.g., GitHub Actions, Azure DevOps).


### 🔹 2.2 Execution Phase
This involves execution of manual, automated, API, and performance tests.
### Automation First Approach
- Run automation smoke suite on each deployment.
- Run regression suite nightly / on pull requests.
- Use API + UI hybrid strategy (fast feedback + UI validation).

### Manual Testing
- Run Manual Tests using Azure DevOps Test Execution Tool
- Add results for each test case
- Add & Attach Test result screenshot for test steps that prove the testcase has passed to each testcase for clear traceability


### 🔹 2.3 Defect Management
- Log defects in Azure DevOps / Jira.
- Prioritize based on severity + business impact.
- Conduct daily triage with developers.
- Track defect aging, reopen rate, resolution time.

### 🔹 2.4 Exit Phase
Release decisions based on:
- Completion of high/medium priority test cases.
- Acceptance criteria met.
- No critical/blocker defects.
- Performance thresholds met.
- Sign-off from QA + stakeholders.

## 3. Test Prioritization Strategy
### 🟢 High Priority
- Core business flows (e.g., login, payment, workflows).
- API endpoints used by multiple services.
- Newly developed or changed features.
- High-risk modules (legacy or customer complaints).

### 🟡 Medium Priority
- Secondary workflows.
- Negative test scenarios.
- Permissions, roles, access control.

### 🔵 Low Priority
- Edge-case validations.
- Optional UI behaviours (alignment, colors, minor visuals).