Back to Game QA Portfolio hub

🍽️ The Chef's Shift - Early Build QA - Core Loop & System Interaction Case Study (PC)

Tested: 16 Apr–17 Apr 2026

Introduction

This case study is part of my game QA portfolio.

This project is a focused early build QA pass on The Chef’s Shift (PC, v0.1.2a), tested across 16–17 April 2026. The project targeted core loop stability, system interaction, input handling, recovery behaviour, and accessibility-related pressure points from a first-time player perspective.

Testing was charter-driven and risk-based rather than exhaustive. The goal was not full content coverage or full regression, but to identify the issues most likely to disrupt progression, create player confusion, or expose accessibility barriers in a typing-based gameplay loop.

Alongside core QA, I applied an accessibility lens informed by my APX Practitioner training to examine how typed input, readability, multitasking, and UI clarity affected player performance under pressure. This strengthened the analysis of player-facing friction without turning the project into a full accessibility audit.

• Scope: Short, self-directed QA pass on The Chef’s Shift (PC, v0.1.2a), covering the core loop (prepare → tray → serve → collect → repeat), input handling, serving flow, recovery/progression, and accessibility-related pressure points. No claim of studio coverage or full regression.
• Approach: Risk-based charter testing executed through a Test Matrix and Session Log. Core tests validated the main loop, invalid actions, recovery, and input behaviour, followed by accessibility-focused passes examining typing under pressure, readability, action chain complexity, and order association clarity.
• Outcome: 8 logged sessions (S1 to S8) produced 2 tracked issues. The main findings were a core loop blocking payment inconsistency (CHEF-1) and a UI visibility/readability issue affecting oven interaction under pressure (CHEF-2).
• Evidence: Workbook tabs (Test Matrix, Session Log, Bug Log, STAR summaries) supported by video evidence per session and per issue. Jira tickets were also created to mirror real-world workflow and strengthen traceability from test execution to logged defect.

📊 Metrics

⭐ STAR SUMMARY - The Chef’s Shift - Early Build QA - Core Loop & System Interaction (PC)

Situation: Short, self-directed QA portfolio project on The Chef’s Shift (PC, build v0.1.2a). Testing focused on a typing-based core loop where input handling, flow stability, and prompt visibility could quickly affect progression.

Task: Run a realistic early build QA pass focused on core loop stability, input reliability, system interaction, recovery/progression, and accessibility-related pressure points from a first-time player perspective.

Action: Created a charter-driven Test Matrix, then executed 8 structured sessions (S1 to S8) with linked video evidence. Covered baseline loop flow, repetition, invalid serving, recovery, input correction, complexity under pressure, readability, and order association clarity. Logged issues in a structured Bug Log and mirrored key defects in Jira with reproducible steps and evidence.

Result: Logged 2 gameplay-impacting issues: a core loop blocking payment inconsistency (CHEF-1) and a UI visibility/readability issue affecting oven interaction under pressure (CHEF-2). Also validated that invalid serving, recovery/progression, input correction, and order association remained stable outside failure scenarios. Testing showed that performance shifted from input accuracy at low complexity to cognitive load and task management at higher complexity.

📚 Accessibility Training & Application

For this project, I applied learning from the Accessible Player Experiences (APX) Practitioner certification to add an accessibility-focused lens to a core loop and system interaction QA pass.

This was not a full accessibility audit. The main project focus remained early build QA of the core gameplay loop, input handling, serving flow, and recovery. APX was used to strengthen the analysis of player-facing pressure points, especially where readability, typing speed, multitasking, and UI clarity affected gameplay performance.

APX patterns applied in this project:

• Flexible Text Entry - informed checks around typing speed, correction behaviour, and how input pressure affects performance.
• Clear Text - informed readability checks, especially recognition speed under pressure and the impact of text presentation on decision-making.
• Distinguish This From That - informed checks around prompt visibility and whether important information was easy to separate from surrounding UI/background noise.
• Do More With Less - helped frame whether failure came from unnecessary action complexity or from genuine gameplay challenge.
• Slow It Down - supported analysis of how performance changed when typing pace was deliberately reduced under pressure.
• Undo Redo - supported evaluation of recovery behaviour when players mistyped, reset input, or re-targeted actions.

Outcome: Applying APX improved the project in two ways. First, it helped separate system failures from player performance limits. Second, it made the accessibility findings more specific, especially around the shift from input accuracy at low complexity to cognitive load and task management at higher complexity.

Verify APX Practitioner

📷 Evidence & Media

These links are the complete artefacts for this project. They contain:

• Overview and scope
• Test Matrix and Session Log
• Bug Log
• STAR summaries

📌 Core Project Findings - Sessions and Bugs

