Overview
In automatic mode:- Steps execute automatically
- AI assists with element detection
- Progress is tracked in real-time
- Human intervention only when needed
Interface Layout
Execution Phases
Phase 1: Precondition Analysis
Before running steps:- Device Check: Verify device is connected
- App Check: Verify target app is installed
- State Analysis: Analyze current device state
- Preconditions: Display required preconditions
Phase 2: Step Execution
For each step:- Prepare: Read step configuration
- Analyze: If using locators, find element
- Execute: Perform the action
- Verify: Check for errors
- Capture: Take screenshot
Phase 3: Result Collection
After all steps:- Summary: Compile results
- Screenshots: Organize captured images
- Report: Generate execution report
AI Analysis Features
Element Detection
When using element locators:- AI analyzes the screen
- Locates the target element
- Falls back to coordinates if needed
Adaptive Execution
AI can:- Handle minor UI changes
- Detect unexpected dialogs
- Suggest corrections
Analysis Overlay
During analysis, an overlay shows:Controls
Pause Button (⏸️)
- Pause current execution
- Review current state
- Continue when ready
Stop Button (✕)
- Stop execution
- Record partial results
- Return to test round
During Failure
When a step fails:- Retry: Attempt the step again
- Skip: Skip this step, continue
- Abort: Stop the entire execution
Countdown Timer
Triggered Execution
When execution is triggered remotely:- 10-second countdown before start
- Option to cancel if needed
Viewing Results
During Execution
- Step-by-step progress
- Current step details
- Screenshots per step
After Completion
Detailed Results
Click View Details to see:- Individual step results
- Failure reasons
- Screenshots for each step
- Timing information
Best Practices
Test Design for Automation
- Use element locators: More reliable than coordinates
- Add wait steps: Allow UI to settle
- Include verification: Confirm expected states
- Handle edge cases: Configure error handling in steps
Execution Tips
- Stable device state: Start from known state
- Network connectivity: Ensure stable connection
- Screen on: Keep device screen active
- No interruptions: Close notification-heavy apps
Troubleshooting
”Element Not Found”
- Check element locator configuration
- Verify element is visible on screen
- Try different locator strategy
- Add fallback coordinates
Execution Hangs
- Check device connection
- Verify Qaptly service is running
- Check for device dialogs/popups
- Restart streaming
Inconsistent Results
- Add longer wait times
- Use more specific locators
- Check for timing-dependent steps
- Review device state before execution
Related: