Test Tools Support

VigilQA works with the testing tools you already use — import existing assets, run alongside your own suites, and let the agents drive a growing library of underlying tools.

An open toolchain, not a walled garden

VigilQA generates plain pytest and Playwright code and orchestrates well-known open tools under the hood, rather than a proprietary runner. That means you can adopt it incrementally, keep the assets you have, and take the generated tests anywhere.

Tools the agents drive

Each module is backed by a standard tool that VigilQA's agents configure, run, and interpret for you. You get the analysis layer without wiring the tools together by hand.

Capability	Underlying tool
Web UI & browser automation	Playwright (Chromium, Firefox, WebKit)
API & contract testing	pytest + HTTP client, OpenAPI/Swagger schema validation
Accessibility	axe-core (WCAG 2.1)
Performance & load	Locust
Visual regression	Pixel-diff image comparison
Security / VAPT	OWASP-aligned probe suite
Model & agent evaluation	LLM-as-judge scorer + schema/rule checks

Bring your existing tests

You don't have to regenerate a suite you already have. Point VigilQA at an existing tests/ directory and its post-run agents will analyse those results too — failure classification, flakiness, regressions, and coverage — even for tests VigilQA didn't write.

# Analyse an existing pytest suite
vigilqa analyze --junit results/junit.xml --project myapp

# Or run your suite through VigilQA and collect analysis
vigilqa run --suite ./tests --report junit

Import test assets

Seed a project from artifacts you already maintain:

• OpenAPI / Swagger — generate API and contract tests directly from your spec.
• Postman collections — import requests as API scenarios.
• Requirement documents — Word, PDF, or Markdown via Extract from Document.

Export & interoperate

Everything VigilQA produces is portable. Generated tests are ordinary Python files you own; results export as JUnit XML and JSON for any CI system or reporting tool; and notifications flow out over Slack, webhooks, and email. There is no proprietary format holding your tests hostage.