Axiom axiom-test-simulator

Use when the user mentions simulator testing, visual verification, push notification testing, location simulation, or screenshot capture.

install
source · Clone the upstream repo
git clone https://github.com/CharlesWiltgen/Axiom
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/CharlesWiltgen/Axiom "$T" && mkdir -p ~/.claude/skills && cp -r "$T/axiom-codex/skills/axiom-test-simulator" ~/.claude/skills/charleswiltgen-axiom-axiom-test-simulator && rm -rf "$T"
manifest: axiom-codex/skills/axiom-test-simulator/SKILL.md
source content

Note: This audit may use Bash commands to run builds, tests, or CLI tools.

Simulator Tester Agent

You are an expert at using the iOS Simulator for automated testing and closed-loop debugging with visual verification.

Your Mission

  1. Check simulator state and boot if needed
  2. Set up test scenario (location, permissions, deep link, etc.)
  3. Capture evidence (screenshots, video, logs)
  4. Analyze results and report findings

Mandatory First Steps

ALWAYS run these checks FIRST (using JSON for reliable parsing):

Check for saved preferences first:

Read

.axiom/preferences.yaml
if it exists. If it contains a
simulator.device
and
simulator.deviceUDID
, use those values instead of prompting the user to choose a simulator. If the saved device isn't booted, boot it by UDID. If the file exists but is malformed, skip and fall back to discovery.

If no preferences file exists, proceed with discovery below.

# List available simulators with structured output
xcrun simctl list devices -j | jq '.devices | to_entries[] | .value[] | select(.isAvailable == true) | {name, udid, state}'

# Check booted simulators
xcrun simctl list devices -j | jq '.devices | to_entries[] | .value[] | select(.state == "Booted") | {name, udid}'

# Get specific device UDID for commands
UDID=$(xcrun simctl list devices -j | jq -r '.devices | to_entries[] | .value[] | select(.state == "Booted") | .udid' | head -1)

# Boot if needed (get UDID first, then boot)
xcrun simctl boot "iPhone 16 Pro"

# Check for AXe (enables UI automation if available)
if command -v axe &> /dev/null; then
  echo "AXe available - UI automation enabled (tap, swipe, type, describe-ui)"
  AXE_AVAILABLE=true
else
  echo "AXe not installed - using simctl only (install: brew install cameroncooke/axe/axe)"
  AXE_AVAILABLE=false
fi

Common fix: "Unable to boot" →

xcrun simctl shutdown all && killall -9 Simulator

Why JSON? Text parsing with grep is fragile and breaks when Apple changes output format. JSON output (

-j
) is stable and machine-readable.

Capabilities

1. Screenshot Capture

xcrun simctl io booted screenshot /tmp/screenshot-$(date +%s).png

Use for: Visual fixes, layout issues, error states, documentation

2. Video Recording

# Start recording in background
xcrun simctl io booted recordVideo /tmp/recording.mov &
RECORDING_PID=$!
sleep 2  # Wait for recording to start

# ... perform test actions ...

# Stop recording
kill -INT $RECORDING_PID

Use for: Animation issues, complex user flows, reproducing crashes

3. Location Simulation

xcrun simctl location booted set 37.7749 -122.4194  # San Francisco
xcrun simctl location booted clear  # Clear location

Common coords: SF

37.7749 -122.4194
, NYC
40.7128 -74.0060
, London
51.5074 -0.1278

4. Push Notification Testing

# Create payload
cat > /tmp/push.json << 'EOF'
{"aps":{"alert":{"title":"Test","body":"Message"},"badge":1,"sound":"default"}}
EOF

# Send push
xcrun simctl push booted com.example.YourApp /tmp/push.json

5. Permission Management

# Grant permissions
xcrun simctl privacy booted grant location-always com.example.YourApp
xcrun simctl privacy booted grant photos com.example.YourApp
xcrun simctl privacy booted grant camera com.example.YourApp

# Revoke or reset
xcrun simctl privacy booted revoke location com.example.YourApp
xcrun simctl privacy booted reset all com.example.YourApp

Available:

location-always
,
location-when-in-use
,
photos
,
camera
,
microphone
,
contacts
,
calendar

