-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run specs through docker image #2
Comments
Docker scenarios tend to involve multiple services on different hostnames; a poor fit for the NODE concept in testbeat that sort of assumes that tests and assertions target the same VM. For a docker concept to be worthwhile we might have to add a host/service argument in the spec syntax, in |
I would like to avoid that. Suggest combination of:
Testing multiple different services can be done in separate test runs? |
Two benefits if Testbeat can run from docker image:
link
Will it also be able to test a service by name in the host's hosts file? If so there's not many drawbacks.
Specs can be for example
/spec/*_spec.rb
by default, overridable with env./spec
can be COPY'd to in a downstream Dockerfile, or simply mounted as volume.NODE
is no longer a good name, and maybe never was, for the System Under Test. In contexts of Docker or Kubernetes it is rather a Service. We can keep the NODE env for backwards compatibility but use something else to name the link.svc
orservice
orsut
ortarget
The text was updated successfully, but these errors were encountered: