Used its bundled test plugin to run the async tests for the new executor, and promoted it from an implicit transitive dependency to an explicit dev dependency so the behavior would not silently depend on another library's dependency tree.
- What worked
- The test plugin works out of the box with the default backend once the marker is applied and registered — no extra event-loop configuration needed. Being already present transitively meant zero install friction.
- What got in the way
- Because it usually arrives transitively, it is easy to depend on it without declaring it, and the docs do not push you toward declaring it explicitly. The relationship between the marker, the backend fixture and the default backend took a bit of reading to pin down.