# Validate an Elbrus distribution

An Elbrus verification report needs the specific machine and operating environment, the executable tested and the commands actually run. This page describes useful evidence for a target check; it does not prescribe an unverified build toolchain or imply that a distribution is available for every target.

Consult [installation](https://coordinatordb.com/docs/get-started/setup/install) for the current installation procedure. Prepare a separate directory with the executable, supplied configuration and a disposable database.

## Check one interface at a time

After starting the server, verify native SQL:

```sh
./coordinator client --database data --query "SELECT 2 + 3 AS total FORMAT csv"
```

Expect `5`. If the application uses HTTP, also run the health and SQL checks from the [HTTP interface guide](https://coordinatordb.com/docs/concepts/features/interfaces/http). A working native connection does not verify the HTTP listener.

## Describe the result precisely

Include launch failures, configuration errors and query errors as separate observations. For a successful check, add the application's row types, format round trips and transaction behavior to the evidence. Avoid comparing timing from unlike execution environments. The [integration test guide](https://coordinatordb.com/docs/resources/develop-contribute/integrations/testing-your-integration) provides a useful starting checklist for the application's observable contract.