Skip to content
Skills Library
Programming · Testing

grasshopper-testing

/grasshopper-testing

Validate Grasshopper components and Rhino plugins with pure-core tests, host integration, saved-definition round trips, and real canvas or viewport checks. Use when testing plugin behavior or diagnosing host-specific test failures.

Licence
MIT
Last repository change
10.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Validate Grasshopper components and Rhino plugins with pure-core tests, host integration, saved-definition round trips, and real canvas or viewport checks. Use when testing plugin behavior or diagnosing host-specific test failures.

Original author description

Validate Grasshopper components and Rhino plugins with pure-core tests, host integration, saved-definition round trips, and real canvas or viewport checks. Use when testing plugin behavior or diagnosing host-specific test failures.

How it works

  1. Select evidence by behavior
  2. Make the run trustworthy
  3. Report the actual result
Original SKILL.md headings · 32 lines, 388 words
SKILL.md preview
---
name: grasshopper-testing
description: Validate Grasshopper components and Rhino plugins with pure-core tests, host integration, saved-definition round trips, and real canvas or viewport checks. Use when testing plugin behavior or diagnosing host-specific test failures.
---

# Grasshopper testing

Choose the cheapest layer that can observe the behavior being changed. A successful build, a headless solve and a real viewport check establish different things.

- Read [Verification layers and GH fixtures](references/verification-layers.md) to choose checks or build repeatable definitions.
- Read [Host identity and crash triage](references/host-triage.md) when a test loads the wrong plugin, crashes in Rhino/GH startup, or appears to ignore keyboard input.

## Select evidence by behavior

| Changed behavior | Useful evidence |
|---|---|
| Numerical algorithm, state transition, parser, replay or key deduplication | Host-free tests with numerical/behavioral invariants |
| Rhino geometry adaptation, GH inputs/outputs, warnings, resource lookup | Real Rhino/GH integration using the exact build under test |
| Wiring, persistence, defaults, migrations, examples | Save, close and reopen a GH definition; solve and inspect restored state |
| Canvas controls, focus, hooks, viewport/HUD, DPI, cancellation and cleanup | Interactive Rhino/GH with the actual UI or genuine input path |
| Runtime/package compatibility | Loading and smoke checks for each supported runtime/package variant |

Keep the test runner's target framework and dependency model compatible with the code it exercises. Moyu compiles its host-free source files directly into a separate runner; a separate core assembly is another valid design.

## Make the run trustworthy

- Identify the exact loaded assembly path, host version and runtime. Refuse or report a stale installed copy instead of testing it as if it were the new build.
- For iterative GH components, expire and solve deliberately. Check initial/paused state, one advance, changed input, reset and completion as relevant; an output merely being non-null is weak evidence.
- Pair positive scenarios with the specific invalid or boundary input the change handles. Use stable numerical or geometry invariants rather than a screenshot alone.
- Treat generated examples as deliverables: reopen the saved file and check links, defaults and execution. Avoid silently overwriting user-edited examples when regenerating fixtures.
- Keep host-specific tests explicit about prerequisites. Missing licensed Rhino or unavailable interactive UI is an unrun layer, not a passing test.

## Report the actual result

State what ran, the build/host used, and what the result establishes. Name meaningful failures or unavailable layers. A software-rendered geometry image from a headless test is useful evidence of data, but is not a captured Rhino viewport or proof that keyboard/focus behavior works.
Files in this package (4)
  • SKILL.md 3 KB
  • agents/openai.yaml 1 KB
  • references/host-triage.md 5 KB
  • references/verification-layers.md 7 KB

Versions

The database has no other skills named grasshopper-testing.

Database snapshot: 13.11.2026 · package version a45453aaf368 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100grasshopper-plugin-development
    Develop or revise C# Grasshopper plug-ins for Rhino, including component contracts, custom data, state and persistence. Use for new components, architecture changes, or diagnosing host integration; use the focused icon, interaction, testing, or release skills for those specific tasks.
  • 90grasshopper-interaction-display
    Build or debug Grasshopper canvas controls, Rhino viewport previews, interactive sessions, keyboard or mouse handling, and persisted display preferences. Use for host-integrated interaction rather than standalone application or game development.
  • 98rhino-gh-vscode-setup
    Create a Grasshopper plug-in project that builds and debugs from VS Code with F5 (Rhino 8, Windows). Use when asked to set up, scaffold or initialise a Grasshopper (.gha) plug-in project, or to make VS Code behave like Visual Studio for Rhino and Grasshopper development, in a folder the user names.
  • 90execute-grasshopper
    Use when the user asks to build or modify a Grasshopper definition through Rook.
  • 100sofistik-rhino-cdb
    Write C# scripts for the Grasshopper C# Script component or the Rhino script editor that read a SOFiSTiK CDB database (*.cdb) through the SOFiSTiK.Analysis.Database assembly - geometry, analysis results, cross sections, tendons and axes. Use this skill whenever the user wants to…
  • 90design-grasshopper
    Use when a Grasshopper request is ambiguous or open-ended and the user needs alternatives, constraints, or acceptance criteria clarified.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.