QIT CLI 1.3.1 Release Notes

New Features

Added authenticated beta API fuzz testing

The new qit run:api-fuzz <extension> command runs schema-driven fuzz testing against plugin-owned WordPress REST API routes. It supports published extensions, uploaded development builds, synchronous and asynchronous execution, and normalized JSON results.

Lifecycle status is shown separately from the fuzz campaign state. The command waits up to 45 minutes by default, treats cancellation as terminal, and preserves the established QIT exit codes for success, warning, and failure.

See API Fuzz Testing for scope, campaign limits, result interpretation, and examples.

Improvements

• Managed-run JSON output decodes structured result fields instead of returning nested JSON strings.
• Asynchronous managed-run output includes the initial lifecycle status.
• All Manager-backed run:* commands now accept a local ZIP, local directory, or remote HTTP(S) ZIP through --zip.
• Managed run:* commands now return failure exit code 1 when the Manager lifecycle status is hanged.
• qit get displays the API-fuzz campaign state and treats a cancelled run as finished.

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

• Update snapshot by @zhongruige in #469
• Revert validation snapshot: "Tested up to" back to "5.8" for themes by @zhongruige in #470
• Require Docker Compose v2 instead of silently falling back to EOL v1 by @zhongruige in #472
• QIT-1006: Clarify repeatable environment reset contract by @zhongruige in #473
• QIT-1013: Reduce API-fuzz reset overhead by @zhongruige in #474
• Expose API fuzz testing through qit run:api-fuzz by @zhongruige in #475

Full Changelog: 1.3.0...1.3.1

QIT CLI 1.3.1 Release Notes

New Features

Added authenticated beta API fuzz testing

The new qit run:api-fuzz <extension> command runs schema-driven fuzz testing against plugin-owned WordPress REST API routes. It supports published extensions, uploaded development builds, synchronous and asynchronous execution, and normalized JSON results.

Lifecycle status is shown separately from the fuzz campaign state. The command waits up to 45 minutes by default, treats cancellation as terminal, and preserves the established QIT exit codes for success, warning, and failure.

See API Fuzz Testing for scope, campaign limits, result interpretation, and examples.

Improvements

• Managed-run JSON output decodes structured result fields instead of returning nested JSON strings.
• Asynchronous managed-run output includes the initial lifecycle status.
• All Manager-backed run:* commands now accept a local ZIP, local directory, or remote HTTP(S) ZIP through --zip.
• Managed run:* commands now return failure exit code 1 when the Manager lifecycle status is hanged.
• qit get displays the API-fuzz campaign state and treats a cancelled run as finished.

Support and Feedback

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

QIT CLI 1.3.0 Release Notes

New Features

Added run:compatibility command for compatibility smoke tests

A new run:compatibility command runs WooCommerce compatibility smoke tests against your extension. When no test package is specified, it defaults to woocommerce/compatibility-smoke-tests:latest.

qit run:compatibility my-plugin
qit run:compatibility my-plugin --zip=my-plugin.zip --wait

Local test runs now also report each extension's requested version (not just the resolved version) to QIT Manager, enabling versioned compatibility reporting.

Bug Fixes

Fixed misleading "invalid zip" error when a download returns an HTTP error

Downloads that returned an HTTP error (404, 403, 5xx) or an empty body were written to disk anyway, so a "Not found" page could masquerade as the downloaded zip and only fail later as a confusing "invalid zip" error. The CLI now validates the HTTP status and file size immediately after download, deletes the bad file, and fails with a message naming the real cause.

Fixed stale cached WooCommerce dev builds

WooCommerce development builds (x.y.z-dev) change frequently but were cached with the long-lived TTL, so in-place rebuilds could be missed. They now use the short cache TTL alongside rc and nightly.

Improved plugin activation failure reporting

Plugin activation failures now surface a clearer, structured report (plugin, debug log, output) and the runner bails correctly on a fatal activation error instead of continuing.

Maintenance

PHP 8.1+ deprecation fixes

Removed a deprecated ReflectionProperty::setAccessible() call (now guarded to PHP < 8.1) and redundant curl_close() calls, silencing deprecation notices on newer PHP versions.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page or run qit feedback "your message".

What's Changed

• Fix snapshots for activation test by @zhongruige in #465
• Add versioned compatibility runner support by @zhongruige in #466
• Fix WooCommerce dev ZIP resolution by @zhongruige in #468

Full Changelog: 1.2.4...1.3.0

QIT CLI 1.3.0 Release Notes

New Features

Added run:compatibility command for compatibility smoke tests

A new run:compatibility command runs WooCommerce compatibility smoke tests against your extension. When no test package is specified, it defaults to woocommerce/compatibility-smoke-tests:latest.

qit run:compatibility my-plugin
qit run:compatibility my-plugin --zip=my-plugin.zip --wait

Local test runs now also report each extension's requested version (not just the resolved version) to QIT Manager, enabling versioned compatibility reporting.

Bug Fixes

Fixed misleading "invalid zip" error when a download returns an HTTP error

Downloads that returned an HTTP error (404, 403, 5xx) or an empty body were written to disk anyway, so a "Not found" page could masquerade as the downloaded zip and only fail later as a confusing "invalid zip" error. The CLI now validates the HTTP status and file size immediately after download, deletes the bad file, and fails with a message naming the real cause.

Fixed stale cached WooCommerce dev builds

WooCommerce development builds (x.y.z-dev) change frequently but were cached with the long-lived TTL, so in-place rebuilds could be missed. They now use the short cache TTL alongside rc and nightly.

Improved plugin activation failure reporting

Plugin activation failures now surface a clearer, structured report (plugin, debug log, output) and the runner bails correctly on a fatal activation error instead of continuing.

Maintenance

PHP 8.1+ deprecation fixes

Removed a deprecated ReflectionProperty::setAccessible() call (now guarded to PHP < 8.1) and redundant curl_close() calls, silencing deprecation notices on newer PHP versions.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page or run qit feedback "your message".

