Designing mesh flows without tangling cleanup

Mesh tests tempt you to script API first, UI second, cleanup whenever. That whenever is where sessions linger.

We recommend writing cleanup as a numbered list beside the test, then mirroring those numbers in code comments at the tearDown site. Sounds pedantic until a midnight deploy proves otherwise.

Correlation IDs belong in both API and UI failure bundles so support can stitch timelines without asking you for grep recipes.

Mesh flows are powerful; discipline keeps them from becoming folklore.