What happens
Running yarn test:integration twice against the same local kernel fails, while a fresh kernel (as in CI) passes:
Source/**/when_replaying_an_older_generation.integration.spec.ts failed two reactor-observation tests on the first local run.- On the next run against the same kernel,
when_erasing_a_subject.integration.spec.ts failed because a MongoDB database name left over from the migration spec (event store MigrationReplayMissing…) exceeds MongoDB's database-name length limit.
On a freshly started kernel all 7 files and 53 tests pass.
Expected
Integration specs use short, unique event store names and do not depend on state left by other specs, so they pass when run repeatedly against one local kernel.
Impact
Local integration runs are flaky unless the kernel container is recreated each time. CI is not affected.
What happens
Running
yarn test:integrationtwice against the same local kernel fails, while a fresh kernel (as in CI) passes:Source/**/when_replaying_an_older_generation.integration.spec.tsfailed two reactor-observation tests on the first local run.when_erasing_a_subject.integration.spec.tsfailed because a MongoDB database name left over from the migration spec (event storeMigrationReplayMissing…) exceeds MongoDB's database-name length limit.On a freshly started kernel all 7 files and 53 tests pass.
Expected
Integration specs use short, unique event store names and do not depend on state left by other specs, so they pass when run repeatedly against one local kernel.
Impact
Local integration runs are flaky unless the kernel container is recreated each time. CI is not affected.