Quality code, thoroughly tested

Every release is tested by someone who didn't build it

Most WordPress plugin companies rely on their developers to test their work. Barn2 employs a full-time QA engineer: Aleem Asghar. He tests every plugin and app release before it reaches customers, and nothing goes out until it has passed his manual and automated tests.

QA in numbers

Fixed before it reached your site

90+

Releases tested

170+

Issues found before release

30+

Plugins and apps covered

100%

Approved before shipping

The process

Before a release ships

Features first

Developers submit each new feature for testing on its own, before the release is built. This helps us to identify any issues early instead of discovering them at the last minute.

Changelog testing

We test every line in the release changelog individually. Our developers provide detailed testing guidance to ensure that every feature is thoroughly checked.

Package checks

We check the download for stray development files, and verify the version numbers and WordPress, PHP and WooCommerce requirements in every file that states them.

Full smoke test

We test the settings, the admin screens, the setup wizard and the front end, not only the parts that changed. The browser console and the PHP error log stay open throughout.

Sign-off

A release can only go out once QA has approved it, however small the change. When Aleem finds a problem, the developer fixes it and resubmits. A major release usually takes four or five rounds.

How we test

Two kinds of testing

Manual testing

A real person uses the plugin the way your customers will, on a site set up like a working store with other plugins installed. The awkward problems only show up that way. For example, two plugins can each work perfectly alone and then conflict as soon as you activate both.

Automated testing

Playwright drives real browsers through end-to-end tests, and Pest covers unit and integration tests in the code itself. Every new plugin is built with tests. Every run starts from a clean WordPress install, so a test never passes because of something the previous run left behind.

Real examples

What QA caught before release

  • A discount that applied to products the store owner had explicitly excluded, so shoppers would have paid less than intended.
  • Product options silently dropped from an order when the shopper changed the quantity in their cart.
  • Discounts that stopped applying once a product had more than 100 variations.