What we can show you

We do not publish reviews we cannot verify, and we have no customer outcomes to show you yet. Rather than fill that space with something invented, here is the other thing we can offer: the testing this software goes through before it ships, published as the raw output, so you can read it instead of taking our word for it.

This is us testing our own software. None of it is a customer outcome, and none of it makes any claim about results on your site.

The runs, 2026-08-28

• Google Drive backup, 147 checks, plugin 6.50.13
• OneDrive backup, 127 regression groups, plugin 5.47.4
• Licensing guard suites, rerun 2026-08-31, plugin 10.49.0
• Every first-party PHP file parses, 471 files

Why the names matter more than the numbers

A pass count tells you almost nothing. What a check is actually named tells you whether anyone thought hard about the failure. A few real lines from the files above:

• same-size SQL swap after lazy addFile cannot enter the signed member set
• unchanged incremental source reproof catches same-size mtime-restored byte drift
• source authority reproof catches same-byte inode-number-reuse replacement
• failed database export removes its partial SQL image
• an archive collision refusal names both colliding members

Those are all about a backup that looks fine and is not. That is the failure that matters, because you find it on the day you need the backup.

What runs, and how often

Every push runs the full suites for both backup plugins on PHP 7.4 and 8.3, and the Licensing suites on PHP 8.0 and 8.3, because those are the oldest versions each plugin says it supports. Testing only on the newest PHP would tell us nothing about the sites most likely to break.

Alongside them, restore drills stand up a real database and a real WordPress in containers and restore into them, rather than pretending with mocks: 62 checks per plugin for restore and rollback, three separate states for the international-character warning, and nine file-relocation families checked for release-gate violations.

What this is not

It is not proof the software is free of defects, and we would not claim that. It is a record of what we check and what those checks are called, dated, in our own words, published whether the numbers flatter us or not. When we do have a customer willing to say something about their own experience, it will appear with their name and their permission, and never otherwise.