testing-checklist

Verification goal (smoke/sanity/regression) List of critical scenarios and modules Environment constraints and access List of recent changes/fixes Release risks and priorities </input_requirements> Quick check that the system works overall Check a specific area after changes Check that changes did not break existing behavior </checklist_types> Blocks the release Critical, but has a workaround Important for UX, but not blocking Checklist items are verifiable and unambiguous Each item is tied to user value No duplicates or overlaps between items Items are short and quick to execute If result recording is needed, use a single consistent format </construction_rules> Critical user paths Authorization and access control Core CRUD operations Errors and data validation Do not turn a checklist into a full set of test cases Do not include items without a clear success criterion Do not mix smoke and regression in one list Do not include items that depend on another item without an explicit link </do_not> Log in with valid credentials Create an entity via the primary form Show an error for an empty required field P0: Verify admin role access to key sections </example_items>