VigilQA Docs

Modules

VigilQA's eight test modules cover the full testing surface of modern web and API applications. Enable any combination per project.

Module reference

ModuleApp typeWhat it tests
REST / GraphQL APIAPIFunctional API requests, response validation, status codes, payloads
Web UI TestingWebEnd-to-end browser automation, user flows, form interactions
API ContractAPIConsumer-driven contract tests, schema stability, breaking change detection
Visual RegressionWebPixel-level screenshot comparisons between builds
AccessibilityWebWCAG 2.1 AA/AAA automated audit per page and component
Security & VAPTAPI / WebOWASP Top 10, SQL injection, XSS, authentication vulnerabilities
PerformanceAPI / WebResponse times, throughput, Lighthouse metrics, load thresholds
Bug TrackerAllAutomatic bug entry creation from test failures with full context

Enabling modules

Modules are configured per project. Navigate to Project Settings → Modules to enable or disable modules. You can change module settings at any time; the change takes effect on the next test run.

When you enable a new module after the initial generation run, you'll need to re-run the generation pipeline for domains where you want the new module to produce tests. Existing scripts for other modules are not affected.

Module-specific KB fields

Most KB scenarios work across all enabled modules. Some modules support additional scenario fields to improve generation quality:

  • REST / GraphQL APIendpoint, method, request_body, expected_status
  • Performancemax_response_ms, min_throughput_rps
  • Securityauth_required, sensitive_data_fields
  • Visual Regressionviewport, screenshot_regions

These fields are optional. The generation agents use them as hints when present.

Running a subset of modules

Test plans can be scoped to specific modules. For example, you can define a plan that runs only Web UI and Accessibility tests on every PR, while the full suite (including Security and Performance) runs nightly. See Test Plans.