Repository navigation
test(nodes): validate tutorial code and simplify scaffold tests - #216
Merged
Merged
Conversation
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.
The custom Node tutorial previously lacked automated validation of its actual C++ examples. Generate and compile fixtures directly from the three tutorial stages, execute their behavior examples, and check the registered Catalog descriptions, parameters and model bindings.
Add the test-only
NodeUnderTesthelper and use it in scaffolded tests to hide runtime wiring. Failed initialization clears the runnable node; focused tests cover failed requests, subsequent recovery and invalid initialization/input bindings. No production Node authoring contract changes.Validation: the canonical local gate passed with 465 tests passed and 5 asset-dependent tests skipped (470 total). Three mutation checks confirmed that an invalid C++ identifier, incorrect stage-1 output and missing stage-2 description are each detected. Existing real-model/asset-dependent checks remain skipped.