Grove Bound - Ongoing QA Case Study
๐งพ Project Overview
- Game: Grove Bound
- Studio: GDO Games
- Credited Role: QA Lead
- 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 am credited as QA Lead on Grove Bound, providing ongoing QA throughout active development and adapting testing priorities alongside the project's development needs.
My initial work focused on onboarding, player guidance, object interaction clarity, progression flow, and the overall first-session experience. More recently, my testing has expanded into targeted quest and progression validation ahead of further content development.
My responsibilities include exploratory QA, player-facing risk identification, test planning, structured reporting, regression testing, quest and feature validation, dialogue quality checks, and practical recommendations to support continued development and 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."
๐ง Triage & Planning
- Aligned testing with current development priorities
- Prioritised player-facing and progression risks
- Defined focused test scope for each pass
- Separated functional issues from clarity and usability concerns
- Planned targeted regression and follow-up testing
- Documented blocked and untested areas
๐ฎ Testing Focus
- Tutorial, onboarding and player guidance
- Early-game progression and feature discoverability
- Quest progression and objective clarity
- Inventory and quest-item interactions
- Resource gathering and crafting
- Cooking and buildable systems
- Farming setup, planting and crop lifecycle
- Watering, crop growth and harvesting behaviour
- Crop processing and food-production workflows
- NPC interaction and dialogue quality
- Player feedback and UX clarity
๐ Ongoing Support
- Regression testing after fixes
- Fix and reproduction validation
- New feature and system validation
- Targeted testing using developer-provided QA saves
- Quest and progression validation
- Continued Steam demo readiness support
๐ ๏ธ Workflow & Communication
Testing is carried out through ongoing collaboration with the developer using Discord. Testing priorities are aligned with current development needs, previously identified risks, newly implemented changes, and areas requiring focused validation.
My approach varies depending on the objective of each pass, ranging from first-time-player exploratory testing to targeted regression, feature validation, and quest testing. Developer-provided QA saves are used where appropriate to reach specific progression states efficiently and avoid unnecessary replay.
Findings are delivered through structured QA reports supported by screenshots, video evidence, bug logs, friction logs, and practical recommendations. Follow-up passes are used to validate fixes, check for regressions, and assess whether previously reported concerns have improved.
| Workflow Area | How It Works |
|---|---|
| Communication | Direct Discord communication with the developer. |
| Planning | Testing aligned with current development priorities, known risks, and requested validation areas. |
| Testing | Exploratory testing, targeted regression, feature validation, and quest testing. |
| Test States | Developer-provided QA saves used to reach specific progression points for focused testing. |
| Reporting | Structured reports documenting scope, findings, player impact, and recommendations. |
| Evidence | Screenshots and gameplay recordings used to support findings where appropriate. |
| Follow-up | Fix validation and regression testing across subsequent builds. |
๐งญ Onboarding, Progression & Feature Validation
Testing has evolved alongside Grove Bound's development, beginning with broad first-time-player and onboarding evaluation before expanding into regression testing, feature validation, targeted quest testing, and system-level investigation.
Coverage has included onboarding, progression, quest flow, inventory interactions, resource gathering, crafting, cooking, buildable systems, farming, dialogue, save integrity, puzzles, and player-facing usability. Farming coverage included equipment crafting, farm patch placement, planting, watering, crop growth and harvesting, repeat-harvest crops, and crop-to-food production workflows.
Testing priorities have changed between builds based on development needs and previously identified risks, with findings separated between functional defects and player-experience or communication issues where appropriate.
The timeline below shows how my QA coverage has expanded and shifted alongside the project's development.
| Testing Area | Jun 2026 | Jul 2026 | Aug 2026 | Sep 2026 | Oct 2026 |
|---|---|---|---|---|---|
| Tutorial & Onboarding | โ | โ | โ | โ | โ |
| First-Session Experience | โ | โ | โ | โ | โ |
| Progression & Player Guidance | โ | โ | โ | โ | โ |
| Quest Validation | โ | โ | โ | โ | โ |
| Inventory & Item Interactions | โ | โ | โ | โ | โ |
| Crafting & Resource Systems | โ | โ | โ | โ | โ |
| Cooking Systems | โ | โ | โ | โ | โ |
| Buildable & Storage Systems | โ | โ | โ | โ | โ |
| Farming & Crop Lifecycle | โ | โ | โ | โ | โ |
| Growth & Harvest Behaviour | โ | โ | โ | โ | โ |
| Puzzle / Logic Progression | โ | โ | โ | โ | โ |
| Dialogue System & Content Quality | โ | โ | โ | โ | โ |
| Save / Load Integrity | โ | โ | โ | โ | โ |
| Regression & Fix Validation | โ | โ | โ | โ | โ |
| Player Experience & UX Feedback | โ | โ | โ | โ | โ |
โ Tested during this period โ Not tested or not a focus during this period
๐บ๏ธ Quest & Progression Testing
As development progressed, my testing expanded into focused validation of existing quest content ahead of further planned content development.
I carried out exploratory quest playthroughs from a first-time-player perspective, testing progression flow, objective clarity, inventory interactions, puzzles, resource gathering, crafting, cooking, and NPC dialogue.
A key part of this testing was evaluating not only whether quest systems functioned correctly, but whether the intended progression could be understood using the information available to the player.
Where progression became unclear, I avoided requesting the intended solution from the developer. Instead, I tested logical player actions, documented the resulting behaviour, and reported where the progression path could not be determined naturally. This preserved the value of the first-time-player perspective and helped identify discoverability and guidance issues.
Individual systems and progression steps were isolated where appropriate to distinguish functional defects from unclear instructions, missing feedback, or player-facing communication issues. This allowed findings to be reported according to the underlying problem rather than treating every unexpected result as a bug.
Dialogue was also reviewed during these passes for grammar, spelling, punctuation, capitalisation, formatting, and clarity.
๐ฑ Farming System & Crop Lifecycle Testing
As the farming system was introduced, I carried out a dedicated charter-based QA pass covering the player workflow from crafting farming equipment through to planting, crop growth, harvesting, and food production.
Testing covered equipment crafting, farm patch placement, seed interactions, watering, crop growth, harvesting behaviour, crop persistence, and crop-to-food production workflows.
I planted and grew all available crop types and used controlled comparison testing to investigate the effect of watering on crop growth. Two crops were planted at the same time under different conditions, allowing growth behaviour and player-facing visual feedback to be compared directly.
Harvest testing covered multiple crop behaviours, including single-harvest and persistent crops. I also tested the interactions available to the player after harvesting to verify that crop and plot states behaved consistently throughout the farming lifecycle.
The pass identified issues affecting feature interaction, crop-state communication, visual consistency, and harvesting behaviour. Where results were ambiguous, I investigated further rather than immediately classifying unexpected behaviour as a defect.
One finding initially appeared to be a functional issue. After reproducing the behaviour and discussing the intended design with the developer, I established that the underlying functionality was working as designed but was not sufficiently communicated to the player. I reclassified the finding as player-experience feedback rather than retaining it as a bug.
This pass combined functional validation, exploratory testing, controlled comparison testing, and player-experience analysis. Findings were separated between confirmed defects, intended behaviour, and areas where clearer guidance or feedback could improve player understanding.
โ ๏ธ Current Player-Facing Risk Areas
| Risk Area | Player Impact |
|---|---|
| Progression Clarity | Players may become unsure how to progress when the intended next action is not sufficiently communicated. |
| System Discoverability | New systems, including farming interactions, may be difficult to discover or understand without sufficient in-game guidance. |
| Feature Communication | Mechanics may function as intended while their purpose or behaviour remains unclear. This can cause intended functionality to appear broken or incomplete to the player. |
| Quest & System Guidance | Players may understand the overall objective but struggle to identify the required item, interaction, location, or system needed to progress. |
| Interaction Feedback | Missing or unclear prompts, state information, and interaction feedback can make it difficult for players to understand whether an action has succeeded or what options are available. |
| Reward Communication | Rewards such as Gold or XP may be missed when the game does not provide clear feedback, leaving players uncertain about the outcome of an interaction. |
| Retention Risk | Repeated uncertainty around progression, interactions, or system behaviour can interrupt gameplay flow and reduce motivation to continue. |
๐ค Working With the Developer
Testing priorities are agreed collaboratively based on current development needs, active feature work, upcoming testing requirements, and player-facing risks identified during previous QA passes.
As development has progressed, testing has moved from broad first-time-player and onboarding evaluation into more targeted regression, feature, progression, and quest validation. Developer-provided QA saves are used where appropriate to reach specific test states efficiently.
Feedback is reported in a practical way, separating functional defects, progression blockers, usability and discoverability concerns, content-quality issues, and lower-priority observations to support development decisions.
The project remains an ongoing collaboration, with QA priorities continuing to evolve alongside development and future Steam demo readiness.
๐งฐ Tools & Evidence Workflow
| Tool / Method | Used For |
|---|---|
| PC Testing | Testing development builds and targeted gameplay scenarios. |
| Browser Testing | Testing browser-based builds and player-facing functionality. |
| Developer-Provided Save States | Accessing specific progression points for focused quest and feature testing. |
| Google Docs | QA summaries and structured test reporting. |
| Google Sheets | Bug logs and friction tracking. |
| Discord | Developer communication, testing priorities, and feedback discussion. |
| Screenshot Evidence | Visual issue documentation and supporting evidence. |
| Video Evidence | Capturing gameplay behaviour and reproduction evidence. |
| itch.io | Accessing and testing available project builds. |
โ What This Case Study Shows
- Ongoing QA Lead responsibility on an actively developed indie project.
- Player-focused exploratory testing from a first-time-user perspective.
- Charter-based testing adapted to developer priorities and changing builds.
- Targeted quest, progression, farming, and feature validation using developer-provided test states.
- Testing of interconnected inventory, gathering, crafting, farming, cooking, and progression systems.
- End-to-end validation of gameplay workflows, including planting, growth, harvesting, crop processing, and food production.
- Controlled comparison testing to validate system behaviour, including the effect of watering on crop growth.
- Identification of onboarding, progression, usability, feedback, and feature-discoverability risks.
- Investigation of unexpected behaviour to distinguish functional defects, intended behaviour, and player-experience issues.
- Reclassification of findings when developer clarification establishes intended design behaviour.
- Dialogue and content-quality checks alongside functional gameplay testing.
- Structured QA reporting with reproducible findings, evidence, player-impact analysis, and clear developer recommendations.
- Regression planning and feature validation across multiple development updates.
- Independent testing based on priorities agreed directly with the developer.
- Ongoing contribution to player-experience improvements and future demo readiness.
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.