메뉴
Add or update a Robolectric JVM unit test for the FireCrasher library. Use when changing recovery logic, crash handling, back-stack counting, exit-info reporting, or the recovery-state codec, and a test should cover it.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Cut a new FireCrasher library release — bump the version, sync the README and ABI baseline, verify, and tag for JitPack. Use when asked to "release", "publish", "cut a version", or "bump to x.y.z".
Inspect FireCrasher's recovery level and show custom recovery UX (loading dialog, toast, snackbar) or force a specific recovery level. Use when tailoring what the user sees during recovery, or reacting differently to occasional vs. repeated crashes.
Report native crashes, ANRs, and low-memory kills that FireCrasher's in-process handler cannot catch, using ApplicationExitInfo on API 30+. Use when you need a complete crash picture, or "why don't I get reports for native crashes / ANRs".
Add the FireCrasher crash-recovery library to an Android app and install it in the Application class. Use when integrating FireCrasher, setting up crash recovery, or when "app crashes should recover instead of closing".
Forward FireCrasher-caught exceptions to a crash reporter (Crashlytics, Sentry, etc.) while still recovering the app. Use when wiring crash reporting, logging non-fatals, or "make sure we still get crash reports after recovery".
Run the full local build that mirrors CI for FireCrasher — unit tests, Android lint, and the ABI baseline comparison. Use before pushing or opening a PR, or whenever asked to "run the tests", "check the build", or "verify it compiles".
SOC 직업 분류 기준
| name | add-library-test |
| description | Add or update a Robolectric JVM unit test for the FireCrasher library. Use when changing recovery logic, crash handling, back-stack counting, exit-info reporting, or the recovery-state codec, and a test should cover it. |
The library's tests run on the JVM under Robolectric — no device or
emulator needed. They live in
firecrasher/src/test/java/com/osama/firecrasher/ and use JUnit 4. Every
behavior change to the library should come with a test.
| Concern | Test |
|---|---|
Recovery level selection (evaluate) | RecoveryLevelEvaluationTest (pure, no Robolectric) |
| Activity counting / back-stack depth | BackStackCountTest |
Crash delivered to the onCrash hook on the main thread | CrashHandlerTest |
| Install DSL: scope population, auto-recover default, forced-level recover | FireCrasherDslTest |
GO_BACK back dispatch (dispatcher vs. legacy onBackPressed) | GoBackDispatchTest |
ApplicationExitInfo querying (API 30+) | ExitInfoTest (@Config(sdk = [30, 36])) |
| Recovery-state encode/decode + 128-byte limit | RecoveryStateCodecTest |
Extend the matching suite when your change fits one; add a new
*Test.kt in the same package otherwise.
@RunWith(RobolectricTestRunner::class). Pure-logic tests (like
RecoveryLevelEvaluationTest) need no runner — prefer that when possible.Robolectric.buildActivity(...); drive lifecycle
through CrashHandler's lifecycleCallbacks rather than reaching into
internals.@Config(sdk = [30, 36]) (see ExitInfoTest) so both the guarded and
unguarded paths are exercised.FireCrasher is an object with process-wide state
(retryCount). Tests that call into it must clean up in @After via
FireCrasher.resetForTest() (see GoBackDispatchTest) so tests don't leak
into each other.`first crash restarts the activity`)../gradlew :firecrasher:test
Test reports land in firecrasher/build/reports/tests/. Before finishing, run
the run-checks skill so lint and the ABI baseline are covered too.