This project was a charter-driven early build QA pass on The Chef’s Shift (PC, v0.1.2a). Across 8 logged sessions (S1 to S8), I focused on core loop stability, system interaction, input correction, recovery/progression, and accessibility-related pressure points including readability, prompt visibility, and task management under higher complexity.

Across the project I logged 2 issues in the Bug Log. The highest-impact finding was a core loop blocking payment inconsistency (CHEF-1), followed by a UI visibility/readability issue affecting oven interaction under pressure (CHEF-2). Outside those defects, the project also validated several stable behaviours, including invalid serve rejection, input correction, Retry/Continue state reset, and order association clarity.

🗂️ Jira - Bug Tickets

Click any thumbnail to view the full-size image.

🐞 Bugs – Summary + Screenshots/Videos

ID	Title	Sev	Repro	Evidence
CHEF-1	Payment input accepted but payment behaviour is inconsistent when multiple customers are active	High	3/3
CHEF-2	Oven interaction prompt is difficult to see against background during pizza step	Medium	Observed repeatedly under pressure

📈 Results

• Completed a focused, charter-driven early build QA pass on The Chef’s Shift (PC, v0.1.2a), across 8 logged sessions (S1 to S8).
• Logged 2 issues in total in the Bug Log: 1 high and 1 medium.
• Repro evidence was recorded per issue, including a 3/3 blocking defect (CHEF-1) and a repeated under-pressure UI visibility issue (CHEF-2).
• Primary blocker: payment progression. Repeated loop testing exposed a payment inconsistency that blocked core loop progression and prevented repeat-loop validation (CHEF-1).
• Primary Accessibility/UI issue: prompt visibility and readability under pressure. Readability and prompt visibility problems slowed recognition, caused missed interactions, and delayed service (CHEF-2).
• Stable systems were also validated. Invalid serving, input correction, Retry/Continue progression, and order-to-customer association all behaved consistently outside failure scenarios.
• Pressure shifted from execution to cognition. At low complexity, performance was limited mainly by typing accuracy. At higher complexity, the limiting factor shifted toward cognitive load, situational awareness, and task management.

See Metrics above for the full table of runs and references.

🏁 Result and takeaway

Result: Across a focused early build QA pass on The Chef’s Shift (PC, v0.1.2a), I completed 8 logged sessions and recorded 2 gameplay-impacting issues in the Bug Log, each supported by evidence and traceable through the Test Matrix, Session Log, Bug Log, and Jira.

Takeaway: The highest-impact risks were a core loop blocker in payment handling and a visibility/readability issue affecting interaction prompts under pressure. The project also showed that not all difficulty comes from system failure: under higher complexity, player performance shifted from typing accuracy to cognitive load and multitasking pressure. This made the accessibility lens valuable for separating broken systems from player-facing friction.

🧠 What I learned

• Risk-based scoping finds signal faster. Focusing on high-risk gameplay surfaces made it possible to identify a core loop blocker quickly without wasting time on fake thoroughness.
• Repetition testing exposes blockers fast. A clean baseline run can look fine, but repeated loop testing is where unstable systems often break.
• Not every difficult moment is a bug. Some pressure points came from player execution limits or multitasking load rather than system failure, which is exactly why accessibility-aware testing matters.
• Readability and visibility can break gameplay just as much as logic bugs. CHEF-2 showed that a missed UI prompt can delay service and disrupt progression even when the underlying system still works.
• Stable systems matter too. Confirming that invalid serving, recovery flow, and order association behaved correctly strengthened the project more than trying to force extra bugs.
• Good admin makes the work easy to audit. Session IDs, linked evidence, bug IDs, and mirrored Jira tickets made the project easy to trace from test execution to final findings.

🔚 Conclusion

Focused early build QA pass completed on The Chef’s Shift (PC, v0.1.2a), tested across 16–17 April 2026. The project was tightly scoped to core loop and system interaction risks, using structured charters rather than broad, unbounded exploration.

• Coverage delivered: baseline and repeated core loop checks, input correction, invalid action handling, Retry/Continue progression, pressure and complexity analysis, readability under pressure, and order association clarity.
• Highest-impact findings: a gameplay-blocking payment inconsistency (CHEF-1) and a UI visibility/readability issue affecting oven interaction under pressure (CHEF-2). Together, these show both a true system failure and a player-facing clarity risk.
• Evidence maturity: Coverage and outcomes are traceable through the Test Matrix and Session Log, with 2 logged issues recorded in the Bug Log and mirrored in Jira. Each issue includes severity, reproducibility, and linked evidence, providing a clear audit trail from test execution to conclusion.

Up next: a controller parity QA case study on Recompile (PC), focused on input feel, mapping accuracy, and behaviour consistency across multiple Xbox-style controllers. The project will cover latency, dead zones, prompt clarity, and hot-swap handling to evaluate how reliably the game supports different input scenarios.

Email Me Connect on LinkedIn Back to Manual Portfolio hub

📎 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.