Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
In-process test harness for apps built on the standout CLI framework.
[TestHarness] is a fluent builder over the injection seams a test
needs: env vars, cwd, stdin, clipboard, the representation, the color
policy and whether stdout is a terminal, theme facts on
TargetProperties, and tempdir fixtures. run applies every override,
calls into the app in-process, and a Drop impl restores everything on
success or panic. [TestResult] then exposes the run's
result values as data ([TestResult::result]), the rendered bytes
([TestResult::stdout]) and the delivery decision
([TestResult::delivery]) separately, plus structured facts like style-tag
resolutions that a text search can't get at; [assert_page_snapshot!]
and [matrix] pin a rendered page across representation/color/theme cells.
There is no in-process TTY simulation: [TestHarness::run_process]
spawns the real binary and [TestHarness::run_pty] (Unix) gives it a
pseudo-terminal. The fixed TargetProperties defaults and the
#[serial] rule for tests that mutate env or cwd are in
docs/topics/testing.md.