--- name: testing-checklists description: Creating checklists for regression, smoke, and feature testing. Use when organizing test coverage. --- Create comprehensive checklists for structured manual testing and test coverage tracking<\/purpose> Creating regression test checklist<\/trigger> Creating smoke test checklist<\/trigger> Creating feature-specific checklist<\/trigger> <\/triggers> <\/skill_overview> Standard format for testing checklists<\/overview> Indicates item tested or not tested<\/description> [ ] - Not tested<\/state> [x] - Tested and passed<\/state> [!] - Tested and failed<\/state> [~] - Tested with issues<\/state> [?] - Blocked, cannot test<\/state> <\/states> <\/component> Clear description of what is being checked<\/description> Action-oriented, specific, and observable<\/format> <\/component> Outcome of the check<\/description> Pass, Fail, Partial, Blocked, N\/A<\/values> <\/component> Additional observations or issues<\/description> Documenting specific problems, workarounds, or details<\/use> <\/component> Importance level of the check<\/description> Critical, High, Medium, Low<\/values> <\/component> <\/components> <\/checklist_structure> Different types of checklists and their purposes<\/overview> Quick sanity tests on main features to ensure system is stable enough for further testing<\/description> Tests critical paths only<\/characteristic> Fast to execute<\/characteristic> Covers happy paths<\/characteristic> Run after deployment or before full testing<\/characteristic> <\/characteristics> After new deployment<\/usage> Before starting full regression test suite<\/usage> When system was down or had issues<\/usage> As first step in testing cycle<\/usage> <\/when_to_use> <\/type> Focused tests on specific functionality that was changed or fixed<\/description> Tests specific changed features<\/characteristic> Narrower scope than smoke testing<\/characteristic> Targets bug fixes and new features<\/characteristic> Faster than full regression<\/characteristic> <\/characteristics> After bug fix<\/usage> After feature implementation<\/usage> Before merging code changes<\/usage> When testing specific module<\/usage> <\/when_to_use> <\/type> Comprehensive tests to ensure existing functionality still works after changes<\/description> Covers all major functionality<\/characteristic> Tests previously working features<\/characteristic> Includes edge cases and negative scenarios<\/characteristic> Time-consuming but comprehensive<\/characteristic> <\/characteristics> Before major release<\/usage> After significant changes<\/usage> Periodically to catch regressions<\/usage> When refactoring code<\/usage> <\/when_to_use> <\/type> Comprehensive checklist for a specific feature or module<\/description> Covers all functionality of feature<\/characteristic> Includes positive and negative cases<\/characteristic> Tests integration points<\/characteristic> Used during feature development and QA<\/characteristic> <\/characteristics> During feature development<\/usage> Before feature release<\/usage> For feature-specific regression<\/usage> For training new testers<\/usage> <\/when_to_use> <\/type> Tests to verify application works across different browsers<\/description> Same tests on multiple browsers<\/characteristic> Focus on rendering and behavior differences<\/characteristic> Tests JavaScript, CSS, and user interactions<\/characteristic> <\/characteristics> Before major release<\/usage> After major CSS\/JS changes<\/usage> When browser-specific bugs reported<\/usage> <\/when_to_use> <\/type> Tests for mobile and tablet devices<\/description> Tests responsive design<\/characteristic> Tests touch interactions<\/characteristic> Tests performance on mobile<\/characteristic> Checks mobile-specific features<\/characteristic> <\/characteristics> For responsive web applications<\/usage> After UI changes<\/usage> When mobile bugs reported<\/usage> <\/when_to_use> <\/type> <\/checklist_types> Structuring checklists for clarity and efficiency<\/overview> Group related checks together<\/principle> Order checks logically (happy paths first, then edge cases)<\/principle> Mark critical items clearly<\/principle> Keep checks focused and actionable<\/principle> Include both functional and non-functional checks<\/principle> <\/organization_principles>

Setup and configuration before testing<\/description> Environment setup, test data preparation, authentication<\/examples> <\/section>

Positive test scenarios<\/description> Successful operations, valid inputs, normal usage<\/examples> <\/section>

Error handling and invalid inputs<\/description> Empty fields, invalid formats, error messages<\/examples> <\/section>

Boundary and corner cases<\/description> Maximum values, zero, special characters, concurrent operations<\/examples> <\/section>

Testing with other components<\/description> API calls, database interactions, external services<\/examples> <\/section>

Security and permission checks<\/description> Authentication, authorization, input validation<\/examples> <\/section>

Load and response time checks<\/description> Page load time, API response time, large datasets<\/examples> <\/section>

