SECURITY WARNING: Never run commands you don't understand. Always review code before execution. Use at your own risk.
Testing New Added 30 August 2026

pytest: async def functions are not natively supported

pytest collects an async test, has no event loop to run it in, and skips the body, so the test reports as passed or warns while asserting nothing. A plugin has to drive the coroutine.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix
pip install pytest-asyncio

# pyproject.toml
[tool.pytest.ini_options]
asyncio_mode = "auto"

# Or mark each test explicitly
import pytest

@pytest.mark.asyncio
async def test_fetch():
    assert await fetch() == 200

How to diagnose Testing errors

Test errors divide into infrastructure problems (the framework cannot find or load your tests, fixtures or modules) and flakiness, which is the more expensive category. End-to-end timeouts are almost always a race between the test and the application, and the durable fix is to wait for a condition (an element, a network response, a state change) rather than for a duration.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

  1. Run a single failing test in isolation. If it passes alone but fails in the suite, you have shared state or test ordering dependence.
  2. For Cypress and Playwright timeouts, use the trace viewer or video to see what the page actually showed. The element usually exists but is covered, detached, or not yet interactive.
  3. Replace fixed waits with condition-based waits. waitForSelector and auto-retrying assertions eliminate an entire class of flakiness.
  4. For collection and module-resolution errors, check the framework's rootDir/testPaths configuration and the presence of __init__.py or conftest.py where the framework expects it.
  5. Review snapshot diffs rather than updating them reflexively. A changed snapshot is sometimes a real regression.

Tools worth reaching for

  • playwright show-trace
  • pytest -x -vv --tb=long
  • jest --runInBand
  • cypress open
  • test retry analytics

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

pytest-asyncio.readthedocs.io

Related Testing errors

See all 18 Testing errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.