Game test says passed? Keep actions and screenshots

Use Cursor with a Godot test scene and acceptance criteria to prepare action logs, screenshots and untested items through the test workflow below, then review it. Matching tools and permissions are required.

Execution environment and usage

AI / software

Cursor

Where to operate

The Agent panel in the Cursor code editor, with a project copy open.

Getting started

  1. Use the official setup guide to install/sign in to Cursor; open an isolated test project or data copy.
  2. Supply a Godot test scene and acceptance criteria and the prompt below. Confirm the scope before allowing necessary actions.
  3. Inspect the resulting action logs, screenshots and untested items; record anything not run or not verified.

Setup and plan requirements

Requires access to Cursor, authorized test data and a matching runtime; file writes and shell commands must stay within approved scope. Preparation: Prepare an owned test copy, reviewed tools, a specified scene and acceptance criteria. Requires Godot, a runnable scene and reviewed input/screenshot tools. The source plugin was not rerun here; absent real actions and images means untested.

Prompt portability limits

Adapt the wording to another coding assistant only after separately configuring files, runtime, test tools and integrations. Renaming the tool does not establish compatibility.

Usage limitations

This workflow was not hands-on tested. Work on test copies; no automatic publishing, payment or production-data changes. Separate plans, actual results and untested areas.

Environment sources

適用情境 / When to use

Use Cursor with a Godot test scene and acceptance criteria to prepare action logs, screenshots and untested items through the test workflow below, then review it. Matching tools and permissions are required. Joelnicolass publishes a Godot testing tool for Cursor or Claude Code to operate scenes and retain screenshots and pass/fail results.

步驟 / Steps

  1. Prepare an owned test copy, reviewed tools, a specified scene and acceptance criteria.
  2. Use existing mapped inputs and record the action sequence and actual screenshots.
  3. Check every criterion and error log; mark unavailable scenes or visuals untested.

提示詞 / Prompt

Test [scene and acceptance criteria] in [game test copy] using only [existing inputs]. Return action logs, screenshots and pass/fail/untested reasons. Stop if the scene is missing; create no substitute world, change no game rules and claim no complete coverage.

留意事項 / Cautions

  • Never fabricate screenshots or bypass game state through code.
  • Do not change gameplay rules, input mappings or production saves.

來源限制 / Evidence limits

Project documentation describes functionality without coverage or reliability evaluation; a working game window and scene are required.

流程說明 / Workflow note

These steps and prompts are original, untested exercises by this site, not the author’s verbatim workflow. Reported results do not guarantee exercise outcomes.

原始工具組合 / Original tool stack

Cursor or Claude Code; Godot 4; godot-studio-playtest plugin and CLI

Source checked: 2026-10-19

Godot studio playtest