The Woo E2E (end-to-end) test suite creates a temporary WordPress installation with WooCommerce and your extension installed, then uses a scripted browser to simulate …

The QIT Command Line Interface (CLI) is your primary tool for running tests locally and integrating QIT into your development workflow. Installing it globally via Composer is often the …

Not for managed tests: Managed tests, such as activation, Woo E2E, or security tests, always run in QIT’s cloud environment. The local environment will not affect these tests.

Woo — As noted in the WooCommerce plugin creation documentation, this will be automatically added during deployment. Including it manually may cause issues and will be warned against.

SUT: Usually defined by specifying a woo_extension argument, using a local qit.yml, or providing a --source parameter. QIT infers which extension is the primary one to test.

Choose the test type you wish to run, such as Activation, Woo E2E, or Security. Pick the versions of WordPress and WooCommerce you'd like to test against. Click Confirm and run test to …

Quality Insights Toolkit, or just QIT. A testing platform for WooCommerce plugins and themes.

Woo E2E test: Simulates key WooCommerce customer journeys, verifying that your extension does not break core store flows. Woo API test: Validates API endpoints and their responses …

By integrating QIT into your GitHub Actions workflows, you can automatically test your extension whenever changes are pushed, pull requests are opened, or releases are created. This tight …

The Activation test type performs basic operations on a test site with your plugin activated. It simulates essential workflows that a merchant might perform, ensuring your plugin behaves …