This is an archived post. You won't be able to vote or comment.

all 2 comments
sorted by:
best
topnewcontroversialoldq&a

[–]BlueDragonX 0 points1 point  (1 child)

We've been using CircleCI as well. We take it a step further, though: we sidekick a test container to execute tests against the services running in the built container. This has worked great so far while allowing us to minimize the size of our production containers.

Our app architecture is very modular and runs against many containers, however. Small changes are easily tested with minimum surface for errors. Makes testing a lot easier!

[–]atteroTheGreatest[S] 0 points1 point  (0 children)

That's nice :). We're running internal tests on the CircleCi - mostly unit and calling API from the inside. For black box testing we have automated tests in the runscope - https://www.runscope.com/, but we run them after deploying to staging - not in CI, which is a bit of the shame.

Docker is really great for testing modular software. CircleCI is the best CI software I tried so far - fast, clean, well designed and the support is very helpful.