Revise testGetForecast to not make live API calls #7
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
While attempting to run the tests, testGetForecast consistently failed, with the exception's error message saying that the BOM API had detected the use of automation software during the request. Given that, and that it may well not be necessary to actually make a live request, this change updates the test to use a mock response with one of the fixture files instead. It also improves the performance of the test.
|
This is outdated now as tests don't make live requests any more. |
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.
While attempting to run the tests,
testGetForecast()consistently failed, with the exception's error message saying that the BOM API had detected the use of automation software during the request. Given that, and that it may well not be necessary to actually make a live request, this change updates the test to use a mock response with one of the fixture files instead. It also improves the performance of the test.