Repository navigation
Add Unittest component from component functionality - #761
Draft
IsakNaslundBh wants to merge 1 commit into
Draft
IsakNaslundBh wants to merge 1 commit into
IsakNaslundBh wants to merge 1 commit into
Conversation
IsakNaslundBh
added
status:do-not-merge
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.
Issues addressed by this PR
Closes #760
Adds initial code for creating a unit-test component based on a in-place component on the canvas in Grasshopper.
Please see issue for a bit more details, but this would essentially allow for more rapidly turning well working test-scripts into datadriven unit-tests (dataset unit tests).
The code in this PR is not suitable for merge atm, but just a proof of concept. Still needs to be figured out:
Not to be merged before the 9.3 release.
Test files
Changelog
Additional comments