Feature: eventing_integration_test
Table of Contents
This page is one authored MASD feature in ORE Studio Variability Model § "Projection configuration: how an existing artefact family is shaped". Any profile that fixes this feature's value links here rather than restating its effect.
Identity
| Field | Value |
|---|---|
| Literal name | :ores.cpp.eventing-integration-test.enabled: |
| Bundle | ores.cpp.testing |
| Type | bool |
| Default | false |
Effect
Enables the ores.cpp.eventing-integration-test facet, which generates a
projects/{component_core_dir}/tests/{entity}_eventing_integration_tests.cpp
Catch2 test case per entity. The test writes the entity via its repository,
waits for the resulting NATS entity-changed notification on the wire, and
asserts the payload matches — no mocks, real Postgres LISTEN/NOTIFY, real
NATS. Guards against regressions in the full eventing pipeline (PG trigger →
event source → event bus → NATS publish) that unit tests alone cannot catch.
Structural consequence
Adds one test source file per entity. Requires a running NATS server and Postgres with LISTEN/NOTIFY support during test execution.
Used by
See also
- ORE Studio Variability Model — the bundle this feature belongs to.