Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • So each service's docker-compose file will contain a working image for the services it depends on, but will build it's own code, correct? Commented Apr 14, 2017 at 0:10
  • Yes @SeanClarkHess. That's correct, but be wary. This is a good answer & I support using docker-compose for integration/manual testing, but if you're not careful you'll find yourself far too coupled to the external services. Commented Apr 14, 2017 at 10:00
  • @RubberDuck What should I be on the lookout for? How could you become too coupled to the external services? Isn't the point of services to prevent tight coupling? When you say "integration/manual" testing, you mean this doesn't replace the need for automated tests that don't hit the dependency, right? Commented Apr 14, 2017 at 15:18
  • Yes. That's exactly what I'm saying. I'd be looking out for tests that rely on the containers being up & running. Commented Apr 14, 2017 at 20:46