qit. woo. com This file contains links to documentation sections following the llmstxt org standard ## Table of Contents
Woo API tests - WooCommerce 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
Environment Configuration | Easy automated tests for WooCommerce . . . 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
Development Workflow | Easy automated tests for WooCommerce plugins and . . . Guide to developing and debugging test packages locally Covers the manual testing workflow: start an environment with `qit env:up`, source environment variables with `qit env:source`, run Playwright tests directly with `npx playwright test` or `--ui` mode, iterate on tests without restarting Docker Includes debugging tips (WordPress debug log, Playwright traces, browser inspector
QIT Runtime | Easy automated tests for WooCommerce plugins and themes - QIT Two Access Patterns The runtime provides two ways for test packages to use code from other packages: qit actions(name): Anonymous Capability Discovery Like WordPress do_action() Multiple packages register implementations for the same action name Consumers iterate over all of them without knowing who provided them
The qit. json Configuration File - qit. woo. com Complete reference for the qit json configuration file Covers all top-level sections: SUT (local, URL, wccom, wporg sources with optional build commands), environments (version pins, plugins, themes, volumes, php_extensions, envs, utilities), test_types with profiles (inline values or environment references, profile inheritance via extends), and groups (batch execution) Includes a real-world
Utility Packages | Easy automated tests for WooCommerce plugins and . . . Complete guide to utility packages: test packages without a run phase, used for environment setup and configuration Covers how to attach them to environments via the `utilities` array in qit json, create them with `qit package:scaffold --package-type=utility`, publish to the registry, and discover available utilities with `qit package:list --type=utility` Documents common patterns (disable
Test Profiles | Easy automated tests for WooCommerce plugins and themes . . . Covers inline version values (php, wp, woo, short or long form), environment references, profile inheritance via extends, the precedence chain (CLI > profile > environment > defaults), common patterns (smoke, compatibility, remote test profiles), tweaks skip for skipping tests by name or regex, and when to use inline values vs named environments
Activation tests | Easy automated tests for WooCommerce plugins and . . . Activation tests 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 correctly throughout the entire process, from activation to order placement and deactivation Operations performed Log in as admin Activate any dependencies that your plugin has (e g
Global Setup | Easy automated tests for WooCommerce plugins and themes . . . Explains the globalSetup lifecycle phase: how each test package encapsulates its own environment setup (dismissing onboarding wizards, configuring API keys, setting defaults) so packages can be combined without coupling Covers the execution model: globalSetup runs once for ALL packages before any tests, its changes persist to the database snapshot, and every subsequent package's tests see the