This repository contains a Bazel ruleset for running services in a hermetic way. This capability can be used to provision a dev environment, or to run tests against the services.
For example, you may want to run integration tests that depend on having a DB, redis, etc. running. Or you may be integration-testing first party binaries.
With this ruleset, each test can declare the set of services that it expects, and it is guaranteed to be provisioned with a fresh set of services that have passed healthchecks before the test code is executed.
This ruleset also integrates with ibazel to provide incremental hot-reload capabilities.
See the documentation in the docs folder.
Note that the implementation of per-service reload under ibazel works by injecting a cache-busting input, so it is disabled by default to keep tests cacheable. You can enable it with the @rules_itest//:enable_per_service_reload flag.
Note that ibazel uses cquery which does not accept Starlark flags, and common in .bazelrc also does not work with Starlark flags, so you may need a setup like this:
.bazelrc
build:enable-reload --@rules_itest//:enable_per_service_reload
fetch:enable-reload --@rules_itest//:enable_per_service_reload
query:enable-reload --@rules_itest//:enable_per_service_reload
ibazel run --config enable-reload //path/to:target
Basic usage examples (Go or Node binaries) can be found under the the tests folder.
More advance usage examples (mysql, redis, dynamodb) can be found under the examples folder.