Super Speedy Chat testing
Testing › Super Speedy Chat
Last full run: version 1.21.2 · 11 November 2026
Summary
This page lists the test suites we run on Super Speedy Chat, what each one proves, and the result of the last full run. Every suite runs on its own WordPress test site, never on a live shop. The tests open the chat as a real visitor would, send real messages through the plugin’s own routes, reply from wp-admin and the agent console, and then read back what was actually stored and shown.
Super Speedy Chat can answer visitors three ways, chosen by the Ajax Type setting: Normal, where WordPress loads in full; Fast, where WordPress loads in full but with only the plugins the chat needs; and Ultra, where a small must-use plugin answers the chat request itself and WordPress never finishes loading. A conversation must behave the same whichever type is chosen, so the conversation tests run each case on all three.
The latest run found four known faults in the plugin, all reported and all listed below. We show them rather than hide them.
The test suites
| Suite | What it proves | How it runs |
|---|---|---|
| Function and REST suite | 32 test files inside a real WordPress. Visitor and admin chat routes, the Ultra path, who may read or reply to a chat, Require Login, opening hours and away status, Instant Reply, canned and AI replies, Search Assist, the daily caps, WhatsApp and Discord relays, the Discord connection test, MCP abilities, privacy export and erase, and Delete All Data. It also checks that a visitor’s IP address is never stored on a chat or sent to Discord, WhatsApp or anywhere else. Outside services are answered on the test machine itself, so nothing is sent to a real account. | WP-CLI, calling the plugin directly and through its REST routes |
| Browser suite | 47 tests with real clicks in a real browser: guest and logged-in conversations on Normal, Fast and Ultra; admin replies, closing and deleting chats; the agent console and its new-chat alerts and sounds; message times in the viewer’s time zone; a message that fails to send showing as not sent and sending once on Retry; contact details on the email prompt; colours and layout on phone and desktop screens; settings export and import; page caches being cleared when settings change; hosts that refuse DELETE and PUT requests; and the built-in Ajax Type benchmark. | Chromium, against the real chat widget and wp-admin |
| Install and uninstall | Two separate sites are filled with chats, canned responses and channel data through the plugin’s own code, then the plugin is deactivated. With “Delete all chat data when this plugin is deactivated” switched off, every record must survive. With it switched on, every table, option and the must-use plugin file must be gone. | WP-CLI, on two dedicated sites |
| Visitor limits under load | Real parallel requests over the web server, on Ultra, Fast and Normal: 40 chats started at once must admit no more than the 10-a-minute limit; 30 email submissions on one chat must send no more than 3 emails to you; a chat must cost at most one paid AI classification however often it is asked; and a site-wide AI cap of 5 must hold against 30 requests at once. | HTTP, through nginx and PHP-FPM |
| Chat switched off | With the chat bubble switched off, every visitor route must refuse the request on Ultra and on Normal, and no chat, message, email or AI call may result. Switched back on, everything must work as before. | HTTP, through nginx and PHP-FPM |
| Discord bot | The companion Discord bot’s message handler, fed Discord-shaped messages: it answers its own connection test, relays a person’s reply in a chat thread, and ignores other bots, other channels and its own messages, so it cannot loop. | Node.js |
Last full run: version 1.21.2
Run on 11 November 2026 against the current code, on PHP 8.5 and MariaDB.
| Suite | Result |
|---|---|
| Function and REST suite | 529 of 530 checks passed, in 31 of 32 test files. The one failure is a known fault: WhatsApp away pause (below) |
| Browser suite | 40 of 47 passed in the full run. 4 failures are known faults in the plugin (below). 2 were faults in the tests, which were fixed and then passed. 1 is a known test-harness problem; that test passed when run on its own |
| Install and uninstall | Keep data: 16 of 16 passed. Delete all data: 14 of 15 passed. The one failure is a known fault: two options left behind (below) |
| Visitor limits under load | 11 of 11 passed |
| Chat switched off | 13 of 13 passed |
| Discord bot | 8 of 8 passed |
The known faults in the plugin
- WhatsApp away pause. With “Pause WhatsApp forwards while away” switched on and the chat set to away, a visitor’s message sent through the Normal or Fast type is still forwarded to WhatsApp. Discord pauses correctly, the message itself is stored as it should be, and your own replies still go out.
- Send button on a pale colour. If you choose a very pale primary colour, the Send button keeps white text, which is hard to read. 2 browser tests (phone and desktop width) fail on this.
- Close icon on a white header. On a phone, with a white chat header, the close icon is white on white. It still works when tapped, but cannot be seen. 1 browser test fails on this.
- Settings import and page caches. Saving settings clears your page cache, and that test passes. Importing a settings file does not, so visitors can see the old welcome message until the cache expires or you clear it. 1 browser test fails on this.
- Delete all data leaves two options behind. With “Delete all chat data when this plugin is deactivated” switched on, deactivating the plugin removes every chat table and setting except two small options: the daily channel cap notice and the last Discord error. No chat content or visitor details are among them.
The faults in the tests, and their fixes
In version 1.20.7 the Welcome Message and Contact Details to Ask For settings moved to the Automated Responses tab. Two browser tests still looked for them on their old tabs, so they could not find them and failed. They now open the Automated Responses tab and both passed, along with the other 4 tests in their two files. In version 1.21.0 the plugin gained an eighth database table for its visitor limits, and the install and uninstall tests still expected seven. They now expect eight, and the re-run gave the results above. The plugin code was not changed, so the version is still 1.21.2.
The alert-sound test opens its own browser that blocks sound until the page has been clicked, and checks that the agent console warns you about it. In a full run that browser already counts as clicked before the test touches it, so the warning correctly does not show and the test fails. We traced this to the test setup, not the plugin, in October 2026. Run on its own, it passed.
Not part of this run
- Real outside accounts. Sending to a real Discord server, a real WhatsApp number, a real mailbox or a real AI provider. The tests answer those services on the test machine, which checks what the plugin sends and how it handles errors, but not the services themselves.
- The release ZIP. Super Speedy Chat does not yet have a suite that installs the built ZIP on a fresh site. These tests ran against the plugin’s code, not the packaged download.
What the tests do not cover
- 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 browser. The browser suite runs in Chromium. Firefox and Safari are not part of it.
- Every cache. Page cache clearing is tested with WP Super Cache. Other caching plugins and CDNs are not.
- Every other plugin. Other plugins on your site, and how Fast trims them, are not tested beyond the test plugins each suite installs.
