Gravity’s Edge - Survival Mode QA Pass: Core Loop Stability & System Interaction (PC)

Tested: 3 May 2026 • Build: Demo (no version displayed in-game)

🧾 Test Overview

Platform: PC (Windows 11)
Build: Demo (no version displayed in-game)
Environment: PC, 1080p, Dhaose Xbox 360 Wired PC Controller
Network: Standard home broadband via Wi-Fi
Tools: OBS, Google Sheets, Steam
Focus Areas: Survival Mode core loop, gravity and movement, combat interaction, camera tracking, and recovery from edge-state conditions
Purpose: Conduct a short pre-launch QA test pass focused on identifying player-impacting stability, control, and system interaction issues.

Introduction

This is a focused QA test pass on Gravity’s Edge, tested on PC using the public demo build.

The goal was to assess Survival Mode readiness before launch by testing high-risk systems that could affect stability, control, recovery, or player progression.

This was not a playtest or design review. Testing focused on reproducible, player-impacting QA risks rather than general feedback on fun, balance, or difficulty.

Testing focused on:

Survival Mode core loop stability
Gravity transitions and movement consistency
Conflicting gravity fields and edge cases
Combat interaction under pressure
Camera tracking and visibility
Recovery from awkward movement states

Game	Platform	Scope
Gravity’s Edge	PC, Demo build	One-day pre-launch QA test pass focused on Survival Mode stability, movement reliability, combat interaction, camera tracking, and recovery from edge-state conditions.

🎯 Goal

Check whether Survival Mode remains stable and controllable under repeated, stress-based gameplay conditions.

🧭 Focus Areas

Core loop stability
Gravity and movement
Combat pressure
Camera tracking
Recovery from edge states

📄 Deliverables

QA workbook with README, charters, session notes, risk matrix, and one-line summary
Risk-based system coverage summary
Session-based evidence capture
Short write-up focused on launch stability and system reliability

📊 Metrics

Metric	Value
Total Sessions Logged	5
Total Bugs Logged	0
Critical	0
Major	0
Minor	0
Primary Risk Area	Survival Mode movement, control, and recovery stability
Testing Type	Risk-based exploratory QA using targeted charters
Result	No crashes, soft locks, control loss, or system breakage observed within tested scope

📷 Evidence

Supporting evidence was captured through session-based gameplay recording. No bug clips are included because no functional bugs were logged during this pass.

Type	File / Link
QA Workbook	Open Workbook
QA Workbook PDF Export	Open PDF

📌 Key Findings

Area	Finding	Evidence
Core Loop Stability	Core loop from start to survival, death, and restart remained stable across repeated runs with no reset or state carryover issues.	S01, S03, S05
Gravity & Movement	Gravity transitions and movement behaviour remained consistent and predictable across varied speeds, angles, and edge cases.	S01, S02
Combat Interaction	Combat inputs remained responsive during movement and under pressure, with no conflict between attack and traversal systems.	S03
Camera Tracking & Visibility	Camera tracking remained stable and maintained clear visibility of the player, enemies, and navigation space during fast movement and combat scenarios.	S04
Recovery & Edge States	Player consistently recovered from awkward movement states with no instances of soft lock, control loss, or persistent broken states.	S05

🐞 Bugs Logged

No functional bugs were logged during this QA pass. Tested systems remained stable under the covered scenarios, including repeated gravity transitions, combat pressure, edge-state recovery, and death/restart checks.

🧠 Risk Assessment & System Coverage

System Area	Risk Level	Why Risky	Result
Core Loop	High	Failure would block Survival Mode progression or break restart flow.	Stable under tested conditions.
Gravity & Movement	High	Core mechanic affecting navigation, control, and survival.	Consistent and predictable under tested conditions.
Combat & Input Interaction	High	Input conflict or delay would directly affect survivability under pressure.	No input loss or system conflict observed.
Camera Tracking & Visibility	Medium	Poor visibility can reduce awareness and make deaths feel unfair.	Camera remained stable and readable.
Recovery & Edge States	High	Failed recovery could cause stuck states, soft locks, or broken control.	No stuck states or recovery failures observed.

📈 Results

Completed 5 focused QA sessions on Survival Mode.
Logged 0 functional bugs.
Tested high-risk systems including gravity movement, combat interaction, camera tracking, and recovery from unstable movement states.
Observed no crashes, soft locks, input loss, camera tracking failures, or broken death/restart states within tested scope.
Found that Survival Mode’s core control and recovery systems remained stable under repeated stress-based testing.

🔍 Key Points for the Developer

Gravity transitions remained stable under stress. Movement between planets behaved consistently across direct, shallow, high-speed, and edge-based transitions.
Conflicting gravity areas resolved predictably. When positioned between nearby planets, the system consistently resolved toward the nearest planet or the player-facing orientation without jitter or control loss.
Combat did not interfere with movement control. Attacking while jumping, landing, and moving under pressure did not produce input loss or movement interruption.
Camera tracking supported readability. The side-on camera kept the player, enemies, and navigation space visible during fast movement and combat.
Recovery from awkward movement states was reliable. Forced bad landings, mid-transition inputs, and edge-state recovery attempts did not produce stuck states or soft locks.

🔚 QA Summary & Next Steps

This Survival Mode QA pass did not identify crashes, soft locks, input failures, or system breakage within the tested scope.

The strongest result was overall system stability. Gravity movement, combat inputs, camera tracking, and recovery behaviour remained consistent across repeated and stress-based scenarios.

Because no functional bugs were logged, the value of this pass is risk reduction rather than issue discovery. The tested systems are high-impact areas for launch readiness, and they held up under targeted testing.

Recommended next steps:

Repeat Survival Mode checks on the final release candidate build.
Run a longer upgrade-focused pass once Ability Anvils and progression systems can be tested more deeply.
Run additional coverage using keyboard and mouse if controller was the primary input method.
Check co-op separately if it is planned for launch and accessible in the tested build.
Confirm build/version visibility for easier QA traceability in future test passes.

📎 Disclaimer

This is a personal, non-commercial portfolio for educational and recruitment purposes. I’m not affiliated with or endorsed by any game studios or publishers. All trademarks, logos, and game assets are the property of their respective owners. Any screenshots or short clips are included solely to document testing outcomes. If anything here needs to be removed or credited differently, please contact me and I’ll update it promptly.