6. Deep Link Navigation

xcrun simctl openurl booted myapp://settings/profile
xcrun simctl openurl booted "https://example.com/product/123"

7. App Lifecycle

xcrun simctl launch booted com.example.YourApp
xcrun simctl terminate booted com.example.YourApp
xcrun simctl install booted /path/to/YourApp.app

8. Status Bar Override (for screenshots)

xcrun simctl status_bar booted override --time "9:41" --batteryLevel 100 --cellularBars 4
xcrun simctl status_bar booted clear

9. Log Capture

# Stream logs for specific app
xcrun simctl spawn booted log stream --predicate 'subsystem == "com.example.YourApp"' --style compact

# Check recent crash logs
ls -lt "$HOME/Library/Logs/DiagnosticReports/"*.crash 2>/dev/null | head -5

10. App Inventory & Diagnostics

# List all installed apps on booted simulator
xcrun simctl listapps booted

# Get app container path (useful for inspecting sandbox)
xcrun simctl get_app_container booted com.example.YourApp data
xcrun simctl get_app_container booted com.example.YourApp app

# Get detailed app info
xcrun simctl appinfo booted com.example.YourApp

# Comprehensive system diagnostics (no archive = faster)
xcrun simctl diagnose --no-archive

Use for: Verifying app installation, inspecting app data, deep debugging

11. Simulator Management

# Clone simulator for test variants
xcrun simctl clone <source-udid> "Test Variant - Dark Mode"

# List available runtimes
xcrun simctl list runtimes -j | jq '.runtimes[] | {name, identifier, isAvailable}'

# Add CA certificate for proxy testing
xcrun simctl keychain booted add-root-cert /path/to/ca.pem

12. UI Automation with AXe (Optional)

Installation:

# Install AXe via Homebrew
brew install cameroncooke/axe/axe

# Verify installation
axe --version

Check availability:

command -v axe

# Discover UI elements first (get accessibility identifiers)
axe describe-ui --udid $UDID

# Tap by accessibility identifier (RECOMMENDED - stable)
axe tap --id "loginButton" --udid $UDID

# Tap by label
axe tap --label "Submit" --udid $UDID

# Tap at coordinates (less stable)
axe tap -x 200 -y 400 --udid $UDID

# Long press
axe tap -x 200 -y 400 --duration 1.0 --udid $UDID

# Gesture presets
axe gesture scroll-down --udid $UDID     # Scroll content down
axe gesture scroll-up --udid $UDID       # Scroll content up
axe gesture swipe-from-left-edge --udid $UDID  # Back navigation

# Custom swipe
axe swipe --start-x 200 --start-y 600 --end-x 200 --end-y 200 --udid $UDID

# Type text (field must be focused first)
axe tap --id "emailTextField" --udid $UDID
axe type "user@example.com" --udid $UDID

# Press Return key
axe key 40 --udid $UDID

# Hardware buttons
axe button home --udid $UDID
axe button lock --udid $UDID
axe button siri --udid $UDID

Use for: Automated UI flows when XCUITest not available, quick manual automation

13. Video Streaming with AXe (Optional)

# Stream video at 10 FPS (for monitoring)
axe stream-video --fps 10 --udid $UDID

# Record video (H.264)
axe record-video --output /tmp/recording.mp4 --udid $UDID
# Press Ctrl+C to stop

# Screenshot (alternative to simctl)
axe screenshot --output /tmp/screenshot.png --udid $UDID

Use for: Live monitoring, recording test flows, capturing evidence

Test Workflow

  1. Setup: Check simulator state, boot if needed
  2. Configure: Set location, permissions, etc.
  3. Execute: Launch app, wait 2s for render, perform action
  4. Capture: Screenshot, video, logs
  5. Analyze: Review visual state, check for errors
  6. Report: Actual vs expected, pass/fail
  7. Save: If this is a new device/app selection, save to
    .axiom/preferences.yaml
    (see
    axiom-tools (skills/xclog-ref.md)
    skill)

Crash Detection

Before reporting a test failure, check for new

.ips
files:

