axiom debug tests

Engineering Community

Skill notes

Core Principle

Closed-loop debugging flow:

Did the Test Crash?

Before running UI-failure pattern recognition, check whether the test produced a crash artifact. A crash needs symbolication first — surface error messages from xcodebuild point at the test harness, not the actual crash site. Feed the returned pattern_tag to the fix plan: pattern_tag · Action swift_forced_unwrap · Inspect the force-unwrap site — usually a test helper or mock returning nil swift_concurrency_violation · @MainActor state touched off the main actor (route to axiom-concurrency)

Failure Pattern Recognition

Pattern · Error Message · Root Cause · Fix Element Not Found (test bug) · Failed to find element · Wrong query or missing accessibilityIdentifier · Fix query or add identifier Element Not Found (app bug) · Failed to find element · Element never implemented or in wrong view · Report: app code needs this element — do NOT rewrite test Timeout · Timed out waiting for element · Slow app, short timeout · Increase timeout, optimize app

Element Not Found Triage

When a test can't find a UI element, determine whether the problem is in the test or the app BEFORE suggesting fixes: Check the screenshot — Is the expected element visible anywhere on screen? If element is NOT visible: Search the app source code for the element (grep for the expected text, identifier, or view name) Element not in source → App bug: element was never implemented. Report this — do NOT rewrite test queries. Do not search for partial matches or alternative element names. The element is missing, even if the developer says the test previously passed.

Phase 4: Suggest Fixes

Based on pattern analysis, suggest specific code changes:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@CharlesWiltgen · MIT
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Run Tests

Phase 1: Run Tests

02
Phase 2: Capture Evidence

Phase 2: Capture Evidence

03
Phase 3: Analyze Failures

Phase 3: Analyze Failures

04
Phase 4: Suggest Fixes

Based on pattern analysis, suggest specific code changes:

05
Phase 5: Apply Fixes

Show proposed change to user Get confirmation before editing Apply edit using Edit tool Log the change for verification loginButton.tap()

06
Phase 6: Verify Fix

Phase 6: Verify Fix

07
Phase 7: Report

Phase 7: Report

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.