Why We Should Care About Test Execution Output in Safety-Critical Industries
summary
Bazel does not cache test output, which breaks ASPICE-style deliverables used by BMW and NVIDIA; forking Bazel is costly. The claim is to run test as part of build so test binaries act as tools and produce human- and machine-readable reports that become build artifacts. Implementation uses a wrapper lum_cc_test and a quality config alias to produce report targets during bazel build, leveraging Bazel caching to avoid re-running tests; it works but increases exposure to flaky tests.
AI-written summary · about
related talks
11mLightning Talk – Testing Bazel’s Remote Execution API
28mIntegration testing with Bazel
45mSelective Testing + Q&A
22mCollecting Code Coverage With Bazel
25mBad Behaviour: Automating System-level Safety Testing Using Open Source Tools
45mUsing AI, statistics, and set theory to know what to test
25mBuild and Test Caching in Go
47mThe Valley of Success