CargoTestResult
The result of a test run.
interface in bldr/rust-tools
The result of a test run.
Properties
diagnostics: Diagnostics
property
What the compiler said while building the suite.
From the --no-run pass, which is the one that can produce any. A suite
that does not compile has no cases to report and this is the whole of
what it has to say.
See Diagnostics.
failed: Value<boolean>
property
Whether the command exited non-zero.
Lazy: reading it is what runs the command, exactly like forcing any other artifact. Nothing here runs because it was described.
Only ever true for a call that passed
OnTheFly.ignoreFailures. Without it a failure has already failed
the build, so by the time anyone could read this it can only say false —
which is not a trap so much as the point: the default is that failures
stop the build, and you opt out to inspect them.
See Value.
log: File
property
Everything the command wrote to stdout and stderr.
This is what a registered gate registers, so a failure's output is kept as the target's artifact rather than scrolling past in a build log.
See File.
report: Report
property
The individual cases, as a report bldr test can read.
A test failure is data and lands here; a compile failure is not, and fails the command. The two are told apart rather than merged, so "the tests ran and three failed" never looks like "nothing compiled".
See Report.