rules_itest
rules_itest copied to clipboard
Bazel rules for integration testing services
**Observed Behavior:** When a service managed by `rules_itest`'s `runner` is stopped (e.g., via `svcctl`'s `/v0/kill` endpoint) and subsequently waited upon (via `svcctl`'s `/v0/wait` endpoint), the `/v0/wait` call can fail with...
When a service_test wrapping a go_test times out, it kills the go test indirectly via a context cancellation on CommandContext, inhibiting the go test from dumping useful stack traces to...
Firstly, after some years with bazel I have just come across this repo from a stackoverflow comment. Really cool stuff, it was just what we were missing. Thanks! It would...
This PR supports additional substitutions on env values supplied in env parameter to itest rules. Substitutions are: 1) $(location... etc as previously supported 2) $(OTHERENV)/extra - substitute a different envvar...
The use case is for testing cron jobs. The ask is to not start a specific itest_service to allow the service_test to exclusively start it through svcctl. This allows to...
First of all let me say that the rationale behind this project is incredible! I've been watching at testcontainers for a while, and even though it's great from the developer...
I can't find this in the documentation: Assume that I have multiple service_tests that all depend on a single itest_service with fixed port. Questions - does rules_itest handle this gracefully...
Thanks for creating this module! I'm enjoying the language-agnostic way of managing test dependencies. In adopting this for a repository, I discovered that custom `args` supplied to the underlying test...