Test what users see, how systems communicate, and whether important product rules hold.
Loading progress…
Lesson 1
Testing produces evidence that specified behaviour holds under selected conditions and exposes uncertainty that remains outside those conditions. Learn the founder decision, practical evidence, and warning signs that matter.
Lesson 2
Test what users see, how systems communicate, and whether the product’s rules continue to hold under incorrect inputs.
Lesson 3
User interface testing checks whether people can perceive, understand, operate, and recover from the product's visible interactions. Learn the founder decision, practical evidence, and warning signs that matter.
Lesson 4
Responsive testing checks layout, content priority, controls, and input behaviour across representative viewport sizes and devices. Learn the founder decision, practical evidence, and warning signs that matter.
Lesson 5
Form testing verifies accepted input, rejected input, feedback, preservation, submission, and the same rules at the server boundary. Learn the founder decision, practical evidence, and warning signs that matter.
Lesson 6
Loading and failure testing verifies what the user sees and can safely do while work is delayed, unavailable, partial, or unsuccessful. Learn the founder decision, practical evidence, and warning signs that matter.
Lesson 7
An API endpoint is a defined network address and operation through which a client requests or changes a specific capability. Learn the founder decision, practical evidence, and warning signs that matter.
Lesson 8
Postman is a client for constructing, sending, organising, and inspecting API requests independently of the product interface. Learn the founder decision, practical evidence, and warning signs that matter.
Lesson 9
Request testing distinguishes valid operations from malformed, impossible, unauthenticated, and insufficiently authorised attempts. Learn the founder decision, practical evidence, and warning signs that matter.
Lesson 10
Workflow testing follows a user goal across screens, services, rules, messages, and stored state from starting condition to final outcome. Learn the founder decision, practical evidence, and warning signs that matter.
Lesson 11
Boundary testing examines values at and around limits, while impossible-state testing challenges combinations the product should never permit. Learn the founder decision, practical evidence, and warning signs that matter.
Lesson 12
Duplicate actions repeat an intended operation, while race conditions make results depend on the timing of concurrent work. Learn the founder decision, practical evidence, and warning signs that matter.
Lesson 13
Permission testing verifies that each identity can perform only allowed actions on allowed resources, including through direct requests. Learn the founder decision, practical evidence, and warning signs that matter.
Lesson 14
Logic mistakes arise from misunderstood rules, missing conditions, incorrect sequencing, or false assumptions regardless of whether code was written by a person or model. Learn the founder decision, practical evidence, and warning signs that matter.
Lesson 15
An MVP test plan lists priority claims, environments, data, steps, expected results, owners, evidence, and release decisions. Learn the founder decision, practical evidence, and warning signs that matter.