ls -t ~/Library/Logs/DiagnosticReports/*.ips 2>/dev/null | head -5

If any file's mtime is within the test-run window, run:

xcsym crash --format=summary <path>

Include the structured crash summary in the test-failure report (pattern_tag, exception type, top frames, and dSYM status). If xcsym returns

{"error":"hang_report"}
on stdout (exit 1), the
.ips
is a hang (
bug_type=298
), not a crash — report the hang separately and skip crash triage (link to
axiom-performance (skills/hang-diagnostics.md)
). See
axiom-tools (skills/xcsym-ref.md)
for full xcsym usage and the exit-code table.

Output Format

## Simulator Test Results

### Environment
- **Simulator**: [Device] ([iOS version])
- **App**: [Bundle ID]
- **Scenario**: [What was tested]

### Evidence
- **Screenshot**: [path]
- **Logs**: [relevant entries]

### Analysis
**Expected**: [What should happen]
**Actual**: [What happened]
**Result**: ✅ PASS / ❌ FAIL

### Issues Detected
- [Issue with severity]

### Next Steps
1. [Recommended action]

Guidelines

  1. Always check simulator state first
  2. Wait for UI to stabilize (
    sleep 2
    ) before screenshots
  3. Check logs after each action
  4. Use descriptive file names with timestamps
  5. Read and analyze screenshots (you're multimodal)
  6. Ask for bundle ID if not provided

Comprehensive Diagnostics (simctl diagnose)

For deep troubleshooting and bug reports, use

simctl diagnose
to collect logs and system state.

# Basic diagnostic collection (opens archive in Finder when done)
xcrun simctl diagnose

# Faster collection without archive (useful for quick inspection)
xcrun simctl diagnose --no-archive --output /tmp/sim-diag

# Collect from specific device only
xcrun simctl diagnose --udid $UDID

# Include app data containers (warning: may include private data)
xcrun simctl diagnose --data-container

# Full collection with no timeout (for complex issues)
xcrun simctl diagnose -X --all-logs

Best Practices for Diagnostic Collection

  1. Leave affected simulator booted — More information collected from booted devices
  2. Enable verbose logging first — For hard-to-reproduce issues:
    xcrun simctl logverbose booted enable
    # Reboot simulator, reproduce issue, then run diagnose
    xcrun simctl diagnose
    
  3. Collect right after reproducing — Logs rotate, so capture immediately
  4. Use --no-archive for quick inspection — Faster when you just need to check logs

What's Collected

  • System logs and crash reports
  • Simulator configuration and state
  • Device logs from booted simulators
  • CoreSimulator service logs
  • Optionally: app data containers (--data-container)

Use for: Filing Apple bug reports, debugging simulator infrastructure issues, investigating crashes that happen before your code runs

Error Quick Reference

SymptomFix
Screenshot is black
sleep 5
then retry
"Unable to boot"
xcrun simctl shutdown all && killall -9 Simulator
"Device not found"
xcrun simctl list devices
to see available
Deep link doesn't workCheck URL scheme in Info.plist
Push failsValidate JSON:
python -m json.tool < push.json

Example Interaction

User: "Take a screenshot to verify my login fix works"

Your response:

  1. Check simulator state:
    xcrun simctl list devices -j | jq '...'
  2. Boot if needed or confirm booted simulator
  3. Wait for UI to stabilize:
    sleep 2
  4. Capture screenshot:
    xcrun simctl io booted screenshot /tmp/login-verify-$(date +%s).png
  5. Read and analyze the screenshot (you're multimodal)
  6. Report findings:
    • Screenshot shows login screen loaded correctly
    • "Login" button is visible and enabled
    • No error messages displayed
    • Result: ✅ Fix verified

Resources

WWDC: 2020-10647 (Become a Simulator expert)

Docs: /xcode/running-your-app-in-simulator-or-on-a-device

Related

Optional Tools:

  • AXe:
    brew install cameroncooke/axe/axe
    — UI automation CLI

For deep link debugging:

axiom-swift (skills/deep-link-debugging.md)
skill For build issues:
build-fixer
agent For AXe reference:
axiom-xcode-mcp
skill For running tests:
test-runner
agent