Expand description
Structs§
- Case
Index - Position of a case in a plan.
- Clause
- One top-level condition of a condition block. Top-level conditions are conjunctive and side-effect free, so evaluating them separately at the same moment gives the same verdict as the whole block.
- Content
Id - Stable identity of a case’s executable content: changes when its start,
steps, fixtures or AI mode change, but not when lines merely move or marks
such as
#skipare added. - EventId
123ornamespace.123.- Event
Info - A top-level
country_eventseen while collecting, used to validatefiretargets and to estimate what a case touches. - Fixture
- A named, reusable preparation step, executed in the case’s country scope before the case’s own steps. There is no teardown: every session is discarded after it runs.
- Fixture
Name - Name of a fixture: an ASCII identifier.
- Game
Date - A full EU4 calendar date (no leap years), formatted
YYYY.M.D. - Helper
File - A helper event file copied into the generated test layer.
- Marker
- Marks
- Native
Block - Native script, without its outer braces.
- NodeId
- Human-readable address of a case, modeled on pytest node IDs:
my-mod::events/reforms.txt::reforms.1::grants_flag[tag=DAN]. - RunId
- Identifies one execution of the test command. It appears in generated script and log markers, so it is restricted to a safe alphabet.
- Start
- Tag
- Three uppercase ASCII letters/digits starting with a letter, such as
SWE. - Test
Case - XFail
Enums§
- AiMode
- Case
Name - A case’s name within its target. Unnamed inline cases use their position among the annotations on the same event, which shifts when annotations are added or removed.
- Session
Request - Step
Constants§
- MAX_
ADVANCE_ DAYS - Upper bound of real game days a single test may advance in total.
Functions§
- identifier
- An ASCII identifier: a letter or
_, then letters, digits or_.