Describe the real Fixie setup in the No State found error - #1902
Merged
Conversation
The message told users to inherit from VerifyTestProject, a type that does not exist in the package, the repo, or the docs. It fires exactly when a user has not wired Verify into Fixie yet, so it sent them looking for a base class that was never there. It now states the actual requirement: implement Fixie's ITestProject and IExecution, assign the target assembly, and wrap each run in ExecutionState.Set.
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 message told users to inherit from VerifyTestProject, a type that does not exist in the package, the repo, or the docs. It fires exactly when a user has not wired Verify into Fixie yet, so it sent them looking for a base class that was never there.
It now states the actual requirement: implement Fixie's ITestProject and IExecution, assign the target assembly, and wrap each run in ExecutionState.Set.