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 …

Overview of test packages: custom Playwright E2E tests in a standardized format that can be shared and combined for cross-plugin compatibility testing. Explains the problem (plugins test in isolation, …

Command reference for test package and environment operations. Auto-generated CLI usage for run:e2e, env:up, env:down, package:scaffold, package:publish, package:list, package:show, …

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, …

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 …

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 …

Guide to named environments in qit.json, an optional feature for reusing WordPress/WooCommerce/PHP version combinations across multiple profiles. Covers all …

Get started with QIT — let your AI coding agent handle installation, authentication, and testing, or run the CLI commands yourself. Same tool, you choose who drives.

The recommended MCP servers and tools for using QIT with AI coding agents. Covers Playwright MCP for browser observation, Xdebug MCP for PHP debugging, and how they work together in a typical …

PHPCompatibility tests PHPCompatibility tests analyze your extension’s codebase against a range of PHP versions to ensure broad compatibility. By identifying deprecated features, incompatible …