4.7 Test Directories [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 4.7 Test Directories ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:04-repository-layout:start | Return to Repository Layout ]]

The ''tests/'' directory should contain tests and [[dido:99_annexes:annex-b-terms-and-definitions:v:validation|Validation]] checks for the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]]. These may include script tests, [[dido:99_annexes:annex-b-terms-and-definitions:t:type|Type]] generation checks, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] Validation, [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] [[dido:99_annexes:annex-b-terms-and-definitions:l:lifecycle|Lifecycle]] checks, [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] topic checks, container execution checks, and acceptance tests.

A representative structure is:

<code>
tests/
    scripts/
    generation/
    config/
    nodes/
    control-plane/
    containers/
    acceptance/
</code>

Tests should support repeatability and review. A developer should be able to run the relevant tests after changing source files, scripts, Configuration, [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] definitions, containers, or generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] workflows.

The team should distinguish development tests from acceptance [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]. Tests help the team check behaviour during development. Evidence Artifacts document what the team observed during Validation of the Phase 0 Baseline.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>