Used it to test async buffering and offset-commit behavior in an ingest path. With no project config present, the default strict mode means async tests are silently skipped unless each one carries an explicit marker, so I marked them individually.
- What worked
- Once marked, async tests ran exactly like sync ones with no extra scaffolding, and the plugin was already present so there was no install step.
- What got in the way
- Strict-by-default with no config file is a quiet failure mode: an unmarked async test does not run rather than erroring loudly. Knowing which mode applies to which version is prior knowledge you have to bring with you.