Website Exploratory Testing
Goal
ultrathink
You are tasked with performing comprehensive exploratory testing on a website using the user's configured browser automation tool.
Your goal is to identify functional and non-functional deficiencies through systematic exploration.
Setup Instructions
- Use the available browser automation tool (see CLAUDE.md for configured tool)
- Create a sub-task for browser operations to manage context window efficiently
Authentication Handling
IMPORTANT: If you encounter login pages, authentication requirements, CORs errors, or areas requiring user credentials:
- STOP testing immediately
- Document what you've found so far
- Ask the user to provide necessary login credentials (username/password, API keys, etc.)
- Wait for credentials before proceeding with authenticated areas
- Once provided, continue testing both public and authenticated sections
Testing Methodology
Perform exploratory testing using these established techniques:
Core Testing Areas
- User Journey Testing: Navigate critical user paths (registration, login, checkout, etc.)
- Boundary Testing: Test form inputs with edge cases (empty, max length, special characters)
- Error Handling: Deliberately trigger errors to test graceful failure
- Accessibility Testing: Check ARIA labels, keyboard navigation, color contrast
- Responsive Design: Test different viewport sizes and orientations
- Performance: Monitor page load times and resource usage
- Security Basics: Check for exposed sensitive data, insecure forms
- Cross-browser Compatibility: Test core functionality across browsers
- Authentication Flow: Test login/logout, session management, password reset (when credentials provided)
Testing Approach
- Start with homepage reconnaissance - understand site structure
- Identify and test all publicly accessible interactive elements
- Stop and request credentials if authentication is required
- Test authenticated areas once credentials are provided
- Follow happy path user journeys first, then explore edge cases
- Test error scenarios and recovery paths
- Validate accessibility and usability patterns
- Check mobile responsiveness and touch interactions
- Monitor console errors and network issues throughout
Issue Classification
🔴 CRITICAL (Red X):
- Broken core functionality
- Security vulnerabilities
- Accessibility violations preventing usage
- Site crashes or unrecoverable errors
- Authentication bypasses or exposures
⚠️ WARNING (Yellow Warning):
- Poor UX patterns
- Minor accessibility issues
- Performance concerns
- Inconsistent behavior
- Weak authentication patterns
✅ PASSED (Green Checkmark):
- Working functionality
- Good user experience
- Proper error handling
- Accessibility compliance
- Secure authentication flow
Report Requirements
Create a comprehensive markdown report saved as exploratory_testing_report_YYYY-MM-DD_HH-MM-SS.md (use current date and timestamp) with:
Structure:
- 🔴 CRITICAL ISSUES (at top for visibility)
- ⚠️ WARNINGS & CONCERNS
- ✅ PASSED TESTS
- AUTHENTICATION STATUS (what was tested with/without login)
- EXECUTIVE SUMMARY (2-3 readable paragraphs)
- RECOMMENDED ACTION PLAN (prioritized steps to resolve issues)
Content Guidelines:
- Include specific steps to reproduce issues
- Capture screenshots for visual problems
- Note which browsers/devices were tested
- Clearly distinguish between authenticated vs non-authenticated testing
- Provide clear, actionable recommendations
- Use proper markdown formatting with checkboxes and status icons
Execution Notes
- Work systematically through each testing area
- Document everything you test, even if it passes
- Always stop and ask for credentials when auth is encountered
- When you find issues, explore related functionality for patterns
- Take screenshots of important findings
- Keep detailed notes of your testing process
Please provide the website URL you'd like me to test when ready to begin.
1---2name: exploratory-testing3description: Perform comprehensive exploratory testing on a website using browser automation, covering user journeys, forms, errors, accessibility, responsiveness, performance, and security basics. Use when asked to QA a site, explore an app, find bugs, or produce a browser testing report.4metadata:5 source: https://skillmd.com/skills/sdiamante13/exploratory-testing6 context: fork7---89# Website Exploratory Testing1011## Goal1213ultrathink1415You are tasked with performing comprehensive exploratory testing on a website using the user's configured browser automation tool.1617Your goal is to identify functional and non-functional deficiencies through systematic exploration.1819## Setup Instructions20211. Use the available browser automation tool (see CLAUDE.md for configured tool)222. Create a sub-task for browser operations to manage context window efficiently2324## Authentication Handling2526**IMPORTANT**: If you encounter login pages, authentication requirements, CORs errors, or areas requiring user credentials:27- **STOP** testing immediately28- Document what you've found so far29- Ask the user to provide necessary login credentials (username/password, API keys, etc.)30- Wait for credentials before proceeding with authenticated areas31- Once provided, continue testing both public and authenticated sections3233## Testing Methodology3435Perform exploratory testing using these established techniques:3637### Core Testing Areas38- **User Journey Testing**: Navigate critical user paths (registration, login, checkout, etc.)39- **Boundary Testing**: Test form inputs with edge cases (empty, max length, special characters)40- **Error Handling**: Deliberately trigger errors to test graceful failure41- **Accessibility Testing**: Check ARIA labels, keyboard navigation, color contrast42- **Responsive Design**: Test different viewport sizes and orientations43- **Performance**: Monitor page load times and resource usage44- **Security Basics**: Check for exposed sensitive data, insecure forms45- **Cross-browser Compatibility**: Test core functionality across browsers46- **Authentication Flow**: Test login/logout, session management, password reset (when credentials provided)4748### Testing Approach491. Start with homepage reconnaissance - understand site structure502. Identify and test all publicly accessible interactive elements513. **Stop and request credentials** if authentication is required524. Test authenticated areas once credentials are provided535. Follow happy path user journeys first, then explore edge cases546. Test error scenarios and recovery paths557. Validate accessibility and usability patterns568. Check mobile responsiveness and touch interactions579. Monitor console errors and network issues throughout5859## Issue Classification6061**🔴 CRITICAL (Red X)**:62- Broken core functionality63- Security vulnerabilities64- Accessibility violations preventing usage65- Site crashes or unrecoverable errors66- Authentication bypasses or exposures6768**⚠️ WARNING (Yellow Warning)**:69- Poor UX patterns70- Minor accessibility issues71- Performance concerns72- Inconsistent behavior73- Weak authentication patterns7475**✅ PASSED (Green Checkmark)**:76- Working functionality77- Good user experience78- Proper error handling79- Accessibility compliance80- Secure authentication flow8182## Report Requirements8384Create a comprehensive markdown report saved as `exploratory_testing_report_YYYY-MM-DD_HH-MM-SS.md` (use current date and timestamp) with:8586### Structure:871. **🔴 CRITICAL ISSUES** (at top for visibility)882. **⚠️ WARNINGS & CONCERNS**893. **✅ PASSED TESTS**904. **AUTHENTICATION STATUS** (what was tested with/without login)915. **EXECUTIVE SUMMARY** (2-3 readable paragraphs)926. **RECOMMENDED ACTION PLAN** (prioritized steps to resolve issues)9394### Content Guidelines:95- Include specific steps to reproduce issues96- Capture screenshots for visual problems97- Note which browsers/devices were tested98- Clearly distinguish between authenticated vs non-authenticated testing99- Provide clear, actionable recommendations100- Use proper markdown formatting with checkboxes and status icons101102## Execution Notes103104- Work systematically through each testing area105- Document everything you test, even if it passes106- **Always stop and ask for credentials when auth is encountered**107- When you find issues, explore related functionality for patterns108- Take screenshots of important findings109- Keep detailed notes of your testing process110111Please provide the website URL you'd like me to test when ready to begin.