bazel-integration-testing
bazel-integration-testing copied to clipboard
bazelbuild
Framework for integration tests that call Bazel
Unfortunately our linter was stuck on bazel 0.11.0 and now when we upgraded it to 0.17.1 we saw we're really behind. It's currently red on ci
This PR implements #64. This is probably a work in progress concerning the API. The feature here allows one to import to the scratch workspace an executable that was compiled...
I think that in terms of ergonomics: 1. The static members in WorkspaceDriver should be moved to an Environment class that would be shared to different instances of WorkspaceDriver (through...
So this is related to the download cache issue (https://github.com/bazelbuild/bazel-integration-testing/issues/63) but operates at a different level. Here, the issue is not to improve performance in general, but only locally, in...
Essentially I'd like to expose an API like `addExternalRepository(repoName`) which copies the repo directory from runfiles and adds it to the test workspace (as a local repository). Part of the...
The idea is that we allow outputing the logs inner tests so that the developer can see in which way the inner test failed and maybe also assert on it....
Sorry in advance for the cheesy name :) Imagine you want to write an integration test for a rule that depends on an executable with runfiles that is somewhat expensive...
currently you can be very explicit and control the bazel version or just use the default versions from the library which is a lot. I'd like it to be easy...
The idea is that the matcher takes care of outputting the workspace layout and on asserting the status code. Exists in successfulExitCode, commandDescription https://github.com/bazelbuild/bazel-integration-testing/blob/master/javatests/build/bazel/tests/integration/BazelBaseTestCaseTest.java#L64
Metadata
Owner
Metadata
Framework for integration tests that call Bazel