This skill provides step-by-step instructions to manually test the generate workflow of WPT-Gen. This acts as a robust smoke test to catch regressions and verify the system's integrity during development.

Test Case

We will use a small, stable web feature for this test: abortable-fetch.

Execution Steps

Run the Generate Workflow: Execute the following CLI command to trigger the generate workflow for abortable-fetch:
```
wpt-gen generate abortable-fetch
```
Wait for Generation: Allow the workflow to complete. It should read blueprints and generate tests autonomously.

Verification Steps

Locate Generated Output: Check the out/ or generated/ directory for the output tests related to abortable-fetch. You can also check the local WPT directory if it outputs there.
Inspect Generated Files:
- Check that the required boilerplate (like testharness.js and testharnessreport.js inclusions) is present.
- Verify correct syntax and structure for a Web Platform Test.
- Check for expected test assertions (e.g., using AbortController and fetch).
Check for Regressions:
- The test generation must not crash or hang.
- A valid test file must be created.
- If any of these fail, report a regression.

Cleanup Steps

After successfully verifying the generated tests, you must clean up the workspace to ensure no residual files interfere with future tests or get accidentally committed to the WPT repository.

Delete Generated Test Files: Read the ~/.cache/wpt-gen/generated_tests.json file. Parse the path for each generated test and delete those specific files from the file system to safely remove untracked generated files without affecting the user's other work.
Revert Tracked Changes in WPT: Navigate to the configured WPT repository and safely revert only the files that were modified during the generation step (such as WEB_FEATURES.yml) by running:
```
WPT_DIR="${WPT_DIR:-../wpt}"
git -C "$WPT_DIR" restore WEB_FEATURES.yml
```
Clear State Artifacts: Remove the JSON artifact to fully reset the test state:
```
rm -f ~/.cache/wpt-gen/generated_tests.json
```

Más de este repositorio

mismo repositorio

wpt-evaluator-conformance

GoogleChromeLabs/wpt-gen

Evaluate a WPT test file against extracted normative requirements from its governing spec. Use when a spec URL is available and conformance to the spec needs to be judged. Pairs with the wpt-evaluator skill, which checks against WPT documentation guidance rather than spec conformance.

2026-07-0112

wpt-evaluator

GoogleChromeLabs/wpt-gen

Evaluate the quality of a WPT test file against guidance in the upstream WPT documentation. Use when reviewing a generated or submitted test before merge.

2026-07-0112

wpt-generator

GoogleChromeLabs/wpt-gen

Generate Web Platform Tests (WPT) from minimal XML test suggestions. The agent will autonomously determine the test type and implementation details by analyzing existing repository paradigms. Use when the user asks to generate a Web Platform Test based on a test suggestion.

2026-06-0212

wpt-gen-cli

GoogleChromeLabs/wpt-gen

Best practices for CLI infrastructure, outputs, subprocess management, and templating in WPT-Gen.

2026-03-2512

wpt-gen-llm

GoogleChromeLabs/wpt-gen

Best practices for configuring LLM integrations, concurrent networking, context scraping, and managing prompts in WPT-Gen.

2026-03-2512

wpt-gen-maintenance

GoogleChromeLabs/wpt-gen

Instructions on managing dependencies, build tools, project architecture rules, and integrating workflows via the Makefile in WPT-Gen.

2026-03-2512

WPT-Gen Manual Test

Test Case

We will use a small, stable web feature for this test: abortable-fetch.

Execution Steps

Run the Generate Workflow: Execute the following CLI command to trigger the generate workflow for abortable-fetch:

wpt-gen generate abortable-fetch

Wait for Generation: Allow the workflow to complete. It should read blueprints and generate tests autonomously.

Verification Steps

Locate Generated Output: Check the out/ or generated/ directory for the output tests related to abortable-fetch. You can also check the local WPT directory if it outputs there.

Inspect Generated Files:

Check that the required boilerplate (like testharness.js and testharnessreport.js inclusions) is present.
Verify correct syntax and structure for a Web Platform Test.
Check for expected test assertions (e.g., using AbortController and fetch).

Check for Regressions:

The test generation must not crash or hang.
A valid test file must be created.
If any of these fail, report a regression.

Cleanup Steps

After successfully verifying the generated tests, you must clean up the workspace to ensure no residual files interfere with future tests or get accidentally committed to the WPT repository.

Delete Generated Test Files: Read the ~/.cache/wpt-gen/generated_tests.json file. Parse the path for each generated test and delete those specific files from the file system to safely remove untracked generated files without affecting the user's other work.

Revert Tracked Changes in WPT: Navigate to the configured WPT repository and safely revert only the files that were modified during the generation step (such as WEB_FEATURES.yml) by running:

WPT_DIR="${WPT_DIR:-../wpt}"
git -C "$WPT_DIR" restore WEB_FEATURES.yml

Clear State Artifacts: Remove the JSON artifact to fully reset the test state:

rm -f ~/.cache/wpt-gen/generated_tests.json