Test Hub
The Test Hub is the central nervous system of your QA workflow. It scans your project directory, indexes every test file, and presents a unified catalog you can search, filter, and launch from — without ever touching the terminal.
What the Test Hub Does
| Capability | Description |
|---|---|
| Auto-Scan | Recursively discovers .spec.ts, .test.ts, and .spec.js files on project load |
| Test Catalog | Presents a searchable, filterable file tree with spec/describe/test counts |
| Data-Driven Testing | Variables and Datasets engine for parameterized execution |
| Quick Launch | Select tests and send them to the Runner with one click |
Catalog at a Glance
The Test Hub parses your project tree and extracts three levels of granularity:
- Spec files — top-level test files discovered by the scanner
- Describe blocks — logical groups inside each spec
- Test cases — individual
test()/it()calls with their titles
Quick Launch
Select one or more tests in the catalog, then press Run Selected. The Runner opens with exactly that scope — no CLI flags required.
Data-Driven Testing
The Test Hub includes a built-in parameterization engine so you can vary test inputs without editing code.
Variables
Key-value pairs injected at runtime — environment URLs, credentials, feature flags. See Variables & Datasets.
Datasets
Tabular data with a spreadsheet-style editor. Import CSV or JSON, then bind datasets to tests to generate a Run Matrix for combinatorial execution.
INFO
Variables and Datasets are stored locally in .xyva/test-data/. They are never committed to version control by default.
Sub-Pages
| Page | Content |
|---|---|
| Test Catalog | File tree, search & filter, test counts, auto-scanning |
| Data-Driven Testing | Variables + Datasets concept, parameterized execution |
| Variables & Datasets | Key-value editor, tabular datasets, CSV/JSON import, run matrix |
Integration with Runner
Tests selected in the Test Hub carry their full context — scope, variables, dataset bindings — directly into the Runner. This eliminates the gap between test planning and test execution.
Test Hub (select + configure) → Runner (execute) → Intelligence (analyze)The feedback loop closes when Intelligence flags flaky or failing tests, which reappear in the Test Hub with updated status badges.