PHPackages                             solutiondrive/sd-test-environment-shopware - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Testing &amp; Quality](/categories/testing)
4. /
5. solutiondrive/sd-test-environment-shopware

ActiveLibrary[Testing &amp; Quality](/categories/testing)

solutiondrive/sd-test-environment-shopware
==========================================

Docker based testing environment for shopware projects.

v0.4.0(4y ago)115.0k[1 issues](https://github.com/solutionDrive/sdTestEnvironmentShopware/issues)11proprietaryShell

Since Aug 15Pushed 4y ago6 watchersCompare

[ Source](https://github.com/solutionDrive/sdTestEnvironmentShopware)[ Packagist](https://packagist.org/packages/solutiondrive/sd-test-environment-shopware)[ Docs](https://solutiondrive.de)[ RSS](/packages/solutiondrive-sd-test-environment-shopware/feed)WikiDiscussions master Synced today

READMEChangelog (2)DependenciesVersions (15)Used By (11)

Docker based Shopware Testing Environment
=========================================

[](#docker-based-shopware-testing-environment)

For easier testing with different shopware- and/or php-versions we use a docker based environment. There are some docker containers providing MySQL, PHP and so on. The local filesystem is mapped into the containers that need them.

**NOTE on this README**This file assumes that bin-scripts are installed to `vendor/bin` (as composer does by default). If your changed this behaviour in your `composer.json`you have to adjust the commands written in this file accordingly.

Installation
------------

[](#installation)

To use the testing environment in a project, add the following dependency to your project's composer.json's require-dev section:

```
"require-dev": {
    "solutiondrive/sd-test-environment-shopware": "*"
}

```

Then do a `composer update` or use `composer require --dev` instead.

To initialize the testing environment, e.g. for Shopware 5.7.x simply run the following:

```
vendor/bin/sdTest.sh init 57

```

This will create some files:

```
/README.TESTING.md              # This README.md in your project for other developers
/etc/test/docker-compose.yml    # A docker-compose file which can be modified for special needs

```

Usage / First steps
-------------------

[](#usage--first-steps)

First you should start the testing docker containers (see also next section of this README):

```
vendor/bin/sdTest.sh start SHOPWARE_VERSION

```

Handle plugin
-------------

[](#handle-plugin)

For all following commands you must pass a php and shopware version, e.g. 74 for PHP 7.4 container and 57 for Shopware 5.7 :

For adding the plugin run:

```
vendor/bin/sdPlugin.sh 74 57 add

```

For removing the plugin run:

```
vendor/bin/sdPlugin.sh 74 57 remove

```

For activating the plugin run:

```
vendor/bin/sdPlugin.sh 74 57 activate

```

For deactivating the plugin run:

```
vendor/bin/sdPlugin.sh 74 57 deactivate

```

Controlling the testing environment
-----------------------------------

[](#controlling-the-testing-environment)

List of SHOPWARE\_VERSION:

- 52 -&gt; v5.2.x
- 53 -&gt; v5.3.x
- 54 -&gt; v5.4.x
- 55 -&gt; v5.5.x
- 56 -&gt; v5.6.x
- 57 -&gt; v5.7.x

To start the containers e.g. with shopware 5.7 and get back your local shell just run:

```
vendor/bin/sdTest.sh start 57

```

To stop the containers run:

```
vendor/bin/sdTest.sh stop SHOPWARE_VERSION

```

In stopped state the containers data is saved.

To destroy your containers you can run:

```
vendor/bin/sdTest.sh remove SHOPWARE_VERSION

```

To restart your containers without loosing data you can run:

```
vendor/bin/sdTest.sh restart SHOPWARE_VERSION

```

Can can also run the containers in foreground to monitor the log output of the containers:

```
vendor/bin/sdTest.sh run SHOPWARE_VERSION

```

Then you can stop the execution by pressing CTRL+C. The containers will exit cleanly.

If you started the container in background using `start`, you can view the logs by running:

```
vendor/bin/sdTest.sh logs SHOPWARE_VERSION

```

You can follow the logs (as known from `tail -f` or `tailf`):

```
vendor/bin/sdTest.sh logs SHOPWARE_VERSION -f

```

To connect to the mysql server use `127.0.0.1` as host with port (default: 10331) configured in `etc/test/docker-compose.yml`.

Less frequently needed
----------------------

[](#less-frequently-needed)

To force a rebuild of the containers you can run:

```
vendor/bin/sdTest.sh build --no-cache

```

To be sure that you have the latest version of the (base) containers you can force pulling newer images:

```
vendor/bin/sdTest.sh build --no-cache --pull

```

To be sure to use the newest containers (not only build based containers):

```
vendor/bin/sdTest.sh pull SHOPWARE_VERSION

```

To destroy and restart your containers in one step without rebuilding images run:

```
vendor/bin/sdTest.sh reset SHOPWARE_VERSION

```

Executing a command in the testing environment
----------------------------------------------

[](#executing-a-command-in-the-testing-environment)

Commands (for example to clear the cache or to run the setup) can be executed inside the container. You must give a version of php and shopware to execute command on, e.g. 74 for PHP 7.4 container and 57 for Shopware 5.7.x:

```
vendor/bin/sdRunInTest.sh 74 57 ./app/install.sh

```

If you want to you can even get a shell inside the PHP container:

```
vendor/bin/sdRunInTest.sh 74 57 /bin/bash

```

###  Health Score

28

—

LowBetter than 54% of packages

Maintenance0

Infrequent updates — may be unmaintained

Popularity22

Limited adoption so far

Community24

Small or concentrated contributor base

Maturity60

Established project with proven stability

 Bus Factor1

Top contributor holds 53.3% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~149 days

Recently: every ~274 days

Total

9

Last Release

1630d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/9c04fbc5922166132f9ded7b5d8efdfcc57f20deb1837bf38ed081327343993a?d=identicon)[sd\_alt](/maintainers/sd_alt)

![](https://www.gravatar.com/avatar/8cd3b593f392b760082ae52b4bd42e1d089d4be641b8b95c0d756713ee1a878c?d=identicon)[sd-lueckel](/maintainers/sd-lueckel)

---

Top Contributors

[![michz](https://avatars.githubusercontent.com/u/7523691?v=4)](https://github.com/michz "michz (8 commits)")[![Jnoack331](https://avatars.githubusercontent.com/u/17640771?v=4)](https://github.com/Jnoack331 "Jnoack331 (4 commits)")[![TheBreaken](https://avatars.githubusercontent.com/u/22234380?v=4)](https://github.com/TheBreaken "TheBreaken (2 commits)")[![sd-lueckel](https://avatars.githubusercontent.com/u/16880583?v=4)](https://github.com/sd-lueckel "sd-lueckel (1 commits)")

---

Tags

testingdocker

### Embed Badge

![Health badge](/badges/solutiondrive-sd-test-environment-shopware/health.svg)

```
[![Health](https://phpackages.com/badges/solutiondrive-sd-test-environment-shopware/health.svg)](https://phpackages.com/packages/solutiondrive-sd-test-environment-shopware)
```

###  Alternatives

[phpunit/phpunit

The PHP Unit Testing framework.

20.0k910.7M134.3k](/packages/phpunit-phpunit)[phpunit/php-code-coverage

Library that provides collection, processing, and rendering functionality for PHP code coverage information.

8.9k892.4M1.5k](/packages/phpunit-php-code-coverage)[mockery/mockery

Mockery is a simple yet flexible PHP mock object framework

10.7k497.0M23.5k](/packages/mockery-mockery)[behat/behat

Scenario-oriented BDD framework for PHP

4.0k96.8M1.9k](/packages/behat-behat)[symfony/phpunit-bridge

Provides utilities for PHPUnit, especially user deprecation notices management

2.5k201.2M4.2k](/packages/symfony-phpunit-bridge)[brianium/paratest

Parallel testing for PHP

2.5k118.8M753](/packages/brianium-paratest)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
