|Test Platform

How to Use

Quick guide to get started with the QA Test Platform

Quick Start
Get up and running in 4 steps
1

Create a Client

Admin > Clients > Add Client

2

Create a Project

Admin > Projects > Add Project

3

Add Test Cases

Admin > Test Cases > Add Test Case

4

Run Tests

Execute > Choose Plan > Start

Navigation
What each section does

Dashboard

Overview of test statistics, execution plans, and recent test runs. See total tests, pass rate, and quick access to common actions.

Tests

Browse all test cases. Filter by module, priority, type, or search by keyword. Click any test to view full details including steps and expected results.

Execute

Start a new test run. Choose from preset plans (Smoke, Regression, Full) or create a custom selection. Track progress and record results in real-time.

History

View past test runs and their results. See pass/fail breakdown, review notes, and track testing progress over time.

Admin

Manage clients, projects, and test cases. Create new test cases manually or organize existing ones.

Adding Test Cases
How to create and organize tests

Required Fields

  • Project:Which project this test belongs to
  • Module:Feature area (e.g., Auth, API, Checkout)
  • ID Prefix:Auto-generates IDs like AUTH-001, API-002
  • Title:Clear description of what to test

Priority Levels

P0 - Critical
P1 - High
P2 - Medium
P3 - Low

Use P0 for core functionality and blockers. P1 for important features. P2 for nice-to-have. P3 for edge cases and cosmetic issues.

Test Types

  • Manual: Requires human execution
  • Automation: Can be automated
  • Both: Manual now, automate later
Executing Tests
How to run a test session

Execution Plans

Smoke Test - P0 only (~15 min)
Regression - P0+P1 (~2 hrs)
Full Suite - All tests (~4 hrs)
Security - Security tags (~30 min)

Recording Results

Pass - Test succeeded
Fail - Test failed
Skip - Not applicable

Add notes to failed tests to document what went wrong. This helps developers fix issues faster.

Tips
Best practices for effective testing
  • 1.Run Smoke Tests after every deployment to catch critical issues quickly.
  • 2.Run Regression before major releases to ensure nothing is broken.
  • 3.Use tags to organize tests (e.g., "api", "ui", "mobile", "security").
  • 4.Write clear steps so anyone can execute the test without prior knowledge.
  • 5.Always add notes when a test fails - include error messages and screenshots.
  • 6.Click Sync Tests to reload test cases from JSON files after updates.