Grove Bound - Ongoing QA Case Study
🧾 Project Overview
- Game: Grove Bound
- Studio: GDO Games
- Role: Embedded QA Tester
- Testing dates: Ongoing from 8 June 2026
- Status: In development, with ongoing QA support across builds and updates
- Platform: PC / Browser / itch.io
- Current focus: Onboarding, progression clarity, feature validation, regression testing, and Steam demo readiness
🎯 My QA Role
I provide embedded QA support for Grove Bound during active development, with an initial focus on onboarding, player guidance, object interaction clarity, progression flow, and the overall first-session experience.
The developer wanted feedback on whether new players could understand what the game was asking them to do, whether the early systems felt clear enough without explanation, and whether the opening experience gave players enough reason to continue. My first QA passes were shaped around those needs rather than broad, unfocused play.
My responsibilities included exploratory QA, player-facing risk identification, structured reporting, regression testing, feature validation, and practical recommendations to support future Steam demo readiness.
Developer Feedback
“Kelina is a pleasure to work with. She is hardworking and provides genuine insight into Grove Bound, approaching it from the perspective of a first time player. Her feedback on player onboarding was essential and greatly improved the overall flow through her suggestions.
She is very good at understanding my needs as a developer and turning them into effective test plans. She requires very little supervision and is more than capable of working independently. Her work was always delivered promptly and included excellent breakdowns and documentation.
I would highly recommend working with her. The only area I would suggest improving is bug severity and priority classification, which could have been more consistent. However, this is something that could easily be addressed through regular weekly meetings to review and classify issues together or a a list of classifications from my self to make putting them in category's easier."
🧠 Triage & Planning
- Reviewed onboarding concerns
- Prioritised first-session risks
- Flagged progression blockers
- Separated bugs from clarity issues
- Planned focused regression checks
🎮 Testing Focus
- Tutorial and onboarding flow
- Early progression guidance
- Quest and NPC direction
- Crafting and cooking clarity
- Buildable system validation
🔁 Ongoing Support
- Regression testing after fixes
- Reproduction checks
- New feature validation
- Storage and buildable testing
- Steam demo readiness support
🛠️ Workflow & Communication
Testing was carried out through ongoing collaboration with the developer using Discord. Each pass focused on current development priorities, player-facing risks, and recently implemented changes.
Findings were delivered through structured QA reports supported by screenshots, video evidence, bug logs, friction logs, and practical recommendations. Follow-up sessions were then used to validate fixes and assess whether previous concerns had improved.
| Workflow Area | How It Worked |
|---|---|
| Communication | Direct Discord communication with the developer. |
| Planning | Testing aligned with current build priorities and known risks. |
| Testing | Exploratory testing, feature validation, and regression testing. |
| Reporting | Structured reports covering findings, impact, and recommendations. |
| Evidence | Screenshots and gameplay recordings used where appropriate. |
| Follow-up | Fix validation and regression testing across later builds. |
🧭 Onboarding, Progression & Feature Validation
A significant portion of testing focused on whether Grove Bound successfully communicated its mechanics, objectives, and progression systems to a new player without external guidance.
Testing covered tutorial flow, post-tutorial progression, NPC guidance, crafting discovery, cooking systems, buildable structures, resource management, and feature usability.
The objective was not simply to verify functionality, but to assess whether players understood why systems existed, how they connected to progression, and what actions they should take next.
| Test Area | Observed Focus |
|---|---|
| Tutorial Flow | Clarity of onboarding and information pacing. |
| Early Progression | Player motivation and direction after onboarding. |
| Quest Guidance | Objective communication and discoverability. |
| NPC Interaction | Dialogue clarity and progression support. |
| Crafting | Recipe understanding and progression value. |
| Cooking | System usability and player feedback. |
| Buildable Systems | Campfires, storage, and feature discoverability. |
| Regression Testing | Validation of fixes and previously reported concerns. |
⚠️ Current Player-Facing Risk Areas
| Risk Area | Player Impact |
|---|---|
| Progression Clarity | Players may become unsure what to do next after completing objectives. |
| System Discoverability | Some systems can be overlooked or misunderstood without sufficient guidance. |
| Feature Communication | Mechanics may function correctly while their purpose remains unclear. |
| Crafting & Building Guidance | Players may struggle to understand unlock paths and progression requirements. |
| Feedback Visibility | Important information can occasionally be easy to miss during normal play. |
| Retention Risk | Confusion during early gameplay can reduce motivation to continue playing. |
🤝 Working With the Developer
Testing priorities were agreed collaboratively based on the developer's current concerns, active feature work, and player-facing risks identified during earlier passes.
Feedback was reported in a practical way, separating progression blockers, usability concerns, clarity issues, and lower-priority observations to help support development decisions.
The project remains an ongoing collaboration, with future testing expected to focus on new features, regression coverage, and Steam demo readiness as development continues.
🧰 Tools & Evidence Workflow
| Tool / Method | Used For |
|---|---|
| PC / Browser Testing | Testing active itch.io builds. |
| Google Docs | QA summaries and reporting. |
| Google Sheets | Bug logs and friction logs. |
| Discord | Communication and feedback discussion. |
| Screenshot Evidence | Visual issue documentation. |
| Video Evidence | Capturing gameplay behaviour and repro evidence. |
| itch.io | Build access and testing. |
✅ What This Case Study Shows
- Ongoing QA support for an actively developed indie project.
- Player-focused exploratory testing from a first-time user perspective.
- Identification of onboarding, progression, and usability risks.
- Structured reporting with clear player-impact analysis.
- Regression testing and feature validation across multiple updates.
- Practical collaboration with a solo indie developer.
- Support for long-term demo readiness and player experience improvements.
Need QA Support for Your Game?
If you have a demo, PC build, browser build, update, or release candidate that needs structured QA support, message me with the platform, build, and what you need checked.
📎 Disclaimer
This page documents QA work completed so far by Kelina Cowell for portfolio and recruitment purposes. Grove Bound is still in active development, and this page will be updated as further QA passes are completed. I am not the developer or publisher of Grove Bound. All trademarks, logos, screenshots, clips, graphs, and game assets remain the property of their respective owners. Internal QA details, full bug logs, and private developer communications are not published here. If anything needs to be removed or credited differently, please contact me and I’ll update it promptly.