6 articles
Every article tagged Testing, newest first. Search all articles
Monitoring9 min read
WooCommerce checkout monitoring without placing live orders
WooCommerce checkout monitoring should run a scheduled browser journey against a staging or sandbox store, using synthetic products, customer details and a test payment method.
Monitoring7 min read
How to test WordPress plugin updates before they reach production
To test WordPress plugin updates safely, copy production to staging, a private test copy, review what changed, update in controlled batches, and run the site flows that matter before production. Keep a pre-update backup and the previous plugin package or version ready so you can reverse a bad release quickly.
Enterprise7 min read
WordPress CI/CD with GitHub Actions: tests, builds and safe deploys
A WordPress CI/CD pipeline in GitHub Actions should test every pull request, build one repeatable release artifact, and deploy only code after approval. Keep uploads, secrets, and the database outside the repository, then switch releases with a symlink so rollback does not require copying files over the live site.
Development7 min read
End-to-end WordPress Playwright testing for editor, admin and checkout
WordPress Playwright testing lets a browser verify the editor, wp-admin, and checkout paths that a release depends on. Run those flows against wp-env, reuse a saved admin session, keep test data fixed, and save traces and screenshots when CI fails.
Development7 min read
WordPress plugin unit testing with wp-env and PHPUnit
WordPress plugin unit testing stays repeatable when pure PHP tests stay small and WordPress integration tests run in a wp-env environment. Set up wp-env, bootstrap the WordPress PHPUnit files through WP_TESTS_DIR, write tests with WP_UnitTestCase, then run the same command in GitHub Actions.
Monitoring7 min read
WordPress visual regression testing before and after updates
WordPress visual regression testing takes reference screenshots of important pages, repeats them after an update, and flags visual differences for review. It catches broken layouts, missing styles, shifted controls, and other front-end regressions that an uptime check can miss.