Testing

The tests we run every release

Every plugin update can break a live shop, so we publish what we test before a release: the list of suites for each plugin, what each one proves, and the result of the last full run.

A written list for each plugin
Each plugin has one written list of the test suites that make up its release run. The page for that plugin describes exactly that list, nothing more.
Real WordPress, real WooCommerce
Tests run on real WordPress sites with WooCommerce and HPOS order storage switched on. Nothing the plugin depends on is faked.
Failures shown, not hidden
Each page shows the version and date of the last full run with its counts. A test that failed is listed as failed, with what it covers, and once it is fixed we say exactly what was re-run.

How we test

The same approach for every plugin, so one page can be compared with the next.

A fresh test site for each suite
Each suite gets its own WordPress site on our development machine, built from scratch with WooCommerce and HPOS switched on. The site is reset at the start of a run, never at the end, so the results stay there to be inspected afterwards.
Drive the plugin the way you would
Tests use the same ways in that customers use: real clicks in a real browser, WP-CLI commands, and scheduled runs started in fresh requests, the way WordPress runs them on a live site.
Check what actually happened
A test passes only when the products, posts, images, orders and screens end up as they should, read back from the database and the page, not when the plugin merely reports success.
Test the exact download
Where a plugin has a release gate, it installs the exact ZIP file built for release on a fresh site and tests that copy, so a file lost during packaging is caught before you install it.

What the suites cover

  • Every way in: the browser, WP-CLI with one or several workers, REST and scheduled runs.
  • Your data afterwards: the stored products, prices, stock, categories, attributes and images, compared with the expected result.
  • Running it twice: repeating the same job should change nothing the second time.
  • Deletes: what is removed, what must be kept, and that the counts reported match the database.
  • Interruptions: stopped runs, killed processes and slow requests, where the plugin claims to recover from them.
  • Bugs fixed before: a test for a fixed bug must first fail on the broken version, so it proves the fix and stops the bug quietly coming back.
What testing does not cover
  • It runs on our machine, not your server. Each run uses one PHP version and one MariaDB version, not every host.
  • It cannot cover every combination of themes and plugins on your site. Plugins we integrate with are tested where a suite names them.
  • Passing tests are not a guarantee. They show what was checked, on the version named.
  • A version is only covered by the run listed for it. A later version is covered once its own run is listed.

Plugins

Each card shows the version and date of the last full release run, and links to the suites behind it.

3.74.4
Super Speedy Imports
Last full run 10 November 2026
1 test fixed and re-run
See the tests and results
6.41.1
Scalability Pro
Last full run 11 November 2026
1 test fixed and re-run, 1 failure under investigation
See the tests and results
5.100.1
Super Speedy Search
Last full run 11 November 2026
282 of 283 passed, 1 test fixed and re-run
See the tests and results
6.75.0
Super Speedy Filters
Last full run 11 November 2026
4 tests fixed and re-run, 17 failures shown with their causes
See the tests and results
1.16.1
Super Speedy AJAX Prices
Last full run 11 November 2026
6 known failures, 1 test fixed and re-run
See the tests and results
3.47.1
External Images
Last full run 11 November 2026
3 known bugs, 6 checks failing
See the tests and results
2.35.3
Delayed Image Import
Last full run 11 November 2026
1 test fixed and re-run
See the tests and results
1.74.9
Auto Infinite Scroll
Last full run 11 November 2026
1 test could not set itself up
See the tests and results
1.21.2
Super Speedy Chat
Last full run 11 November 2026
5 known faults shown, 3 tests fixed and re-run
See the tests and results

Found a bug?

If something breaks on your site, tell us. A confirmed bug becomes a test.

Bugs and feature requests
Report bugs and ask for features on the public issue tracker. Security problems go through the contact form instead.
How we review security
Testing checks that the plugins work. Our security reviews check how safe they are, with a score for each plugin.
▲
▼
1/1