> For the complete documentation index, see [llms.txt](https://carec.gitbook.io/carec-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://carec.gitbook.io/carec-docs/documentation/development/testing-strategy.md).

# Testing Strategy

CAREC uses layered tests so defects are found before hardware and user exposure increase.

| Layer               | Examples                                          |
| ------------------- | ------------------------------------------------- |
| Unit                | Geometry, limits, state transitions, parsers      |
| Component           | Sensor adapter, planner, safety rule, drive mock  |
| Contract            | Messages, units, frames, timeouts, compatibility  |
| Integration         | Perception-to-planning, arbitration-to-drive      |
| Simulation          | Accessible navigation and safety scenarios        |
| Fault injection     | Stale sensor, lost localization, stuck command    |
| HIL                 | Real controller/sensor with simulated environment |
| Unoccupied hardware | Bench and controlled course                       |
| Reliability         | Power cycles, burn-in, battery, environment       |

## Blocking changes

Pull requests affecting motion commands, coordinate frames, timing, safety limits, mode transitions, drive interfaces, sensor validity, localization confidence, or emergency behavior require explicit test evidence and designated review.

A failed safety regression blocks the relevant merge or release unless the owner records a bounded waiver, rationale, compensating control, and expiration.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://carec.gitbook.io/carec-docs/documentation/development/testing-strategy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.