Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save kscc25/8ef5bbd2c4c86167f8cb65ca90e5962c to your computer and use it in GitHub Desktop.
Save kscc25/8ef5bbd2c4c86167f8cb65ca90e5962c to your computer and use it in GitHub Desktop.

Everytime you run grunt docker-test-midway-backend, it will spawn containers, run midway tests then remove containers. It would take time if you run that command multiple times. In fact, you just have to spawn containers once, run the tests multiple times then remove the containers when you finish.

Spawn the containers (AKA prepare the testing environment):

grunt setup-environment setup-mongo-es-docker

Run the midway tests:

grunt run_grunt:midway_backend

Clean the containers:

grunt kill-containers clean-environment

@MichaelBailly
Copy link

You it at your awn risks : we recreate containers every times to be sure we don't have stale data from previous tests.

@kscc25
Copy link
Author

kscc25 commented Apr 3, 2017

In fact, we do not recreate containers after every test case so this way gives no more risks IMO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment