Pre-Test Diagnosis: What Can and Can't Be Tested
Before exploration begins, Rihario analyzes your page to understand what can be tested and what might block testing. This diagnosis phase identifies testable elements, detects blockers, and assesses page complexity. It helps the AI plan exploration and avoid wasting time on untestable pages.
What Happens During Diagnosis
The diagnosis phase (typically 5-10 seconds) analyzes:
- Page structure - What's on the page
- Interactive elements - What can be clicked, typed, or interacted with
- Potential blockers - What might prevent testing
- Page complexity - How much exploration is needed
- Testability assessment - Can this page be effectively tested?
What Gets Diagnosed
1. Page Structure Analysis
The AI analyzes the page structure:
- Layout - Header, content, footer, navigation
- Content types - Forms, buttons, links, images, text
- Interactive elements - What users can click or type
- Page purpose - Landing page, form, dashboard, etc.
2. Testable Elements Identification
The AI identifies what can be tested:
- Forms - Signup, login, contact, checkout forms
- Buttons - Primary actions, navigation buttons
- Links - Internal navigation, external links
- Input fields - Text, email, password, select fields
- Interactive components - Dropdowns, modals, tabs
3. Blocker Detection
The AI checks for things that might block testing:
- CAPTCHA - Cannot proceed if CAPTCHA is required
- MFA prompts - Multi-factor authentication blocks automation
- Cookie banners - May need to be dismissed (see Cookie Banner Handling)
- Auth prompts - Login screens that block access
- Age gates - Age verification screens
- Paywalls - Subscription or payment required
4. Page Complexity Assessment
The AI estimates how complex the page is:
- Simple pages - Few interactive elements, quick exploration
- Medium pages - Multiple forms or sections, moderate exploration
- Complex pages - Many interactive elements, extensive exploration needed
- Single-page apps - Dynamic content, may need more exploration
What Can Be Tested
✅ Testable Pages
- Public pages - Landing pages, marketing pages, documentation
- Forms - Contact forms, signup forms, search forms
- Navigation - Menu systems, links, site structure
- Public content - Blogs, articles, product pages
- Staging environments - If publicly accessible
- Protected pages - If you authenticate manually first
✅ Testable Elements
- Forms and form validation
- Buttons and click handlers
- Navigation links
- Visual layouts
- Console errors
- Network errors
- Accessibility basics
What Can't Be Tested
❌ Blocked by Design
- CAPTCHA-protected pages - Cannot solve CAPTCHAs automatically
- MFA-protected flows - Requires human input
- Age verification - Requires human confirmation
- Payment required - Can't enter payment information
❌ Not Accessible
- Localhost - Must be publicly accessible URL
- VPN-only sites - Must be accessible from public internet
- IP-restricted sites - Must allow access from Rihario servers
- Behind firewall - Must be publicly accessible
❌ Beyond Scope
- Email verification - Cannot access email inboxes
- SMS verification - Cannot receive SMS codes
- Third-party OAuth - Complex OAuth flows may require manual steps
- File uploads - Limited file upload testing
Diagnosis Results
After diagnosis, the AI knows:
- Can proceed - Page is testable, exploration will start
- Has blockers - CAPTCHA or other blocker detected, may need manual help
- Limited testability - Page can be tested but with limitations
- Requires authentication - Page is protected, may need manual login
How Diagnosis Affects Exploration
If Page Is Testable
Exploration proceeds normally:
- AI explores all identified interactive elements
- Follows natural user flows
- Tests forms and validation
- Checks for issues
If Blockers Detected
AI adjusts strategy:
- Cookie banners - Attempts to dismiss automatically
- Auth prompts - May pause for manual authentication
- CAPTCHA - Marks exploration as BLOCKED, waits for manual intervention
- Age gates - May attempt to proceed or mark as BLOCKED
If Limited Testability
AI focuses on what's testable:
- Tests accessible elements
- Reports what couldn't be tested
- Marks limitations clearly
Example Diagnosis Scenarios
Scenario 1: Simple Landing Page
Diagnosis Result:
- ✅ Page structure: Simple landing page
- ✅ Interactive elements: 5 links, 1 CTA button, 1 contact form
- ✅ No blockers detected
- ✅ Complexity: Low - quick exploration
- ✅ Result: Ready to test
Scenario 2: E-commerce Site with Cookie Banner
Diagnosis Result:
- ✅ Page structure: Product catalog
- ✅ Interactive elements: Navigation, product links, search form, cart
- ⚠️ Blocker detected: Cookie banner present
- ✅ Complexity: Medium
- ✅ Result: Will attempt to dismiss banner, then proceed
Scenario 3: Protected Dashboard
Diagnosis Result:
- ✅ Page structure: Dashboard detected
- ❌ Blocker: Authentication required
- ⚠️ Limited testability: Cannot access protected content
- ✅ Result: Will pause for manual authentication
Why Diagnosis Matters
Prevents Wasted Time
Diagnosis identifies blockers early, so the AI doesn't waste time trying to test untestable pages.
Better Planning
Understanding page structure helps the AI plan exploration more effectively.
Clearer Expectations
You know upfront what can and can't be tested, setting proper expectations.