Test Plans

Define which tests to run, when to run them, and against which environment. Test plans are the starting point for every test execution.

What is a test plan?

A test plan is a named, reusable configuration that specifies a subset of tests and an execution environment. Plans allow you to run different sets of tests in different contexts — for example, a fast smoke plan on every PR, and a comprehensive regression plan on every merge to main.

Creating a test plan

Navigate to Test Plans → New Plan. Configure:

• Plan name — a descriptive identifier (e.g. smoke, regression, nightly-full)
• Environment — which environment configuration to use (see Environments)
• Scope — which tests to include (all, by domain, by tag, or by scenario ID list)
• Modules — override which modules run in this plan (or inherit project defaults)
• Timeout — maximum allowed run duration (default: 30 minutes)
• Parallel execution — number of concurrent test workers (default: 4)

Scope options

Scope type	Description	Example use case
All tests	Every approved test in the project	Nightly full regression
By domain	All tests in selected domains	Regression for a specific feature area after a targeted change
By tag	Tests with specific KB tags (e.g. smoke, regression)	Fast smoke check on every PR
By scenario IDs	Explicit list of scenario IDs to run	Re-run a specific set of failing tests

Running a plan

Plans can be triggered three ways:

1. Manually — click Run Now on the plan card in the dashboard
2. Via CI/CD — POST to the VigilQA API with the plan name (see CI/CD Integration)
3. Scheduled — configure a cron-style schedule in the plan settings (e.g. 0 2 * * * for nightly at 2am UTC)

Common plan patterns

Smoke plan (per PR)

A fast plan scoped to smoke-tagged tests across all domains. Typically 10–20% of the full test suite. Runs in 2–5 minutes. Used to gate PR merges.

Regression plan (per merge to main)

Full test suite across all domains and modules except Security (which runs separately). Catches regressions introduced by the merged change. Typically 15–25 minutes.

Security scan (nightly)

Scoped to the Security & VAPT module only, running against the staging environment. Scheduled nightly to detect new security vulnerabilities introduced by recent changes.