7 posts
Testing only through the UI is slow and misses what anyone can do with curl. Write your first pytest tests against the API: the €50.00 boundary, the order chain from login to delete, and the two-user test for broken object level authorisation.
Testing with whatever values come to mind misses the bug at the edge and leaves a coverage claim nobody can check. Pick values with partitions, boundaries and decision tables, explore in timed sessions, and write bug reports a developer can reproduce.
Learning testing tools in a random order leaves you with a suite that runs but can't say what it covers. Learn in order instead: test design, one language and the API, the UI, the checks functional tests miss, CI, then AI, all on one checkout.
