Enterprise Plugin

Findologic Shopware plugin: rebuilt for enterprise reliability

Rebuilt the Findologic Search & Navigation plugin for Shopware 6 with high test coverage, GitHub Actions CI/CD, and multi-version support. Zero regressions shipped.

Industry:: E-commerce / Search
Project Type:: Enterprise Plugin
Duration:: 18 months
Location:: Germany
Published:: February 8, 2024

Outcome

95%+

Test coverage

Full

CI/CD pipeline

Release blockers

SW versions

The Challenge

I took over the Findologic Search and Navigation plugin while Shopware 6 was still in Release Candidate. The plugin was promising but unstable: no tests, no CI, and a release process that depended on manual smoke checks. Enterprise customers wouldn't commit until that changed.

Critical Pain Points

Plugin had to track Shopware 6 RCs as the platform itself was still moving
No automated test infrastructure or release pipeline existed
Enterprise accounts needed proof of stability before adoption
Multi-version support across active Shopware releases was a hard requirement
Search and faceted navigation logic was complex enough to need real coverage

Without test coverage and a real release pipeline, the plugin was always one regression away from a customer escalation. Trust gets built once and lost in an afternoon.

The Solution

I rebuilt the plugin around testing first, then automation, then features. Stability had to come before everything else.

95%+ code coverage

A PHPUnit suite that covers core flows, edge cases, and integration points. Coverage runs on every commit.

GitHub Actions CI/CD

Tests run on every push. Releases tag, build, and publish themselves. The release process became a checkbox.

Multi-version test matrix

Pipeline runs against five Shopware versions on every change. Compatibility regressions surface before merge, not after release.

Documentation worth reading

Code and public APIs documented to a level where new developers can ramp without asking the original author.

Results & Business Impact

Zero production bugs across the rewrite

Customer reports of plugin-caused regressions stayed at zero through the rebuild period.

Survived Shopware 6 RC through 6.4

The plugin tracked Shopware's evolution without breaking releases. CI caught every breaking change before customers did.

Lower maintenance load

Automated tests caught regressions early. Time spent firefighting dropped; time spent on features went up.

Enterprise adoption

Major Shopware operations adopted the plugin once the testing and release story was credible.

Technologies Used

Shopware 5
Shopware 6
PHP 8
Symfony
PHPUnit
GitHub Actions
CI/CD
REST APIs

Plugin in production with no tests?

If a Shopware plugin is your product or your dependency, untested code is a slow-motion incident. Let's talk through what test-first plugin development could look like for you.