Finish wiring up multiple return values using "BlockData" objects #77
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
Added section on test data handling and BlockData usage.
Keboo
approved these changes
Sep 17, 2025
IntelliTect.TestTools.TestFramework.Tests/TestCaseTests/MultipleDependencyTests.cs
Outdated
Show resolved
Hide resolved
…ct/TestTools.TestFramework into multiple-return-values
Co-authored-by: Kevin B <[email protected]>
…ct/TestTools.TestFramework into multiple-return-values
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.
Description
Add support for a way for a test block to return multiple points of test data. Leverages a new IBlockData interface and three basic implementations (IBlockData<T1,T2 and T3, T4>).
NOTE: It is very possible, though not advised, to do other implementations without generic type arguments, as that circumvents a lot of the pre-execution checking that occurs to make sure top-level dependencies are all being satisfied.
Ensure that your pull request has followed all the steps below: