issue: add a label "testing" for test reports #663

Closed

opened 2026-11-08 16:14:23 +00:00 by adnanioricce · 2 comments

adnanioricce commented

2026-11-08 16:14:23 +00:00

(Migrated from github.com)

The idea

some label to categorize the test reports, could help diagnose problems and also help place them somewhere, giving that currently it seems only possible to add this info in bug or enhancement issues.

Anything else

No response

### The idea some label to categorize the test reports, could help diagnose problems and also help place them somewhere, giving that currently it seems only possible to add this info in bug or enhancement issues. ### Anything else _No response_

adnanioricce commented

2026-11-08 16:24:31 +00:00

(Migrated from github.com)

example:

name: Test report
   description: What you played on your hardware and how it ran, even when nothing broke
   labels: [test report]
   body:
     - type: markdown
       attributes:
         value: |
           Thanks for testing. This form is for a whole run on your hardware: what you reached, how it ran, and what
 broke, **even when nothing did**. AMD and Intel cards, SteamOS and other drivers are the reports the project has the
 least of.

           If one thing is broken, use **Game problem** for it instead, and link the issues here. Before you start:
 newest [release](https://github.com/NotRexed/Hookshot/releases/latest), search the open issues, English, please.
 **Never attach game files**: no hookshot.exe, image.bin, the `.bin` caches, romfs or exefs files, keys or saves.
     - type: input
       id: version
       attributes:
         label: Hookshot version
         description: The release you built (its name on the Releases page, such as `movie-sync`), or the first line
 of `hookshot_log.txt` if it starts with `hookshot`.
         placeholder: movie-sync
       validations:
         required: true
     - type: dropdown
       id: how
       attributes:
         label: How you built it
         options:
           - Hookshot Builder app (Windows)
           - Linux AppImage
           - Command line (nx2/make_game.py)
       validations:
         required: true
     - type: dropdown
       id: os
       attributes:
         label: Operating system
         options:
           - Windows 11
           - Windows 10
           - SteamOS
           - Linux (distribution named below)
       validations:
         required: true
     - type: input
       id: gpu
       attributes:
         label: Graphics card and driver version
         description: The driver version matters as much as the card. Windows shows it under "Driver version" in the
 NVIDIA, AMD or Intel panel; on Linux, `vulkaninfo --summary` or `glxinfo -B`.
         placeholder: Radeon RX 7900 XTX, Mesa 25.1.2
       validations:
         required: true
     - type: input
       id: system
       attributes:
         label: CPU, RAM and the distribution if Linux
         placeholder: Ryzen 7 7700, 32 GB, Ubuntu 24.04
       validations:
         required: true
     - type: textarea
       id: played
       attributes:
         label: What you played
         description: How long, and how far you got. Areas, dungeons, cutscenes, menus, items, and anything you tried
 more than once.
         placeholder: About 3 hours. Kokiri Forest, Link's house, the first shop, Hyrule Field. Opened every menu
 page, saved and reloaded twice.
       validations:
         required: true
     - type: checkboxes
       id: worked
       attributes:
         label: What worked
         description: Tick everything that did its job, so a report with no problems still says something.
         options:
           - label: Sound
           - label: Controller
           - label: Keyboard and mouse
           - label: Saves and loading a save
           - label: In-game menu (Insert)
           - label: Frame generation
           - label: Upscaling and sharpness
           - label: Movies and cutscenes
           - label: Window and fullscreen, alt-tab out and back
     - type: textarea
       id: problems
       attributes:
         label: What broke
         description: One line per problem, with where you were and what you saw. Open a separate **Game problem**
 issue for each one and paste the links here. Leave empty if nothing did.
         placeholder: The fences in Kokiri Forest flicker when the camera turns (#123). Black flash leaving Link's
 house (#124).
     - type: textarea
       id: fps
       attributes:
         label: Frame rate
         description: Turn the FPS counter on (Insert menu) and do this with **Frame generation off** first. Say
 standing still and walking, for each place you listed, then the same with generation on if you used it.
         render: text
         placeholder: |
           Kokiri Forest, standing still: 58 fps
           Kokiri Forest, walking around: 50 fps
           Hyrule Field, running: 41 fps
           Frame generation off, Balanced preset, Auto resolution
       validations:
         required: true
     - type: textarea
       id: settings
       attributes:
         label: Changes from the defaults
         description: Insert-menu options you changed (preset, frame generation, pacing, resolution, upscaling, game
 speed), the lines in `hookshot_env.txt`, and any switch you tested (such as `RX_VK_NOOPT=1`) with what changed. Leave
 empty if none.
     - type: markdown
       attributes:
         value: |
           If the frame rate is the problem, add `RX_VK_SLOW_LOG=15` and `HOS_HOSTCALL_STATS=1` to `hookshot_env.txt`
 before the run. The log then says where each slow frame went, and a report with that in it is worth ten without.
     - type: dropdown
       id: injectors
       attributes:
         label: Other software hooked into the game
         description: ReShade, shader-cache tools (SCSKiller and the like), overlays or frame-generation injectors
 change what Hookshot does. Please test without them before reporting.
         options:
           - None
           - Yes (named under "Changes from the defaults")
       validations:
         required: true
     - type: textarea
       id: log
       attributes:
         label: hookshot_log.txt
         description: Drag the file here, one per build or switch you compared. It is beside hookshot.exe and holds
 the last run only, so attach it right after the run. It has no game files in it.
       validations:
         required: true
     - type: textarea
       id: media
       attributes:
         label: Screenshots or video
         description: Most useful for a picture problem, and for anything hard to describe.
     - type: checkboxes
       id: checks
       attributes:
         label: Before you send it
         options:
           - label: I'm on the newest release, or the report says which older one I ran.
             required: true
           - label: I searched the open issues and linked the ones this report touches.
             required: true
           - label: I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.
             required: true
           - label: I named every overlay or injector that was loaded.
             required: true
           - label: Where I compared builds or switches, I used the same place in the game for the same time.
             required: true```

example: ```yaml name: Test report description: What you played on your hardware and how it ran, even when nothing broke labels: [test report] body: - type: markdown attributes: value: | Thanks for testing. This form is for a whole run on your hardware: what you reached, how it ran, and what broke, **even when nothing did**. AMD and Intel cards, SteamOS and other drivers are the reports the project has the least of. If one thing is broken, use **Game problem** for it instead, and link the issues here. Before you start: newest [release](https://github.com/NotRexed/Hookshot/releases/latest), search the open issues, English, please. **Never attach game files**: no hookshot.exe, image.bin, the `.bin` caches, romfs or exefs files, keys or saves. - type: input id: version attributes: label: Hookshot version description: The release you built (its name on the Releases page, such as `movie-sync`), or the first line of `hookshot_log.txt` if it starts with `hookshot`. placeholder: movie-sync validations: required: true - type: dropdown id: how attributes: label: How you built it options: - Hookshot Builder app (Windows) - Linux AppImage - Command line (nx2/make_game.py) validations: required: true - type: dropdown id: os attributes: label: Operating system options: - Windows 11 - Windows 10 - SteamOS - Linux (distribution named below) validations: required: true - type: input id: gpu attributes: label: Graphics card and driver version description: The driver version matters as much as the card. Windows shows it under "Driver version" in the NVIDIA, AMD or Intel panel; on Linux, `vulkaninfo --summary` or `glxinfo -B`. placeholder: Radeon RX 7900 XTX, Mesa 25.1.2 validations: required: true - type: input id: system attributes: label: CPU, RAM and the distribution if Linux placeholder: Ryzen 7 7700, 32 GB, Ubuntu 24.04 validations: required: true - type: textarea id: played attributes: label: What you played description: How long, and how far you got. Areas, dungeons, cutscenes, menus, items, and anything you tried more than once. placeholder: About 3 hours. Kokiri Forest, Link's house, the first shop, Hyrule Field. Opened every menu page, saved and reloaded twice. validations: required: true - type: checkboxes id: worked attributes: label: What worked description: Tick everything that did its job, so a report with no problems still says something. options: - label: Sound - label: Controller - label: Keyboard and mouse - label: Saves and loading a save - label: In-game menu (Insert) - label: Frame generation - label: Upscaling and sharpness - label: Movies and cutscenes - label: Window and fullscreen, alt-tab out and back - type: textarea id: problems attributes: label: What broke description: One line per problem, with where you were and what you saw. Open a separate **Game problem** issue for each one and paste the links here. Leave empty if nothing did. placeholder: The fences in Kokiri Forest flicker when the camera turns (#123). Black flash leaving Link's house (#124). - type: textarea id: fps attributes: label: Frame rate description: Turn the FPS counter on (Insert menu) and do this with **Frame generation off** first. Say standing still and walking, for each place you listed, then the same with generation on if you used it. render: text placeholder: | Kokiri Forest, standing still: 58 fps Kokiri Forest, walking around: 50 fps Hyrule Field, running: 41 fps Frame generation off, Balanced preset, Auto resolution validations: required: true - type: textarea id: settings attributes: label: Changes from the defaults description: Insert-menu options you changed (preset, frame generation, pacing, resolution, upscaling, game speed), the lines in `hookshot_env.txt`, and any switch you tested (such as `RX_VK_NOOPT=1`) with what changed. Leave empty if none. - type: markdown attributes: value: | If the frame rate is the problem, add `RX_VK_SLOW_LOG=15` and `HOS_HOSTCALL_STATS=1` to `hookshot_env.txt` before the run. The log then says where each slow frame went, and a report with that in it is worth ten without. - type: dropdown id: injectors attributes: label: Other software hooked into the game description: ReShade, shader-cache tools (SCSKiller and the like), overlays or frame-generation injectors change what Hookshot does. Please test without them before reporting. options: - None - Yes (named under "Changes from the defaults") validations: required: true - type: textarea id: log attributes: label: hookshot_log.txt description: Drag the file here, one per build or switch you compared. It is beside hookshot.exe and holds the last run only, so attach it right after the run. It has no game files in it. validations: required: true - type: textarea id: media attributes: label: Screenshots or video description: Most useful for a picture problem, and for anything hard to describe. - type: checkboxes id: checks attributes: label: Before you send it options: - label: I'm on the newest release, or the report says which older one I ran. required: true - label: I searched the open issues and linked the ones this report touches. required: true - label: I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves. required: true - label: I named every overlay or injector that was loaded. required: true - label: Where I compared builds or switches, I used the same place in the game for the same time. required: true```

NotRexed commented

2026-11-09 05:52:58 +00:00

(Migrated from github.com)

Thanks for the idea. Feature requests are now collected in #1007, which lists this one with a link back here, so closing it in favour of that list (this is not a decision against the idea).

👍 1

Commenting is not possible because the repository is archived.