What FAILED vs BLOCKED vs SKIPPED Means

Rihario uses three statuses: FAILED means something broke, BLOCKED means hit an intentional blocker, and SKIPPED means intentionally skipped for safety or efficiency. Understanding these statuses helps you interpret results correctly and know when issues are actual bugs vs expected limitations.

FAILED Status

What It Means

FAILED means something broke during exploration:

• Action failed - Click didn't work, form didn't submit, etc.
• Error occurred - JavaScript error, network error, etc.
• Unexpected behavior - Something didn't work as expected
• Technical problem - Usually indicates a bug in your app

Common FAILED Scenarios

• JavaScript error - Console error breaks functionality
• Network failure - API request fails, page doesn't load
• Element not found - Button or form field missing (but AI expected it)
• Form submission fails - Form doesn't submit, error shown
• Page crash - Page becomes unresponsive

Example: FAILED

BLOCKED Status

What It Means

BLOCKED means exploration hit an intentional blocker:

• Security measure - CAPTCHA, MFA, or other protection
• Access control - Authentication required, paywall, age gate
• Cannot automate - Requires human intervention
• Not a bug - This is expected behavior, not a problem

Common BLOCKED Scenarios

• CAPTCHA - Cannot solve CAPTCHAs automatically
• MFA prompt - Multi-factor authentication requires human input
• Cookie banner - Cannot dismiss complex cookie banners
• Login required - Protected page needs authentication
• Paywall - Content requires payment

Example: BLOCKED

SKIPPED Status

What It Means

SKIPPED means the step was intentionally skipped:

• Safety guard - Prevented infinite loop or stuck state
• Efficiency optimization - Skipped duplicate or low-value actions
• Not a problem - Skipping was the right decision
• Optimization - Saves time without affecting results

Common SKIPPED Scenarios

• Infinite loop prevention - Same action repeating, skipped to stop loop
• Duplicate action - Already performed similar action
• Low-value exploration - Element doesn't add value
• Already explored - Page or flow already checked
• Timeout prevention - Action taking too long, skipped to prevent hanging

Example: SKIPPED

Comparison Table

How to Interpret Results

If You See FAILED

1. Review the error - Check console logs, network errors
2. Verify it's real - Manually reproduce the issue
3. Fix the bug - This indicates a real problem in your app
4. Re-test - Run exploration again to verify fix

If You See BLOCKED

1. Check the reason - See what blocked exploration (CAPTCHA, MFA, etc.)
2. Decide if action needed - If blocker is intentional, that's fine
3. Take control if needed - Manually handle blocker, then resume
4. Use test environment - Disable blockers in staging/test environments

If You See SKIPPED

1. Review the reason - Understand why it was skipped
2. Verify it's fine - Usually skipping is correct
3. No action needed - Skipping is typically intentional and correct

Status Combinations

All Steps Successful

✓ All steps show SUCCESS - Exploration completed without issues. This is the ideal outcome.

Some Steps FAILED

Some steps FAILED, others successful - Your app has bugs, but exploration continued. Review failed steps to fix issues.

Exploration BLOCKED

Hit a blocker and stopped - Intentional security measure prevented automation. Take control manually or use test environment.

Mix of Statuses

Combination of SUCCESS, FAILED, BLOCKED, SKIPPED - Normal. Review each status appropriately:

• Fix FAILED steps (bugs)
• Handle BLOCKED steps (manual intervention or test environment)
• Ignore SKIPPED steps (intentional optimization)

Real-World Examples

Example 1: Successful Exploration

Example 2: Mixed Results

Example 3: Blocked Exploration

Next Steps

• Learn how to read test logs
• Understand different error types
• See CAPTCHA and MFA limitations