1.3.2

QIT CLI 1.3.2 Release Notes

New Features

Define local environments from WordPress Playground Blueprints

Local QIT environments can be defined with a WordPress Playground Blueprint:

qit env:up --blueprint=./blueprint.json
qit run:e2e my-plugin --blueprint=./blueprint.json --test-package=./my-tests

No Playground is involved — the Blueprint is translated into a normal QIT Docker environment. blueprint:import and blueprint:export expose the conversion in both directions without booting anything, so a QIT environment can also be shared back as a Playground link.

Supported on env:up, run:e2e, run:woo-e2e and run:woo-api, for e2e environments only.

Added qit compare for diffing two finished test runs

qit compare <run-a> <run-b> diffs two finished test runs without re-running anything:

qit compare 12345 12346
qit compare 12345 12346 --format=json --exit-code

It reports introduced, resolved and still-failing tests; tests added or removed; summary counts side by side; and a per-test diff of extra.annotations. The diff works on CTRF test names and statuses, so it serves every CTRF-reporting test type.

Ecosystem canary runs get two extra rules. A finding whose signature moved to a different probe is reported as moved rather than as a regression and a fix at once. A baseline finding missing from a probe that stopped early is reported as unverified rather than resolved.

Improvements

• run:woo-e2e and run:activation pick their test package from the WooCommerce version under test instead of always using latest, so a run on 11.0.1 no longer executes specs written for 11.1.
• A WooCommerce version ahead of every published line, such as a nightly or a prerelease, takes the nightly activation package instead of falling back to latest.
• qit list-tests runs again. It sends a test_types filter only when one is given, and rejects unknown types locally, naming the allowed values.

Support and Feedback

If you have questions, encounter issues, or have suggestions, open a GitHub issue or run qit feedback "your message".

What's Changed

• Ignore WC-core activation-table DB errors in PrepareDebugLog by @zhongruige in #477
• Test flat managed directory uploads by @zhongruige in #478
• Define local environments from WordPress Playground Blueprints by @alopezari in #479
• Update QIT binary by @alopezari in #480
• Remove undesired files that were part of PR #479 testing and made it to trunk by mistake by @alopezari in #481
• Fix list-tests by dropping the default test_types filter by @alopezari in #484
• Update QIT-CLI binary. by @alopezari in #485
• Pin GitHub Actions to full commit SHAs by @nerrad in #486
• ci: add job-level timeout-minutes to workflow jobs by @adimoldovan in #487
• Add a qit compare command for two finished test runs by @alopezari in #488
• Pick the Woo Core E2E package by the WooCommerce version under test by @alopezari in #489
• Pick the activation package by the WooCommerce version under test by @alopezari in #490
• Tell a moved canary finding from one the candidate introduced by @alopezari in #491
• Pick the nightly package for WooCommerce ahead of every published line by @alopezari in #492
• Keep woo-api self-tests working now results arrive in ctrf_json by @alopezari in #493
• Update binary. by @alopezari in #494

New Contributors

• @nerrad made their first contribution in #486

Full Changelog: 1.3.1...1.3.2