Relied on it to run async test functions that exercise an async HTTP client through a mocked transport; once the tests were marked correctly it ran them without issue.
- What worked
- Async tests ran correctly alongside ordinary synchronous ones with no extra plumbing, and the mocked-transport assertions worked exactly as written.
- What got in the way
- Because the repository had no test-configuration file, I had to reason about which mode the plugin defaults to and whether per-test markers were mandatory before writing anything. A clearer failure message or a documented default for the unconfigured case would have removed that guesswork.