Doc version: v2.0.0

A test strategy is an outline that describes the testing approach of the software development cycle.

The basis of the Test Strategy comes from the Test Huddle discussion involving all the software developers and the quality engineers.

Table of contents

❗ Priorities in Testing

🏃🏻‍♀️ Speed

🎖️ Quality

🔁 Feedback

🔎 Testing Types

Functional testing

✅ 🤖 Component/Unit Testing

✅ 🤖 Integration Testing

✅ 🤖 Component-Integration Testing

✅ 🤖 System-Integration Testing

✅ 🤖 System Testing

Non-functional testing

✅ Accessibility Testing

❌ Security Testing

❌ Vulnerability Assessment

❌ Penetration Testing

✅ Performance Testing

✅ 🤖 Load Testing

✅ 🤖 Stress Testing

Infra Testing

❓ Infra Testing (DevOps)

**Legend:** 
✅ indicates that activity is confirmed in project sprints 
❓ indicates that activity is still under consideration for future sprints
🤖 indicates good feasibility for test automation

📆 Test Schedule

• 1 Sprint = 2 or 3 Weeks. Each sprint, the team would pick a number of user story, task and bug tickets to work on.
• Each sprint would commence with a Sprint Planning session by the entire product team, followed by the Test Planning session among the QEs.
• A sprint typically consists of 10 working days, with the following breakdown:
  • During the first 5 days, QEs will typically be involved in static testing activities like ticket review & clarifications, code review, kickoff & desk-checks, design review & clarifications, test case design and test execution preparation.
  • During the last 5 days, QEs will typically be involved in dynamic testing activities like test case execution, test reporting, test automation design & execution and exploratory testing.