Add note about AutoStartHost for integration tests #3869
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
2 participants
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.
I ran into some issues when running integration tests after switching my app to use app.RunJasperFxCommands(). At first, my WebApp worked fine without the CLI tools integration, so I didn’t notice anything was wrong. But once I added RunJasperFxCommands(), the test server wouldn’t start anymore.
I only found this info by chance in this section of the Wolverine docs:
https://wolverinefx.net/tutorials/cqrs-with-marten.html#creating-an-integration-test-harness
It might also be worth including this hint in the main testing guide here:
https://wolverinefx.net/guide/testing.html#test-automation-support
Since that’s where most people (including me) would probably look first.