Test Catalog

The Test Catalog is the discovery layer of the Test Hub. It automatically scans your project directory and presents every test file in a structured, searchable interface.

Auto-Scanning

When you open a project in xyva, the catalog scanner runs immediately. It walks the project tree looking for Playwright test files:

Patterns matched:
  **/*.spec.ts    **/*.spec.js
  **/*.test.ts    **/*.test.js

Ignored Directories

node_modules, .git, dist, and build are excluded by default. You can configure additional exclusions in Settings > Test Hub > Ignore Patterns.

File Tree

The left panel displays your tests in their original folder structure. Each node shows:

Element	Description
Folder icon	Collapsible directory with aggregate test count
File icon	Individual spec file
Badge	Number of describe blocks and test() calls inside

Clicking a file expands it to show the describe/test hierarchy parsed from the AST.

Search & Filter

The search bar at the top supports multiple filter modes:

• Name search — type any part of a file name or test title
• Tag filter — filter by @smoke, @regression, or custom tags from test.describe
• Status filter — show only Passing, Failing, Flaky, or Never-Run tests

Status Badges

Status is derived from the most recent Runner execution stored in .xyva/run-history/. Tests that have never been executed show a neutral gray badge.

Test Count Summary

The top bar displays real-time counts:

 Spec Files: 47  |  Describe Blocks: 132  |  Test Cases: 891

These numbers update whenever the scanner detects file changes through the file watcher.

Quick Launch

Select tests using checkboxes at any level — folder, file, or individual test. Then:

1. Click Run Selected to open the Runner with that exact scope
2. Or click Run with Data to attach Variables & Datasets before launching

The selected scope is serialized as a Playwright --grep or --project filter, so the Runner executes only what you chose.

Refresh & Re-Scan

Press Ctrl+Shift+R or click the refresh icon to force a full re-scan. This is useful after checking out a new branch or pulling changes that add or remove test files.

Large Projects

Projects with more than 2,000 test files may experience a brief delay during the initial scan. Subsequent updates use the file watcher and are near-instant.