QIT CLI 1.2.4 Release Notes

Bug Fixes

Fixed local --zip runs reusing a stale cached build after rebuilding in place

When running tests against a local zip, the CLI caches the file using a key derived from its path. Overwriting the same zip in place, for example rebuilding a plugin to the same filename, left the previously cached copy in place, so subsequent runs tested the old build. Moving the zip to a new path was the only workaround.

The CLI now re-copies a local zip into the cache when the source file is newer or a different size than the cached copy, so in-place rebuilds are picked up automatically. Unchanged files continue to use the cache with no extra work.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page or run qit feedback "your message".

What's Changed

• Bust local zip cache to prevent stale runs by @zhongruige in #464

Full Changelog: 1.2.3...1.2.4

QIT CLI 1.2.4 Release Notes

Bug Fixes

Fixed local --zip runs reusing a stale cached build after rebuilding in place

When running tests against a local zip, the CLI caches the file using a key derived from its path. Overwriting the same zip in place, for example rebuilding a plugin to the same filename, left the previously cached copy in place, so subsequent runs tested the old build. Moving the zip to a new path was the only workaround.

The CLI now re-copies a local zip into the cache when the source file is newer or a different size than the cached copy, so in-place rebuilds are picked up automatically. Unchanged files continue to use the cache with no extra work.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page or run qit feedback "your message".

QIT CLI 1.2.3 Release Notes

Bug Fixes

Fixed intermittent "manager sync data bucket for 'versions' is not available" error in CI

Resolved a race condition that could cause test runs to fail with
Failed to parse environment JSON and The manager sync data bucket for 'versions' is not available,
most often on cold CI runners using --woocommerce_version=rc or --wordpress_version=rc.

The sync data that resolves these versions is cached with a short TTL and refreshed at
CLI startup. Slow setup steps — package download, npm install, and Playwright browser
installation — could elapse past that TTL before the version was resolved, leaving the
cache pruned. The CLI now re-syncs on demand when the data has expired instead of failing.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page or run qit feedback "your message".

What's Changed

• Re-sync on stale manager sync bucket to fix cold-CI race (qit-984) by @zhongruige in #463

Full Changelog: 1.2.2...1.2.3

QIT CLI 1.2.3 Release Notes

Bug Fixes

Fixed intermittent "manager sync data bucket for 'versions' is not available" error in CI

Resolved a race condition that could cause test runs to fail with Failed to parse environment JSON and The manager sync data bucket for 'versions' is not available, most often on cold CI runners using --woocommerce_version=rc or --wordpress_version=rc.

The sync data that resolves these versions is cached with a short TTL and refreshed at CLI startup. Slow setup steps — package download, npm install, and Playwright browser installation — could elapse past that TTL before the version was resolved, leaving the cache pruned. The CLI now re-syncs on demand when the data has expired instead of failing.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page or run qit feedback "your message".

QIT CLI 1.2.2 Release Notes

Bug Fixes

Restored previous --extension_set behavior for test runs

Restores the previous --extension_set behavior when running tests, which enqueues run:woo-api, run:woo-e2e, and run:activation on QIT servers. This allows compatibility-set extensions to be resolved by QIT Manager, including restricted WooCommerce.com plugins such as woocommerce-gift-cards, while preserving the existing local test-package behavior when --extension_set is not used.

qit run:woo-api my-plugin --extension_set=compatibility
qit run:woo-e2e my-plugin --zip=my-plugin.zip --extension_set=compatibility --wait

CLI options that only apply to local test-package runs now fail clearly when combined with --extension_set, instead of being silently ignored.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page or run qit feedback "your message".

What's Changed

• Address extension set compatibility unable to resolve error by @zhongruige in #462

Full Changelog: 1.2.1...1.2.2

QIT CLI 1.2.2 Release Notes

Bug Fixes

Restored previous --extension_set behavior for test runs

Restores the previous --extension_set behavior when running tests, which enqueues run:woo-api, run:woo-e2e, and run:activation on QIT servers. This allows compatibility-set extensions to be resolved by QIT Manager, including restricted WooCommerce.com plugins such as woocommerce-gift-cards, while preserving the existing local test-package behavior when --extension_set is not used.

qit run:woo-api my-plugin --extension_set=compatibility
qit run:woo-e2e my-plugin --zip=my-plugin.zip --extension_set=compatibility --wait

CLI options that only apply to local test-package runs now fail clearly when combined with --extension_set, instead of being silently ignored.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page or run qit feedback "your message".

QIT CLI 1.2.1 Release Notes

Bug Fixes

Restored --extension_set option for run:woo-api and run:woo-e2e

The --extension_set option was missing from the run:woo-api and run:woo-e2e commands. It is now declared and resolved on each command, expanding the named set into its extensions and merging them into --plugin.

qit run:woo-e2e my-plugin --extension_set=my-set

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page or run qit feedback "your message".

What's Changed

• Add check around API connectivity and skip by @zhongruige in #459
• Fix for missing extension set option on woo API and woo e2e tests by @zhongruige in #461

Full Changelog: 1.2.0...1.2.1

QIT CLI 1.2.1 Release Notes

Bug Fixes

Restored --extension_set option for run:woo-api and run:woo-e2e

The --extension_set option was missing from the run:woo-api and run:woo-e2e commands. It is now declared and resolved on each command, expanding the named set into its extensions and merging them into --plugin.

qit run:woo-e2e my-plugin --extension_set=my-set

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page or run qit feedback "your message".

QIT CLI 1.2.0 Release Notes

New Features

New run:woo-e2e command

Run WooCommerce Core E2E tests locally against your extension using the self-contained woocommerce/core-e2e-tests:latest test package.

qit run:woo-e2e my-plugin

New run:woo-api command

Run WooCommerce Core API tests locally against your extension using the self-contained woocommerce/core-api-tests:latest test package.

qit run:woo-api my-plugin

Bug Fixes

