Concurrency · interview question

If you wrote a test around async def and await, what should the test prove first?

Multiple choiceEasychapter-15-curatedpremiumconcurrencyasync-def-and-await

python

import asyncio

async def fetch_order(order_id: str) -> dict[str, str]:
    await asyncio.sleep(0.1)
    return {"order_id": order_id}

Keep async def and await implicit so the script stays short and hope the next engineer infers the rule.That the rule behaves correctly at the boundary cases the lesson is trying to make explicit.Solve the symptom with comments only and avoid changing the code shape around async def and await.Delay clarity until production traffic reveals the edge case and then patch it under pressure.

Answer and explanation

Correct answer

B. That the rule behaves correctly at the boundary cases the lesson is trying to make explicit.

Why

Good tests make the design safer to change because they lock in the meaningful behavior rather than surface-level implementation details.

Test yourself on Concurrency

A free test with instant, explained results. No account needed.

Start free test

All Concurrency questions →

If you wrote a test around async def and await, what should the test prove first?

Correct answer

Why

More Concurrency questions