Conducted comprehensive exploratory testing on the Android build (Pocophone F1) of "Graveyard Bash." The session focused on physics collision edge cases, monetization loopholes, and state logic consistency.
The Scope
Device: Pocophone F1 (Android 10)
Focus: Stress-testing the "Jack-in-the-box" and "Angel Statue" physics interactions, and validating the ad-reward loop.
Logic Defect: Win-State Desync
The Bug: The UI indicates a "Win State" (Red Text) even when the score drops below the required threshold due to a Reliquary destruction penalty (-20%).
Impact: Confusing player feedback loop where the game state (Loss) contradicts the UI state (Win).
Calculation Error: Integer Overflow/Underflow
The Bug: The "Target Score" calculation broke during a high-load physics sequence, displaying a negative integer (-128) instead of the correct value.
Context: Occurred during a simultaneous object respawn sequence involving the Angel Statue.
Critical Monetization Exploit: Ad Reward Bypass
Method: Disabling internet connectivity immediately after the ad caches (but before playback completes).
Result: The system grants the reward (Resurrection) without successfully validating the ad view.
Severity: High (Direct Revenue Loss).
Physics & UX Heuristics
Collision Soft-Lock: Identified a rare physics edge case where the ball becomes permanently stuck in the scoreboard UI after a "Corpse Flower" spring interaction.
Input Sensitivity: Flagged the shooting mechanic as overly sensitive in the bottom screen region. Proposed a "Pull-Back" mechanic (similar to billiards genre standards) to reduce accidental inputs.