# `Mutare.Sandbox.Command.Result`
[🔗](https://github.com/foxbenjaminfox/mutare/blob/v0.2.1/lib/mutare/sandbox/command/result.ex#L1)

The typed outcome of one `mix test` mutant run.

A raw exit status is ambiguous: a non-zero code can mean a test failed (the
mutation was caught) *or* that the harness never reached a verdict at all (a
compile error, a missing dependency, a filesystem race). Collapsing both into
"non-zero ⇒ killed" silently inflates the score with infrastructure failures.

So `Mutare.Sandbox.Command` decodes the exit status against the run-side
contract implemented in `outcome/1` and returns this struct, whose `outcome`
*names* what happened. The runner maps that name onto a `Mutare.Result.status`
— and an `:harness_error` is kept out of the score's denominator, never
miscounted as a kill. `exit_status` is retained for diagnostics.

# `t`

```elixir
@type t() :: %Mutare.Sandbox.Command.Result{
  duration_ms: non_neg_integer() | nil,
  exit_status: non_neg_integer(),
  outcome: Mutare.Sandbox.Command.outcome(),
  output: String.t()
}
```

---

*Consult [api-reference.md](api-reference.md) for complete listing*