Fail fast for jest when "testEnvironment": "node" is not set #364
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
Fail fast when
hearbeatTimer
is a number. This occurs in scenarios when a developer is using Jest for testing and they have failed to set"testEnvironment": "node"
. By throwing an error here it save development time troubleshooting.🎯 Relevant issues
ref: #362
💎 Type of change
🚦 How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Write a simple Jest test that does't override the default
testEnvironment
configuration and attempt to start a broker. An error will throw referencing issue #362 which has enough information to fix their code.