Auto Infinite Scroll testing
Testing › Auto Infinite Scroll
Last full run: version 1.74.9 · 11 November 2026
Summary
Auto Infinite Scroll has one written list of the test suites that make up its release run. This page describes that list: what each suite proves, how it drives the plugin, and the result of the last full run. Every suite runs on its own WordPress test site with WooCommerce, HPOS order storage switched on and the classic Storefront theme. Most of the tests open the shop in a real browser, scroll the way a visitor does, and then count the products actually on the page: which ones loaded, in what order, and whether any were missed or shown twice.
The last run used WordPress 7.1 and WooCommerce 10.5.3.
The release run
| Suite | What it proves | How it runs |
|---|---|---|
| Load More pause | The core promise: when your settings say a Load More button should appear, automatic loading stops there so visitors can reach your footer, and only a click loads the next batch. Exactly one button and one loading spinner appear, even when the plugin is started twice on the same page, as some themes and filter plugins do. | Browser |
| Paging intervals | Seven different combinations of the “show Load More after X pages” settings, including zero, one, repeating and switching to endless scrolling. Each checks the exact page requests made, where the pause appears, and that every product arrives once, in the right order. | Browser |
| Back button | A visitor who scrolls down several pages, opens a product and presses Back returns to the same products, in the same order, at the same scroll position, on desktop and mobile. Reloading starts again from page one. | Browser, desktop and mobile |
| Other archives | Infinite scroll on blog post archives, custom post type archives and search results, both adding to the list and replacing it, checking the post IDs and their position on screen. | Browser |
| Page weight | The plugin’s five script and style files load on product, post, custom and search listings. If you choose to exclude them from ordinary pages, they are left off those pages, URL and wildcard rules match only what they should, and turning the option off brings all five back. The developer filter for forcing them on still works. | Browser, through the settings page |
| Settings page | Saving settings on desktop and mobile: trigger distance, on/off switches, choosing a loading image from the media library, the button label, and where the spinner appears during a slow request. Negative page counts are refused. | Browser and WordPress itself |
| Multisite | On a real WordPress network with two sites, each site keeps its own settings and pages at its own intervals. Saving on one site does not change the other. | Browser and WP-CLI |
| Tall sidebar | A shop whose sidebar is much taller than the product grid. A visitor who presses End jumps to the bottom, where no further scrolling is possible. Pages 2 to 4 must still load, the Load More pause must appear, and a click must load page 5. | Browser, using the real End key |
| With Super Speedy Filters | On a shop using Super Speedy Filters: after loading pages 3 and 4 from page 2, the page number, previous and next links and “Showing 25–32 of 64 results” all update. On a category showing both subcategories and products, the subcategory tiles are not repeated as more products load. | Browser |
| AI agent controls | The plugin’s AI agent abilities: reading and changing settings, refusing unknown settings, wrong value types and sensitive changes without confirmation, refusing logged-out callers, and inspecting only pages on your own site. Over a real MCP connection, a read-only agent cannot install plugins or change settings, an agent you have allowed to configure can, and your licence key is never shown in full. | WordPress itself and MCP over HTTP |
| Security fixes | Each security problem fixed in November 2026 has a test that failed on the version before its fix. A “next page” link pointing at another site, a text file holding HTML, a JSONP response or a redirect off your site must never be loaded or run. A button label holding markup stays plain text. The agent’s page inspection refuses other ports, closed ports and off-site redirects. On a multisite network, a sub-site administrator cannot save markup that would run for the network administrator, and cannot create the agent user. | Browser, REST and MCP |
Last full run: version 1.74.9
Run on 11 November 2026, with WooCommerce and HPOS.
| Suite | Result |
|---|---|
| Load More pause | Passed |
| Paging intervals | 7 of 7 passed |
| Back button | 2 of 2 passed |
| Other archives and page weight | 14 of 14 passed |
| Settings page | Browser: 2 of 2 passed. Value checks: 8 of 8 passed |
| Multisite | 3 of 3 passed |
| Tall sidebar | Passed |
| With Super Speedy Filters | 2 of 2 passed |
| AI agent controls | 27 of 28 passed. The one failure was a test that could not set itself up (below), not a plugin fault |
| Security fixes | Single site: 14 of 14 checks passed. Multisite: 8 of 8 checks passed |
The one failure
Several of our plugins carry the same shared settings and licence code, and when more than one is installed, only one copy may register the licence tools. One test checks this, and it needs at least two different versions of that shared code installed side by side. On 8 November 2026 all our plugins were updated to the same version, so the test site no longer had two different versions to compare and the test stopped before checking anything. The plugin code was not at fault, and the test was not changed. The seven checks that run over a real MCP connection with three of our plugins installed together all passed, including finding the licence tool.
Not part of this run
- Release package check. Before release, the ZIP file you download is checked on its own fresh site: every file is syntax-checked, nothing meant only for development is included, and the plugin is installed the way you would install it and checked on a real shop page and a real ordinary page. That check runs on the release package and was not part of this run.
- Large catalogue. These tests use 30 products. A 1,000-product version of the Load More test exists and was not part of this run.
What the tests do not cover
- Your theme. Tests run on the classic Storefront theme. Auto Infinite Scroll works with classic themes; your theme’s product list may use different markup, which is what the CSS selector settings are for.
- Your server. Tests run on our development machine with one PHP version and one MariaDB version, not every host and database you might use.
- Every other plugin. Plugins we integrate with, such as WooCommerce and Super Speedy Filters, are tested where a suite names them. Other plugins on your site, including other filter and caching plugins, are not.
- Every browser. Browser tests run in Chromium, at one desktop and one mobile screen size. Safari and Firefox are not part of the run.
