Idrinth / habit-evaluator / 22113270621

40%

push

github

Add crash diagnostics to Maestro tests and fix instrumentation excludes (#468)

The Maestro UI tests have been crashing on every run since JaCoCo offline
instrumentation was added, but there was no visibility into the actual
crash reason — the script only checked for the app process during coverage
collection, after the test had already failed.

Changes:
- Add pre-flight crash check: launch app before Maestro runs and capture
  the full crash stacktrace (FATAL EXCEPTION, class loading errors,
  process death) if it dies within 5 seconds
- Add post-test crash diagnostics: capture logcat after Maestro fails
  and print categorized error summaries inline in CI
- Upload full logcat as CI artifact on failure for offline analysis
- Exclude module-info.class and package-info.class from JaCoCo offline
  instrumentation (these are special descriptor files that should not
  be instrumented)

https://claude.ai/code/session_01S487Q8cwbCmmDztDMSiFtc

Co-authored-by: Claude <noreply@anthropic.com>

2782 of 6340 branches covered (43.88%)

Branch coverage included in aggregate %.

9426 of 18190 relevant lines covered (51.82%)

2.49 hits per line