Introduction to the QIT local test environment. Ephemeral Docker-based WordPress+WooCommerce environments created with qit env:up and removed with qit env:down. Covers prerequisites (Docker required, platform notes for Mac/Linux/Windows WSL), starting your first environment, accessing the site URL, environment management commands (env:list, env:source, env:exec, env:enter, env:reset), and ...
Woo API tests Woo API tests verify that your extension interacts cleanly with the WooCommerce REST API. By creating and manipulating products, orders, and customers through API requests, these tests ensure that your extension doesn’t introduce errors or alter expected responses, helping maintain a stable and reliable store experience. How it works The Woo API tests: Set up a fresh WordPress ...
Woo E2E tests 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 essential store operations. This includes completing the WooCommerce onboarding wizard, creating a product, making a purchase as a customer, verifying order details as an admin, adjusting tax settings, and more ...
Guide to named environments in qit.json, an optional feature for reusing WordPress/WooCommerce/PHP version combinations across multiple profiles. Covers all environment properties (php, wp, woo, plugins, themes, object_cache, php_extensions, volumes, envs, utilities), environment inheritance via extends, volume mappings, utility packages for environment setup, environment variables (all values ...
Overview of managed tests: pre-built quality checks maintained by the QIT team that run remotely with zero setup. Lists all available test types (activation, security, woo-e2e, woo-api, phpstan, phpcompatibility, malware, validation, plugin-check) with brief descriptions. Explains when to use them (before release, in CI/CD), how to interpret results (success, warning, failed), and links to ...