Galactic Glitch

Client Overview

Game Intro
Galactic Glitch by Crunchy Leaf Games is a twin-stick roguelike shooter featuring physics-based combat. Players use a gravity gun to grab, throw, and slingshot rocks, mines, and debris across arena battlegrounds, making physics a core gameplay mechanic.
Business Requirements
The client requested:
- Functional testing
- Regression testing
- Performance testing
At the initial stage, an additional requirement was continuous video recording of extended gameplay sessions to document the testing process.
Tested on
- PC (Steam)
- Steam Deck

Engagement

In the early phase, the project was supported by a team of 3–6 QA specialists with partial daily involvement.
After workflow analysis, the engagement model was optimized:
A focused team of 1–2 QA specialists
Full 8-hour involvement
1–2 days per build depending on scope
This adjustment improved efficiency and predictability.

Challenges

Lack of detailed test or game design documentation
Unstructured planning of test rounds
Heavy reliance on mass manual testing with long video recordings
Limited clarity regarding feature scope and priorities

Game Testing Solutions

The QA team applied a targeted and methodical approach to test all critical areas of Sengoku Dynasty:rnCore Testing Typesrnrn

Structured Testing Process
Transition from large-scale manual sessions to a documented and structured QA workflow.
QA Documentation Development
Creation of checklists, test cases, and test scenarios to ensure consistent feature coverage.
Feature-Focused Testing
Deeper analysis of mechanics and scope to prioritize high-risk areas.
Team Optimization
Reduction of team size with increased involvement of key QA specialists to improve accountability and focus.

Business Impact / Benefits Delivered

Predictable QA Workflow
Testing cycles became structured and planned in advance, increasing overall process stability.
Improved Test Coverage
Clear documentation and scope analysis led to more comprehensive validation.
Reduced Urgent Testing Sessions
Fewer last-minute and inefficient test rounds.
Increased Timeline Transparency
Clearer expectations and delivery timelines for both QA and development teams.