User interface and experience checks<\/description> Layout, styling, usability, accessibility<\/examples> <\/section> <\/common_sections> <\/organizing_checklists> Marking checklist items by priority<\/overview> Must work, system unusable if failed<\/description> Login, authentication, core business logic, payment processing<\/examples> Test first, block release if failed<\/action> <\/level> Important feature, affects many users<\/description> Main workflows, common operations, frequently used features<\/examples> Test early, serious if failed<\/action> <\/level> Standard feature, affects some users<\/description> Secondary features, occasional operations<\/examples> Test when time permits<\/action> <\/level> Minor feature, edge case, nice to have<\/description> Rarely used features, edge cases, minor UI issues<\/examples> Test last or skip if time limited<\/action> <\/level> <\/priority_levels> <\/prioritization> Common test scenarios to include in checklists<\/overview> Login with valid credentials<\/check> Login with invalid credentials<\/check> Login with empty fields<\/check> Forgot password flow<\/check> Password reset functionality<\/check> Logout functionality<\/check> Session timeout<\/check> Remember me functionality<\/check> Social login (if applicable)<\/check> <\/checks> <\/scenario_category> Submit with all valid data<\/check> Submit with required fields empty<\/check> Submit with invalid data formats<\/check> Field length validation (min\/max)<\/check> Special character handling<\/check> Reset\/cancel form<\/check> Form submission with network errors<\/check> Form persistence after validation errors<\/check> <\/checks> <\/scenario_category> Create new resource<\/check> Read\/view resource details<\/check> Update existing resource<\/check> Update specific fields<\/check> Delete resource<\/check> View list of resources<\/check> Search\/filter resources<\/check> Sort resources<\/check> <\/checks> <\/scenario_category> Status codes are correct<\/check> Response structure is valid<\/check> Required fields present<\/check> Data types match expectations<\/check> Error messages are clear<\/check> Pagination works correctly<\/check> Rate limiting respected<\/check> Authentication required properly<\/check> <\/checks> <\/scenario_category> Layout correct on desktop<\/check> Layout correct on mobile<\/check> Layout correct on tablet<\/check> Text is readable and properly formatted<\/check> Buttons and links work correctly<\/check> Modals and dialogs open\/close correctly<\/check> Loading indicators show appropriately<\/check> Error messages are clear and helpful<\/check> Success messages display correctly<\/check> Navigation works as expected<\/check> <\/checks> <\/scenario_category> <\/test_scenarios> Browser-specific checks<\/overview> Chrome<\/browser> Firefox<\/browser> Safari (Mac)<\/browser> Edge<\/browser> <\/browsers> Layout renders correctly<\/check> Styling applied as expected<\/check> JavaScript functionality works<\/check> Forms submit correctly<\/check> Modals and popups display correctly<\/check> Animations and transitions work<\/check> Drag and drop works (if applicable)<\/check> Audio\/video plays correctly (if applicable)<\/check> <\/checks> <\/cross_browser_testing_checklist> Device-specific checks<\/overview> Mobile phone (portrait and landscape)<\/device> Tablet (portrait and landscape)<\/device> Desktop (various resolutions)<\/device> <\/device_types> Responsive layout adapts correctly<\/check> Horizontal scrolling avoided on mobile<\/check> Touch targets large enough (min 44x44px)<\/check> Zooming works correctly<\/check> Scrolling works smoothly<\/check> Hamburger menu appears on mobile<\/check> Images resize appropriately<\/check> Text is readable at mobile sizes<\/check> Performance acceptable on mobile<\/check> Touch interactions work correctly<\/check> <\/checks> <\/mobile_testing_checklist> Basic accessibility checks<\/overview> Images have alt text<\/check> Form labels are associated with inputs<\/check> Focus order is logical<\/check> All interactive elements are focusable<\/check> Keyboard navigation works without mouse<\/check> Color contrast meets minimum requirements<\/check> Error messages are accessible to screen readers<\/check> Heading hierarchy is correct (h1, h2, h3...)<\/check> Links have descriptive text<\/check> Dynamic content changes announced to screen readers<\/check> No seizure-inducing flashing content<\/check> <\/checks> <\/accessibility_checklist> Performance-related checks<\/overview> Page loads within acceptable time<\/check> API responses are fast<\/check> Large images optimized<\/check> No console errors or warnings<\/check> No memory leaks (check devtools)<\/check> Animations are smooth (60fps)<\/check> No layout thrashing<\/check> Database queries are optimized<\/check> Caching working correctly<\/check> Bundle size is reasonable<\/check> <\/checks> <\/performance_checklist> Documenting checklist execution<\/overview> Execution date and time<\/field> Tester name<\/field> Environment tested (staging, production, local)<\/field> Browser\/device information<\/field> Overall result (Pass\/Fail\/Partial)<\/field> Number of items passed\/failed\/blocked<\/field> Links to bug reports for failed items<\/field> Notes and observations<\/field> Recommendations for next steps<\/field> <\/documentation> <\/tracking_checklist_results> Keeping checklists up to date<\/overview> Add new checks for new features<\/task> Remove checks for deprecated features<\/task> Update checks when functionality changes<\/task> Review and prioritize based on recent bugs<\/task> Archive old versions before major changes<\/task> Solicit feedback from testers on usability<\/task> Keep checklists focused and manageable in size<\/task> <\/maintenance_tasks> <\/checklist_maintenance> Mistakes to avoid when creating checklists<\/overview> Checklists become too long and unwieldy<\/description> Tests skip items or rush through<\/consequence> Split into smaller, focused checklists<\/solution> <\/pitfall> Items are too vague or subjective<\/description> Results vary between testers<\/consequence> Make items specific, observable, and verifiable<\/solution> <\/pitfall> Checklists not updated when features change<\/description> Testing outdated functionality, missing new features<\/consequence> Regular review and update cycle<\/solution> <\/pitfall> No prioritization of items<\/description> Critical items may be skipped when time is limited<\/consequence> Mark priority levels clearly<\/solution> <\/pitfall> Checklist items not testable<\/description> Items cannot be verified objectively<\/consequence> Ensure items are observable and measurable<\/solution> <\/pitfall> <\/common_pitfalls>