Test Explorer — Suites and tests appear in VS Code's built-in Test Explorer panel with run buttons, pass/fail icons, and inline failure messages.
CodeLens — Run Suite ▶ and Run Test ▶ buttons appear inline in .tat.json editor files.
JSON validation — Schema-based IntelliSense and error highlighting in .tat.json files (powered by the published JSON Schema, no configuration needed).
Validate command — tat: Validate File from the Command Palette checks a file without running any HTTP requests.
Output channel — Full tat output appears in the Tiny API Test output channel.
Requirements
tat must be installed in the workspace or globally:
npm install --save-dev @nanotiny/tiny-api-test
If the binary is not found automatically, set tat.cliPath in VS Code Settings to the full path.
Test file naming
The extension discovers files matching **/*.tat.json. Name your test files with the .tat.json extension (e.g. auth.tat.json, users.tat.json).
Settings
Setting
Default
Description
tat.testFilePattern
**/*.tat.json
Glob pattern for discovering test files
tat.cliPath
(auto)
Path to the tat binary. Leave empty to auto-detect from node_modules/.bin/tat or npx tat
tat.timeout
30000
Timeout in ms for tat CLI invocations from the extension
Notes
Running a single test from Test Explorer triggers its whole parent suite (the tat CLI filters by suite name, not individual test). All tests in the suite are updated.
The output channel shows the raw --output json payload from tat, useful for debugging.
Development
cd vscode-extension
npm install
npm run build:watch # rebuild on save
# Press F5 in VS Code to open an Extension Development Host
