Grove Bound - Ongoing QA Case Study

🧾 Project Overview

🎯 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

🛠️ 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.

🧭 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, crafting, cooking, buildable systems, dialogue, save integrity, puzzles, and player-facing usability. Testing priorities have changed between builds based on development needs and previously identified risks.

The timeline below shows how my QA coverage has expanded and shifted alongside the project's development.

✓ 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 potential discoverability and guidance issues.

The testing included both successful end-to-end quest validation and investigation of progression friction. Individual systems were tested independently where appropriate to help distinguish between a functional problem and unclear communication of the intended interaction.

Dialogue was also reviewed during these passes for grammar, spelling, punctuation, capitalisation, and formatting issues.

⚠️ Current Player-Facing Risk Areas

🤝 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

✅ 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.
• Targeted quest, progression, and feature validation using developer-provided test states.
• Identification of onboarding, progression, usability, and discoverability risks.
• Testing of interconnected inventory, crafting, cooking, and progression systems.
• Investigation of progression friction while distinguishing functional issues from unclear player guidance.
• Dialogue and content-quality checks alongside functional gameplay testing.
• Structured QA reporting with defined scope, findings, and player-impact analysis.
• Regression testing 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.