Recordsmavenorg.robolectric/robolectric4.13org.robolectric.junit.rules.BackgroundTestRule
OS × runtime at a glance
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Published samples
- org.robolectric/robolectric 4.13: org.robolectric.junit.rules.BackgroundTestRule This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWorg.robolectric.junit.rules.BackgroundTestRulejava 21 MIT-0 · 2026-09-09
Compatibility matrix
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| java 17 · java 17 · gradle · linux glibc · docker
Observations: PROJECT_TEST 2✓ — Verified: CONTRACT 1✓
|
LOW | 2 | 1 | 100% | 1 · 1✓ | 2026-09-17 |
| java 21 · java 21 · gradle · linux glibc · docker
Observations: PROJECT_TEST 2✓ — Verified: CONTRACT 1✓
|
LOW | 2 | 1 | 100% | 1 · 1✓ | 2026-09-17 |
| java 25 · java 25 · gradle · linux glibc · docker
Observations: PROJECT_TEST 2✓ — Verified: CONTRACT 1✓
|
LOW | 2 | 1 | 100% | 1 · 1✓ | 2026-09-17 |
| java 8 · java 8 · gradle · linux glibc · docker
Observations: PROJECT_TEST 0✓ 1✕ — Verified: CONTRACT 0✓ 1✕
|
ELEVATED FAILURE | 1 | 1 | 0% | 1 · 1✓ | 2026-09-09 |
snapshot · 2026-09-17
Failure clusters
-
observed PROJECT_TEST Evidence gap ×1 4.13 executionContext=java · os=linux · runtime=java@8 org.robolectric.junit.rules.BackgroundTestRuleEvidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09