An asset is still a Python function, so the fastest test calls it directly: assert paid_orders(raw_orders=[...]) == [...]. Inputs are plain arguments; nothing is loaded from storage.
If the asset takes a context, build one: dg.build_asset_context(partition_key="2026-11-07"), and pass it first. Calling such an asset without a context raises an error that says so. Resources are keyword arguments: pass a small fake with the same methods, so the test never touches a real API.
In this workspace you edit test_assets.py and run pytest in the terminal. The check runs your tests against the real assets, which must pass, and against a copy with a bug in it, which your tests must catch. A test that passes on broken code is not testing anything.
Call the asset with a small input you wrote by hand.