Repository navigation
Conversation
The Unity EditMode and PlayMode suites run in no CI, and #110, #141 and #143 show what that costs: a red PlayMode test on main that nobody saw. A CI licence is not available, so the lanes become a mandatory local step instead of a half-maintained one. tools/unity-tests/run_unity_tests.py drives both lanes in one command: never with -quit (Unity would report success without running anything), -nographics only for EditMode, abort when an editor holds the project, stale result files removed first, then freshness, test-count and failure checks plus a warning about leftovers in the working tree. AGENTS.md and CONTRIBUTING.md (5.1.0) name the trigger paths and the owner; the PR template gets the mandatory "Unity-Spuren" line. tests.yml is untouched. Refs #110 (close once D-125 is accepted). Measured on this branch with Unity 6000.5.4f1: EditMode 663/663, PlayMode 15/15; sim tests 778/778. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Was:
tools/unity-tests/run_unity_tests.pyfährt EditMode und PlayMode in einem Kommando: nie-quit,-nographicsnur EditMode, Abbruch bei offenem Editor, alte Ergebnisdatei vorher gelöscht, Prüfung auf Frische/Testanzahl/Fehlschläge, Warnung vor Resten im Arbeitsbaum,--self-test.AGENTS.mdundCONTRIBUTING.md(5.1.0) nennen Auslöserpfade und Zuständigkeit; PR-Vorlage mit Pflichtzeile „Unity-Spuren“.tests.ymlunverändert.Warum: Die Unity-Spuren laufen in keiner CI; #110, #141 und #143 zeigen die Folgen. Keine CI-Lizenz → lokale Pflichtspur statt Zwischenzustand. Refs #110 (Schließen nach Annahme von D-125, Entwurf).
Bereiche:
tools/unity-tests/(neu),AGENTS.md,CONTRIBUTING.md,.github/pull_request_template.md, DecisionLog, CHANGELOG. Kein Spielcode.Changelog:
[Unreleased]→ Hinzugefügt.Tests:
run_unity_tests.py --self-testgrün; Fake-Editor-Probe (-quit-Falle) Exit 1;dotnet test778/778;check_docs.pyOK; Guard-Selbsttest OK.Unity-Spuren: EditMode 663/663, PlayMode 15/15 auf diesem Branch (Basis a6858d1, Unity 6000.5.4f1). Mit demselben Skript wurden anschließend die Branches zu #138, #134, #67 und #127 gefahren.
Spielabnahme: entfällt (kein Spielverhalten). Restrisiko: nur unter macOS gefahren.
Hinweis:
AGENTS.mdist das Steuerdokument aller Agenten — Inhalt braucht die Zustimmung des Inhabers. Berichte:reports/v8.6.0/issue-lauf-2026-10-17/06-issue-110-*.md,06b-review-1-issue-110.md.🤖 Generated with Claude Code