Generalizing AnnotationBasedTestSuite to allow custom AnnotatedTestInputs
#862
Conversation
This file contains 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.
buildTestInputis currently quite restrictive as it only allows to return an instance of theDefaultAnnotatedTestInputcase class. This PR relaxes this constraint such that instances of custom case classes extendingAnnotatedTestInputcan be returned.This allows us in Gobra to extend a test input with additional arguments, namely a Gobra instance and an execution context, such that all data necessary to execute a testcase is contained in the corresponding test input. In particular, the execution of a testcase, thus, does not depend on fields of the corresponding test suite making parallel execution of testcases easier.