---
title: "Test and tool containers"
description: "Run test cases and tools in your own containers inside a RemotiveTopology instance, with any test framework, next to ECUs and behavioral models."
source: https://developer.remotivelabs.com/docs/remotive-topology/usage/test/test-containers
last_updated: 2026-11-20
---

# Test and tool containers

RemotiveTopology also provides a way to run arbitrary containers inside the topology, for example test cases or other tools. Unlike [ECU containers and behavioral models](https://developer.remotivelabs.com/docs/remotive-topology/usage/ecus.md), these containers don't belong to any ECU. Instead they communicate with the ECUs through the TopologyBroker, which is reachable at `http://topology-broker.com:50051` inside the topology.

A common use case is to run test cases. By using an arbitrary container you can use whatever test framework you want:

```yaml
containers:
  tester:
    profiles: [tester]
    build:
      dockerfile: ../tests/Dockerfile
    volumes:
      - ../tests:/app
    working_dir: /app
    command: "pytest --broker_url=http://topology-broker.com:50051 -s -vv"
```

The container properties are the same as for ECU containers and behavioral models. They mirror the service properties in Docker Compose, see the [container schema](https://developer.remotivelabs.com/apis/json/topology#oneOf_i1_containers_additionalProperties).

## Profiles

The containers can have one or more profiles. These correspond to profiles in Docker Compose. To run the preceding tests, [build the topology](https://developer.remotivelabs.com/docs/remotive-topology/usage/run.md#prepare) and start it with the `tester` profile:

```sh
docker compose -f build/mytopology/docker-compose.yml --profile tester up
```

Containers without a profile always start. Using a profile for tests lets you start the topology without them, for example in [interactive mode](https://developer.remotivelabs.com/docs/remotive-topology/usage/run.md#interactive-mode). See [Running tests](https://developer.remotivelabs.com/docs/remotive-topology/usage/run.md#running-tests) for how to shut down the topology when the tests have completed.