Fixed expired credentials causing CLI to hang

When credentials had expired, the CLI would hang indefinitely on authentication instead of failing gracefully with a clear error message.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page or run qit feedback "your message".

What's Changed

• Update snapshots by @Luc45 in #444
• Better handling around expired credentials by @zhongruige in #445
• Snapshot updates for 10.8.0 dev by @zhongruige in #446
• Snapshot updates for 10.8.0 beta by @zhongruige in #449
• Snapshot updates for 10.8 beta 2 by @zhongruige in #450
• 10.8.0-rc1 e2e snapshots by @zhongruige in #451
• e2e snapshots updates for 10.8.0 by @zhongruige in #452
• Update e2e snapshots for 10.8.1 by @zhongruige in #453
• Migrate Woo API tests to test package by @zhongruige in #447
• 10.9.0 dev e2e snapshots by @zhongruige in #454
• Update snapshots for PHPStan and PHPCompat tests by @zhongruige in #455
• Add run:woo-api command for self-contained API test package by @zhongruige in #456
• Fix run:woo-api --optional_features support (re-land of #456) by @zhongruige in #457
• Migrate Woo e2e tests to test package by @zhongruige in #448

Full Changelog: 1.1.9...1.2.0

QIT CLI 1.2.0 Release Notes

New Features

New run:woo-e2e command

Run WooCommerce Core E2E tests locally against your extension using the self-contained woocommerce/core-e2e-tests:latest test package.

qit run:woo-e2e my-plugin

New run:woo-api command

Run WooCommerce Core API tests locally against your extension using the self-contained woocommerce/core-api-tests:latest test package.

qit run:woo-api my-plugin

Bug Fixes

Fixed expired credentials causing CLI to hang

When credentials had expired, the CLI would hang indefinitely on authentication instead of failing gracefully with a clear error message.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page or run qit feedback "your message".

QIT CLI 1.1.9 Release Notes

Bug Fixes

Fixed --json output for synchronous test runs

When using --json with synchronous run commands (e.g., qit run:security my-plugin --json), the output contained progress messages and table-formatted text wrapped in an error JSON object instead of clean test result JSON. This happened because the --json flag was only handled in CI mode — interactive terminal sessions ignored it entirely, causing the stream filter to emit all human-readable output as {"error":"Command failed with non-JSON output","output":"..."}.

The --json flag now works correctly in all environments and the completed test result is output as clean, pretty-printed JSON.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page or run qit feedback "your message".

What's Changed

• Include requires_php from WPORG API in plugin/theme info by @zhongruige in #440
• Snapshot updates for 10.7 beta 2 by @zhongruige in #441
• Fix for --json output flag by @zhongruige in #442

Full Changelog: 1.1.8...1.1.9

QIT CLI 1.1.9 Release Notes

Bug Fixes

Fixed --json output for synchronous test runs

When using --json with synchronous run commands (e.g., qit run:security my-plugin --json), the output contained progress messages and table-formatted text wrapped in an error JSON object instead of clean test result JSON. This happened because the --json flag was only handled in CI mode — interactive terminal sessions ignored it entirely, causing the stream filter to emit all human-readable output as {"error":"Command failed with non-JSON output","output":"..."}.

The --json flag now works correctly in all environments and the completed test result is output as clean, pretty-printed JSON.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page or run qit feedback "your message".

QIT CLI 1.1.8 Release Notes

New Features

JSON output improvements for AI agents and scripts

The --json output for get, get-multiple, and run:e2e now decodes embedded JSON fields (ctrf_json, test_result_json, debug_log) into proper JSON objects instead of returning them as escaped strings (JSON-in-JSON). This makes the output directly parseable by AI agents and tools like jq.

New --json-results flag

A new --json-results flag on get and get-multiple outputs only the test results as clean JSON — no metadata, no URLs. Returns CTRF results if available, otherwise falls back to test_result_json.

qit get 12345 --json-results | jq '.results.summary'

Feedback command

New qit feedback "message" command to send feedback directly to the QIT team. Automatically includes CLI version, PHP version, and OS info. Messages are limited to 2000 characters; for detailed reports, users are directed to GitHub issues.

qit feedback "The security test gave an unexpected result for my plugin"

Contextual hints now appear after test failures and API errors suggesting qit feedback.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page or run qit feedback "your message".

What's Changed

• Fix --json output to decode embedded JSON fields, add --json-results flag by @Luc45 in #438
• Add qit feedback command by @Luc45 in #439

Full Changelog: 1.1.7...1.1.8

QIT CLI 1.1.8 Release Notes

New Features

JSON output improvements for AI agents and scripts

The --json output for get, get-multiple, and run:e2e now decodes embedded JSON fields (ctrf_json, test_result_json, debug_log) into proper JSON objects instead of returning them as escaped strings (JSON-in-JSON). This makes the output directly parseable by AI agents and tools like jq.

New --json-results flag

A new --json-results flag on get and get-multiple outputs only the test results as clean JSON — no metadata, no URLs. Returns CTRF results if available, otherwise falls back to test_result_json.

qit get 12345 --json-results | jq '.results.summary'

Feedback command

New qit feedback "message" command to send feedback directly to the QIT team. Automatically includes CLI version, PHP version, and OS info. Messages are limited to 2000 characters; for detailed reports, users are directed to GitHub issues.

qit feedback "The security test gave an unexpected result for my plugin"

Contextual hints now appear after test failures and API errors suggesting qit feedback.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page or run qit feedback "your message".

QIT CLI 1.1.7 Release Notes

New Features

Configurable HTTP timeout for environments

Control nginx and PHP-FPM timeouts with a new --timeout flag:

qit env:up --timeout=2 --xdebug    # Fast 504 for xdebug+Playwright debugging
qit env:up --timeout=30             # Custom timeout in seconds

Default remains 600s. Also configurable via qit.json:

{
  "environments": {
    "default": {
      "timeout": 2
    }
  }
}

When using xdebug with Playwright MCP for PHP debugging, setting --timeout=2 causes nginx to return 504 after 2 seconds instead of holding the connection for 60s while PHP-FPM is paused at a breakpoint. The xdebug session on port 9003 stays alive and inspectable.

Developer config commands

New config:set and config:get commands (dev-mode only) for managing QIT configuration values.

Bug Fixes

• Fixed wporg version-specific download URL: when requesting a specific plugin/theme version (e.g., --woo=9.0.0 or --plugin=akismet:5.6), the download URL now correctly points to the requested version instead of always downloading the latest.
• Fixed RemoteTestPrecedenceTest::test_zip_upload_option_for_remote_test path bug.
• Fixed test_additional_plugins_conversion assertion to match actual CLI behavior.
• Fixed undefined array key warning in test_cli_slug_wins_and_emits_warning.

Improvements

Test fixture system

Integration tests no longer download real plugin/theme zips from WordPress.org or make live API calls during left-side tests. A fixture system serves committed local responses:

• Pre-approved plugin/theme zips (real root-level files, ~1KB-500KB each)
• Cached WordPress.org API responses as JSON fixtures
• Request logging (QIT_REQUEST_LOG) for auditing network activity during tests
• Fixture mode persisted via QIT Config — no fragile env var propagation

The fixture guard fails loudly if a test attempts a download or API call without a fixture, preventing silent network regressions.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page.

What's Changed

• Add --timeout option to env:up by @Luc45 in #435
• Update activation snapshots by @Luc45 in #436
• Fix wporg version-specific download URL + test fixtures by @Luc45 in #437

Full Changelog: 1.1.6...1.1.7

QIT CLI 1.1.7 Release Notes

New Features

Configurable HTTP timeout for environments

Control nginx and PHP-FPM timeouts with a new --timeout flag:

qit env:up --timeout=2 --xdebug    # Fast 504 for xdebug+Playwright debugging
qit env:up --timeout=30             # Custom timeout in seconds

Default remains 600s. Also configurable via qit.json:

{
  "environments": {
    "default": {
      "timeout": 2
    }
  }
}

When using xdebug with Playwright MCP for PHP debugging, setting --timeout=2 causes nginx to return 504 after 2 seconds instead of holding the connection for 60s while PHP-FPM is paused at a breakpoint. The xdebug session on port 9003 stays alive and inspectable.

Developer config commands

New config:set and config:get commands (dev-mode only) for managing QIT configuration values.

Bug Fixes

• Fixed wporg version-specific download URL: when requesting a specific plugin/theme version (e.g., --woo=9.0.0 or --plugin=akismet:5.6), the download URL now correctly points to the requested version instead of always downloading the latest.
• Fixed RemoteTestPrecedenceTest::test_zip_upload_option_for_remote_test path bug.
• Fixed test_additional_plugins_conversion assertion to match actual CLI behavior.
• Fixed undefined array key warning in test_cli_slug_wins_and_emits_warning.

Improvements

Test fixture system

Integration tests no longer download real plugin/theme zips from WordPress.org or make live API calls during left-side tests. A fixture system serves committed local responses:

• Pre-approved plugin/theme zips (real root-level files, ~1KB-500KB each)
• Cached WordPress.org API responses as JSON fixtures
• Request logging (QIT_REQUEST_LOG) for auditing network activity during tests
• Fixture mode persisted via QIT Config — no fragile env var propagation

The fixture guard fails loudly if a test attempts a download or API call without a fixture, preventing silent network regressions.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page.

QIT CLI 1.1.6 Release Notes

New Features

Xdebug support in local environments

Enable PHP step debugging, profiling, or tracing with a single flag:

qit env:up --xdebug              # Step debugging (default)
qit env:up --xdebug=profile      # Cachegrind profiling
qit env:up --xdebug=trace        # Function call tracing
qit env:up --xdebug=debug,develop # Combined modes

Xdebug is pre-installed in all runner images with mode=off (zero overhead). The --xdebug flag writes an ini override and restarts PHP-FPM — no compilation or network downloads needed.

Also configurable via qit.json:

{
  "environments": {
    "default": {
      "xdebug": true
    }
  }
}

The environment summary shows IDE path mappings and the output directory for cachegrind/trace files.

Documentation: https://qit.woo.com/docs/environment/xdebug

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page.

QIT CLI 1.1.5 Release Notes

New Features

QIT Runtime (@woocommerce/qit-runtime)

A new npm package that gives test packages a standard way to interact with QIT and each other at runtime. Two access patterns:

• qit.actions('makePurchase') - Anonymous capability discovery. Like WordPress do_action(), multiple packages register implementations for the same action name. Consumers iterate over all of them. Adding a payment gateway = zero code changes in the consumer.
• qit.package('woocommerce/core-utils') - Known dependency access. Import another package's exports directly (page objects, login helpers, etc).

Also provides typed environment access (qit.env.siteUrl), WP-CLI execution (qit.wp()), and async polling (qit.waitFor()).

New packages scaffolded with qit package:scaffold include it automatically.

Documentation: https://qit.woo.com/docs/test-packages/concepts/runtime

Actions manifest field

Test packages can now declare actions in their qit-test.json manifest:

{
  "actions": {
    "makePurchase": "./flows/pay.ts"
  }
}

QIT CLI generates the actions manifest and package map at test execution time, wiring qit.actions() and qit.package() to the loaded test packages.

Bug Fixes

Fix $schema validation blocking existing test packages

The $schema field in qit-test.json is for IDE support. A strict const constraint was rejecting packages that used a different schema URL (e.g., qit.woo.com vs GitHub raw). Removed the constraint and added a filter so $schema mismatches never block execution.

Fix error output rendering for run:e2e failures

Errors like "Missing required secrets" were rendered as a double-wrapped JSON mess. Now they display cleanly:

Missing required secrets:

  * E2E_JP_SITE_ID (required by: woocommerce-payments/woopayments-e2e-tests:1.3.0)

Set these environment variables before running this command.
Example: export E2E_JP_SITE_ID='your-secret-value'

Improvements

Outdated runtime version warning

When a test package has an older version of @woocommerce/qit-runtime installed, QIT CLI now warns with an actionable message instead of silently continuing.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page.

QIT CLI 1.1.4 Release Notes

Bug Fixes

Fix cross-package globalSetup deduplication

Fixed a bug where two different test packages with the same relative script path (e.g. ./bootstrap/global-setup.sh) would collide in the globalSetup dedup logic, silently skipping the second package's setup. The hash now includes the package path, so only subpackages from the same parent (which genuinely share the same script) are deduplicated.

Improvements

Utility package suggestions

When spinning up an environment with env:up or run:e2e, QIT now checks if any plugins in the environment have recommended utility packages available. If so, a tip is shown:

Tip: Utility packages are available for plugins in this environment:
  --test-package=woocommerce/baseline:latest

The tip is suppressed when the utility is already included or in JSON output mode.

New utility package: woocommerce/baseline

A new woocommerce/baseline:latest utility package is available on the registry. It dismisses WooCommerce activation redirects, onboarding wizards, coming-soon mode, and configures a ready-to-test store baseline. Include it in any environment that has WooCommerce to prevent activation interference with tests.

--keep-env flag for post-failure debugging

Added --keep-env flag to run:e2e that keeps the environment running after test failures, making it easier to debug issues interactively.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page.

QIT CLI 1.1.3 Release Notes

Improvements

Filesystem-based environment state management

Environment state is now tracked directly on the filesystem instead of a separate cache. Each environment stores its metadata as env_info.json in its temp directory, eliminating "ghost" environments that appeared in env:list when containers were killed externally.

• EnvironmentDanglingCleanup has been removed — no longer needed since the filesystem is the single source of truth.
• env:source has been simplified to use the same source of truth as all other environment commands.

New CLI options

• env:down --all — Stop all running environments with a flag (previously only available as a positional argument env:down all).
• env:list --json — Machine-readable JSON output for scripting and AI agent consumption.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page.

QIT CLI 0.8.8 Release Notes

Bug Fixes and Improvements

Corrected the link to the how to update QIT CLI documentation.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page. Your feedback helps us continually improve QIT.

QIT CLI 1.1.1 Release Notes

This release introduces AI-assisted development as a first-class QIT workflow via the Claude Code plugin system.

What's New

Claude Code Plugin

• QIT CLI is now a Claude Code plugin marketplace. Install with two commands in Claude Code:

  /plugin marketplace add woocommerce/qit-cli
  /plugin install qit@woocommerce-qit
  

  Claude can then handle any QIT task autonomously — running tests, creating test packages, debugging failures, configuring projects — by fetching live documentation on demand.

• Daily plugin recommendation — First CLI invocation of the day shows a brief tip about the Claude Code plugin. Dismiss permanently with qit claude-tip:dismiss.

• Post-connect tip — After successful qit connect, users see the plugin install instructions.

Schema URLs

• $schema URLs now resolve. The --with-schema flag on qit package:scaffold and $schema fields in qit.json/qit-test.json now point to GitHub raw URLs that actually serve valid JSON Schema, enabling IDE autocompletion and validation.

Removed

• ai:context, ai:claude-setup, ai:install-agents commands and all supporting infrastructure (AgentVersionChecker, agent templates, CLAUDE.qit.md template). Replaced by the Claude Code plugin.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page.

QIT CLI 1.1.0 Release Notes

This release focuses on consistency, stability, and developer experience improvements across configuration, environments, and performance.

What's New

Configuration Consistency

• Aliases work everywhere — --wp, --woo, --php short aliases now work in qit.json profiles, not just CLI flags. Previously they were silently ignored in config files.
• Predictable config merging — Fixed config resolution so the precedence chain (CLI flags > profile inline values > referenced environment > defaults) is consistent across all test types.
• Fixed plugins lost in run:e2e delegation — Plugins defined in qit.json profiles were dropped when run:e2e dispatched to env:up.

Environment Stability

• Fixed dangling cleanup race condition — Parallel CLI invocations (e.g. env:list polling) no longer destroy containers mid-creation.
• Volumes tied to environment lifecycle — Docker volumes are now managed by compose, eliminating orphaned volumes that outlived their environments.
• Docker subnet exhaustion — Clear error message with actionable fix when Docker runs out of network subnets, instead of a cryptic failure.

Performance & Reliability

• Reduced redundant sync calls — Subprocesses reuse cached sync data (60s TTL) instead of hitting the Manager on every invocation.
• Faster initialization — Shared cache via symlinks instead of per-worker copies; 30-second timeout on initialization lock prevents indefinite hangs.

Bug Fixes

• Fixed extensions not populated after partner:add.
• Fixed run:e2e succeeding silently without a SUT — now fails fast with a clear error.
• Fixed config pipeline dropping profile-defined environment parameters.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page.

QIT CLI 1.0.0 Release Notes

This is a minor release that restores the missing extension_set option from the activation tests.

QIT CLI 1.0.0 Release Notes

We are excited to announce QIT CLI 1.0.0! This major release introduces a new test package system, project-level configuration via qit.json, and much more.

What's New

Test Packages

• New Test Package System A complete overhaul of the custom test system. Test packages use a qit-test.json manifest format with support for lifecycle phases (global_setup, run, global_teardown), subpackages, CTRF report validation, and Allure reporting.

• Scaffold Command Quickly create new test packages with qit package:scaffold, which generates the manifest and directory structure for you.

• Utility Package Type Test packages can now declare a utility type for shared helpers and setup logic, supported across env:up, run:e2e, package:show, and the scaffold command.

• Auto-Install Required Extensions Extensions declared in test package manifests are automatically resolved and installed during environment setup.

• Network Requirements Test packages can declare requires.network to automatically configure tunnels for tests needing external network access.

Run Groups

• run:group Command Run grouped test suites in a single command, making it easy to execute a coordinated set of tests together.

Project-Level Configuration

• qit.json Configuration File Define test configuration — SUT, plugins, themes, PHP/WP/Woo versions, and profiles — in a project-level JSON config file with schema validation. This makes it easy to check your test setup into source control.

• Version Option Aliases --php, --wp, and --woo are now short aliases for --php_version, --wordpress_version, and --woocommerce_version across all run commands.

Environment Improvements

• env:reset Command Reset a running environment back to its initial state, useful for manual testing workflows.

• Infrastructure Provider Abstraction A new --provider flag on env:up introduces provider abstraction, paving the way for future cloud-based environments.

AI-Assisted Test Investigation

• ai:context and ai:setup Commands Get structured context for AI agents to investigate test failures, with Claude Code integration via the ai:setup command.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page. Your feedback is invaluable and helps us continuously enhance the QIT CLI tool.

QIT CLI 0.10.0 Release Notes

What's New

Improved Plugin Activation Testing

• Enhanced Pre-Activation Step Handling
  The activation testing process now explicitly runs the pre-activation step for all plugins in the activation stack. This ensures that the default bootstrap behavior occurs at the appropriate time during the setup phase.

• Better Multi-Plugin Testing Support
  This update improves compatibility testing scenarios involving multiple plugins, particularly when running activation tests with additional plugins that have custom tests configured.

Enhanced Group Management Features

• JSON Output Support for Group Fetch
  Added a new --json flag to the group:fetch command that allows retrieving test group information in raw JSON format.

• Improved Group Management UX

  • Test group information is now displayed when clearing a group
  • When attempting to enqueue a new test while a completed test group exists, the system will:
    1. Display the existing completed group
    2. Clear it automatically
    3. Proceed with the new test enqueuing

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page. Your feedback is invaluable and helps us continuously enhance the QIT CLI tool.

QIT CLI 0.9.1 Release Notes

Minor release to ignore some PHP debug log entries in the Activation Test that are not coming from the SUT, and might cause the test to become a Warning instead of a Success.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page. Your feedback helps us continually improve QIT.

QIT CLI 0.9.0 Release Notes

We are excited to announce the release of QIT CLI version 0.9.0! This update introduces powerful new features for managing grouped and batched tests, making it easier to organize and execute multiple tests in a coordinated manner.

What's New

Test Grouping and Batching

• Group Management: Organize related tests into logical groups for coordinated execution
• Batch Processing: Execute multiple tests without grouping for parallel processing
• New Commands:
  • group:register - Register test groups with custom identifiers
  • group:run - Execute registered test groups
  • group:fetch - Retrieve group information from remote
  • group:show - Display current group status and details

Enhanced Test Execution

• Local and Remote Coordination: Seamlessly run both local and remote tests in a single group
• Automatic Test Management: Local tests run sequentially without additional user input
• Group Status Tracking: Monitor the progress and completion status of all tests in a group
• Flexible Grouping Options: Use --skip-grouping for batch processing without logical grouping

Add a test to a group

qit run:activation your-extension --group --extension_set compatibility

Register a test group

qit group:register --group-identifier commit-1234567890

Execute a group of tests

qit group:run

Documentation

For detailed information about the new grouping and batching features, please visit our group tests documentation.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page. Your feedback helps us continually improve QIT.

QIT CLI 0.8.8 Release Notes

Bug Fixes and Improvements

Another batch of bug fixes mainly around Custom Tests architecture.

Please keep in mind that the support policy of QIT CLI is to only support the latest version. Make sure to always be on the latest version, especially on CI workflows. Some updates are required and the tool might exit early with an update prompt if you are not on the latest version.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page. Your feedback helps us continually improve QIT.

QIT CLI 0.8.7 Release Notes

<img src="./img/bug-squash.png" alt="Bug Squashing" style="max-width:600px; height:auto;" />

This release is all about squashing bugs!

Bug Fixes and Improvements

This PR includes several bug fixes for the QIT CLI, especially around test types that uses the Custom Tests platform, such as run:e2e, run:activation, and env:up.

• Fix WP.org Download Slug Ambiguity: Resolves issues when the same slug exists as both a plugin and a theme.
• Automatically Activate Theme: When spinning up a test environment with a single --theme argument, that theme (and its parent, if it’s a child theme) is now automatically activated.
• Fix Plugin’s Custom PHPStan Neon File: Ensures PHPStan uses the correct custom neon configuration.
• Improve qit get Command: Removes unnecessarily long columns for cleaner output.
• Display Errors with --json: Ensures errors are properly displayed in JSON output.
• Skip Fetching Custom Tests for Non-WCCOM: Custom tests are fetched only for extensions hosted on WooCommerce.com.
• Correct SUT Path for Zip Files: Sets the proper path for SUT when a zip file is used.
• Fix String Plugin in Config File: Addresses incorrect handling of string-based plugin definitions.
• Tolerate Missing Docker: QIT will now gracefully handle environments without Docker installed.
• Allow Unknown Slugs: Permits extension slug lookups even if the slug is not recognized initially.
• Log Slow Requests: Adds visibility into requests that take longer than expected.
• Self-Tests Around PHPStan Neon Files: Adds internal tests to validate and maintain these configuration files.
• Stop Printing Console Errors to Stdout: Reduce verbosity on console log when running tests that emits a lot of console warnings/errors.
• Increase Notification Timeout: Raises notify timeout for better reliability.
• Change Working Directory Before Scripts: Switches the working directory as needed when running scripts.
• Remove ConfigurationProcessor: Simplifies early setup by removing extra configuration processing.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page. Your feedback helps us continually improve QIT.

QIT CLI 0.8.6 Release Notes

What’s New

Improve qit get command by removing some verbose output and making sure the display is rendered correctly without breaking links.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page. Your feedback helps us continually improve QIT.

QIT CLI 0.8.5 Release Notes

What’s New

Ignoring more deprecation warnings when using extension sets, and better control over Playwright tests via tag filtering.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page. Your feedback helps us continually improve QIT.

QIT CLI 0.8.4 Release Notes

What’s New

Ignoring some common deprecation warnings when using extension sets.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page. Your feedback helps us continually improve QIT.

QIT CLI 0.8.3 Release Notes

What’s New

Extension set support in local activation tests.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page. Your feedback helps us continually improve QIT.

QIT CLI 0.8.2 Release Notes

What’s New

Fixes and improvements to error handling

Several bug fixes and error handling improvements.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page. Your feedback helps us continually improve QIT.

QIT CLI 0.8.1 Release Notes

What’s New

Improved Orchestration in Custom Tests

• Shared Setup/Teardown in Bootstrap Mode
  Additional plugins designated as bootstrap now properly execute their shared setup and teardown steps even if their test suites are skipped. This ensures the bootstrap phase correctly prepares the testing environment for all involved plugins.

• Automatic WooCommerce Dependency Handling
  QIT now ensures that if WooCommerce is a required dependency for your plugin (as determined by WooCommerce.com product metadata - soon to be updated to use your plugin’s "Requires Plugins" header), it is automatically included.

• Enhanced Parameter Handling (--tunnel, --dependencies)
  QIT now lists all possible values for these parameters, making it easier to discover valid options.

• Action Overrides for Additional Plugins
  CLI overrides specified at runtime (e.g., -p plugin:action or --plugin plugin:action) now reliably take precedence over qit.yml settings.

• Corrected Path in dependencies.json
  Fixed a typo referencing qit/dependencies.json. The correct file path is now bootstrap/dependencies.json, ensuring dependencies load as intended.

Documentation Overhaul

Complete Documentation Rewrite

The QIT documentation at qit.woo.com has been entirely rewritten from scratch. The new documentation provides clearer explanations, step-by-step guides, and updated references to reflect recent orchestration improvements and configuration refinements.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page. Your feedback helps us continually improve QIT.

QIT CLI 0.8.0 Release Notes

What’s New

Enhanced Orchestration in Custom End-to-End (E2E) Tests

• Optimized Database Lifecycle Management
  Improved the database (DB) lifecycle handling during Custom E2E tests, particularly for compatibility testing involving multiple plugins.

• Streamlined Lifecycle Steps
  The updated lifecycle now follows these steps:

  1. Shared Setup Execution
     Execute setups that are common to all plugins.
  2. Database Export
     Export the current state of the DB.
  3. Per-Plugin Operations
     For each plugin, perform the following:
     • DB Import
       Import the exported DB state.
     • Plugin-Specific Setup
       Execute setups unique to the plugin.
     • Run Tests
       Conduct the plugin-specific tests.
     • Plugin-Specific Teardown
       Execute teardowns unique to the plugin.
  4. Shared Teardown Execution
     Execute teardowns that are common to all plugins.

• Flexible State Management
  This update allows you to:

  • Share State Across Plugins: Define shared states, such as establishing connections to external services or removing onboarding wizards during the shared setup phase.
  • Isolate Plugin-Specific Configurations: Customize setups unique to each plugin, like installing and activating a custom theme required by a specific plugin.

Documentation

For a detailed understanding of the new lifecycle management, please refer to our Understanding the Lifecycle documentation.

Support and Feedback

If you have any questions, encounter issues, or have suggestions, please visit our GitHub Issues Page. Your feedback is invaluable and helps us continuously enhance the QIT CLI tool.

QIT CLI 0.7.1 Release Notes

What's New

Environment variables in Custom Tests

• Adds --env and --env_file to run:e2e, run:activation and env:up commands.
• This can be used to pass secrets or configuration that you don't want to hardcode in your tests.

Documentation

Check the documentation for Environment Variables.

For any queries, issues, or suggestions, feel free to visit our Github page at https://github.com/woocommerce/qit-cli/issues. We appreciate your feedback as it helps us to continuously improve our tool.

QIT CLI 0.7.0 Release Notes

We are excited to announce the release of QIT CLI version 0.7.0! This update introduces tunneling support, along with UX/developer experience improvements.

What's New

Tunneling Support

• Easy Configuration: Use our built-in tunneling methods for easy tunneling.
• Improved Testing: Tunneling support enables you to test your extensions with a live URL.
• Multiple Tunneling Methods: Choose the tunneling method that works best for you.

Documentation

You can find the documentation for Tunneling here.

For any queries, issues, or suggestions, feel free to visit our Github page at https://github.com/woocommerce/qit-cli/issues. We appreciate your feedback as it helps us to continuously improve our tool.

QIT CLI 0.6.0 Release Notes

We are excited to announce the release of QIT CLI version 0.6.0! This update introduces the Activation Test 2.0, our first smart generic test, along with several enhancements designed to improve your testing workflow.

This is the first test type built on top of our Custom Tests platform!

What's New

Activation Test 2.0

• Improved Coverage: Now visits pages added by your extensions, catching errors that previous tests might have missed.
• Smart Generic Tests: Automatically detects and tests essential functionalities without custom scripts.
• Fast Execution: Completes tests in 50 seconds to 3 minutes, depending on your setup.
• Local Testing: Run tests directly on your machine or CI environment for immediate feedback.
• Error Detection: Captures PHP and JavaScript notices, warnings, and errors, including those on custom plugin pages, as well as Database errors.
• Configurable Environment:

• PHP Versions: Test with PHP 7.2 up to 8.4 RC 3.
  

• WooCommerce & WordPress Versions: Choose any version, including development builds.
  

• Plugin Dependencies: Activate additional plugins by their slugs to simulate real-world scenarios.
• Notifications: Use --notify to receive immediate alerts when issues are detected.
• Centralized Results: All test results are collected in QIT for easy access and analysis.
• Built on Custom Tests: Leverages existing frameworks for efficiency and easier maintenance.

Backwards Compatibility

• Seamless Integration: Designed to work with existing CI workflows without disruptions.
• Minimal Adjustments: No significant changes required for extensions currently using QIT.

Documentation

You can find the documentation for the Activation Test type here.

For any queries, issues, or suggestions, feel free to visit our Github page at https://github.com/woocommerce/qit-cli/issues. We appreciate your feedback as it helps us to continuously improve our tool.

QIT CLI 0.5.4 Release Notes

• Adds support for a QIT_RESULTS_DIR env var which specifies where to store the e2e results when running run:e2e command.

For any queries, issues, or suggestions, feel free to visit our Github page at https://github.com/woocommerce/qit-cli/issues. We appreciate your feedback as it helps us to continuously improve our tool.

QIT CLI 0.5.3 Release Notes

• This is a follow-up to the 0.5.2 release. Fixes an issue with using "--woo" parameter that would cause a Custom E2E test files to not be found.

For any queries, issues, or suggestions, feel free to visit our Github page at https://github.com/woocommerce/qit-cli/issues. We appreciate your feedback as it helps us to continuously improve our tool.

QIT CLI 0.5.2 Release Notes

• Fix an error that can happen when using both "--woo" and "--plugin=woocommerce" at the same time when running a Custom E2E Test.
• Many fixes and improvements

For any queries, issues, or suggestions, feel free to visit our Github page at https://github.com/woocommerce/qit-cli/issues. We appreciate your feedback as it helps us to continuously improve our tool.

QIT CLI 0.5.1 Release Notes

• Register a shareable test run in QIT for local custom test runs, with an embedded Allure Report with support for screenshots and videos of failures in E2E
• Many fixes and improvements

For any queries, issues, or suggestions, feel free to visit our Github page at https://github.com/woocommerce/qit-cli/issues. We appreciate your feedback as it helps us to continuously improve our tool.

QIT CLI 0.5.0 Release Notes

• New Feature: Local Test Environments: Added the ability to create Local Test Environments with a single command. These environments are disposable and fully customizable, making automated testing much simpler. (Read More: Test Environment Documentation)
• New Feature: Custom Tests: Added support for Custom E2E tests, allowing developers to write, share, and run personalized automated tests easily. (Read more: Custom Tests Documentation)
• Many fixes and improvements

For any queries, issues, or suggestions, feel free to visit our Github page at https://github.com/woocommerce/qit-cli/issues. We appreciate your feedback as it helps us to continuously improve our tool.

QIT CLI 0.4.2 Release Notes

• When encountering "429 - Too Many Requests" when starting tests, respect the "Retry-After" header if it's present, otherwise do an exponential backoff.
• When running on Windows without a Certificate Authority file, ask the user if they want to download a CA file to be used in QIT, related to https://github.com/php/php-src/issues/13601.

For any queries, issues, or suggestions, feel free to visit our Github page at https://github.com/woocommerce/qit-cli/issues. We appreciate your feedback as it helps us to continuously improve our tool.

QIT CLI 0.4.1 Release Notes

• Fix the config path on native Windows.
• Groundwork for upcoming local test environments and integrated custom E2E tests for wide-scale compatibility testing.

For any queries, issues, or suggestions, feel free to visit our Github page at https://github.com/woocommerce/qit-cli/issues. We appreciate your feedback as it helps us to continuously improve our tool.

QIT CLI 0.4.0 Release Notes

This is a strongly recommended update.

• Updates QIT URL to https://qit.woo.com.
• Renames "authentication_password" to "qit_token" for clarity.
• Bug fixes and improvements.

For any queries, issues, or suggestions, feel free to visit our Github page at https://github.com/woocommerce/qit-cli/issues. We appreciate your feedback as it helps us to continuously improve our tool.

QIT CLI 0.3.5 Release Notes

This is an optional update.

• Return async response when using --json flag without waiting for the test completion (with --wait flag).
• Minor styling and consistency improvements.
• Bug fixes and improvements.

For any queries, issues, or suggestions, feel free to visit our Github page at https://github.com/woocommerce/qit-cli/issues. We appreciate your feedback as it helps us to continuously improve our tool.

QIT CLI 0.3.4 Release Notes

This is an optional update.

• Resolved an issue that caused QIT to incorrectly identify certain valid zip files as invalid.
• Fixed occasional flakiness when syncing with QIT servers.

For any queries, issues, or suggestions, feel free to visit our Github page at https://github.com/woocommerce/qit-cli/issues. We appreciate your feedback as it helps us to continuously improve our tool.

QIT CLI 0.3.3 Release

This is an optional update.

• Improved onboarding experience for Automatticians.
• Protect user from accidentally leaking credentials if running "very verbose mode" in CI (With -vvv parameter). GitHub already obfuscates any secret in output, but this is an additional measure.

Please ask any questions/report any issues at https://github.com/woocommerce/qit-cli/issues

QIT CLI 0.3.2 Release

• Improve QIT update logic, informing when there's an optional update available, or enforcing when there's a required update to be done.
• Shows possible values of test arguments that are comma-separated values.

Please ask any questions/report any issues at https://github.com/woocommerce/qit-cli/issues

QIT CLI 0.3.1 Release

Suggest an unique app name to be able to run partner:add multiple times without having to delete previous application passwords.

Please ask any questions/report any issues at https://github.com/woocommerce/qit-cli/issues

QIT CLI 0.2.1 Release

Improvements to the partner authentication flow.

Please ask any questions/report any issues at https://github.com/woocommerce/qit-cli/issues

QIT CLI 0.3 Release

In this release we prepare the CLI to be usable by all Partner developers of the Woo Marketplace.

We have reworked the onboarding flow to be more user-friendly both to Automattic and external developers, along with dozens of other improvements.

Please ask any questions/report any issues at https://github.com/woocommerce/qit-cli/issues

QIT CLI 0.1 Release

This is the first release of the QIT CLI. Please ask any questions/report any issues at https://github.com/woocommerce/qit-cli/issues