Skip to content
This repository has been archived by the owner on Jul 28, 2024. It is now read-only.

Stop containers after tests #1399

Merged
merged 4 commits into from
Mar 10, 2019
Merged

Stop containers after tests #1399

merged 4 commits into from
Mar 10, 2019

Conversation

borekb
Copy link
Member

@borekb borekb commented Mar 10, 2019

Issue: #1389

npm run tests:full now automatically stop the containers after the tests finish running (both successfully and with failures).

The tests:stop-and-cleanup script has been renamed to a simpler tests:cleanup and docs updated.

borekb added 2 commits March 11, 2019 00:03
The `tests:stop-and-cleanup` script has been renamed to `tests:cleanup`.
@borekb borekb added scope: dev-infrastructure Build scripts, IDE settings, CI, Docker dev stack, testing, tooling, etc. scope: tests Testing code. For infrastructure (CI, etc.), use "dev-infrastructure". labels Mar 10, 2019
@borekb borekb added this to the 4.0 milestone Mar 10, 2019
@borekb borekb self-assigned this Mar 10, 2019
borekb added 2 commits March 11, 2019 00:26
This script is meant to be used with additional arguments, e.g.:

```
npm run tests:custom-with-wordpress -- -c phpunit.xml --filter RevertTest
```

So it cannot contain "; npm run tests:stop".
Docker stack now needs to be started manually as it's auto-shutdown when tests finish running.
@borekb borekb changed the title Stop containers after tests finish running Stop containers after tests Mar 10, 2019
@borekb borekb merged commit b9e6cc3 into master Mar 10, 2019
@borekb borekb deleted the 1389-stop-containers-after-tests branch March 10, 2019 23:48
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
scope: dev-infrastructure Build scripts, IDE settings, CI, Docker dev stack, testing, tooling, etc. scope: tests Testing code. For infrastructure (CI, etc.), use "dev-infrastructure".
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant