Development and testing policy
Development and testing
We confirm it works before we ship it
Every HUBLO WordPress plugin goes through planning, implementation, verification and documentation before release. This page explains what we check, and what we don't.
- AI (such as Claude Code) helps with design and implementation; nothing is sold without verification
- Released only after hands-on testing, automated tests, log review and a reinstall from the distribution ZIP
- We can't guarantee it works in every environment. Please back up before installing
How we use AI
AI writes a first draft. It doesn't replace verification
HUBLO products are built with AI tools (such as Claude Code) assisting with design, implementation and documentation. We say so openly.
However, we never sell AI-generated code without verifying it. Every product goes through the hands-on checks, automated tests and log review below before we decide whether to release it.
Our process
The steps before release
- Planning and specification: we define the problem, the scope, and what the product deliberately won't do
- Implementation: written to the WordPress coding standards
- Static checks: PHP syntax checks to make sure there are no errors
- Hands-on testing: installed and activated on a real WordPress site, and checked in both the admin and the public pages
- Automated tests: functional tests with WP-CLI and browser automation tests with Playwright
- Log review: we check debug.log for any new errors caused by the plugin
- Reinstall check: a fresh install and activation from the distribution ZIP, to catch problems that only exist in the development environment
- Documentation: README, known limitations and usage instructions
- Product page: a product page and FAQ that state both what it does and what it doesn't
Limits of our testing
Automated tests use synthetic data
Our automated tests (WP-CLI functional tests, Playwright end-to-end tests, syntax checks and debug.log review) run on synthetic data we prepare ourselves (test fixtures). They are not run on the real data of your site.
So we don't use phrases like "verified with real data" until we have actually checked with real data.
Safety by design
Principles shared by our products
This is a summary of the principles our products share. For how a specific product behaves, its product page and bundled documentation are authoritative.
- Some products only detect and suggest; they never rewrite your post content or titles automatically
- Products that do change posts or taxonomies only do so after a preview and other safeguards against mistakes
- No product automatically creates or publishes posts or pages
- No product scrapes other websites
- No product logs in to anyone else's admin automatically
- No product contacts external services that aren't stated on its product page or in its README
We document what it can't do, too
Every product page lists what the product can't do, not just what it can. Each product also ships with a document of known limitations (KNOWN_LIMITATIONS). Please read it before you buy.
No product is flawless
Even after these checks, we can't guarantee that no problem will ever occur with every WordPress setup, server, PHP configuration or combination of plugins. We don't make promises like "always safe" or "completely prevents".
Please back up before you install
HUBLO products have no automatic backup or automatic rollback. Always back up your whole site (database and files) before installing a plugin. If you can, try it on a test site before your live site.
Bug reports and updates
When you report a bug we can reproduce, we confirm it, investigate the cause and ship a fix where needed. For what support covers and response times, see Support.
Updates go through the same verification (hands-on testing, automated tests, log review and a reinstall check), and every change is recorded in the Changelog.