Pick the versions of wordpress and woocommerce you'd like to test against Click confirm and run test to queue the test run The dashboard will display a status such as pending, running, or complete Once finished, you can view detailed results Simulates key woocommerce customer journeys, verifying that your extension does not break core store flows Validates api endpoints and their responses under various conditions.
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. Qit infers which extension is the primary one to test. 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
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 most convenient approach If you don't have composer installed, refer to the official composer documentation before proceeding. This step ensures that only authorized developers can run tests against their listed extensions. Validates woocommerce rest api endpoints under your plugin’s influence Identifies potential security issues using scanning tools and coding standards.
OPEN
