Tweaks to get the acceptance tests running faster in environments wit… #193
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.
What
Tweaks to get the acceptance tests running faster in environments with lots of data:
Plus gofmt.
Fix timing issue in auth unit test
Why
Acceptance tests in production are failing due to them taking over 20 mins to run. The oauth token expires after 20 mins.
The tests are currently pulling down 150mb+ of data from the billing api with each successful call to billable-events.
How to review
Look at the changes
🚨⚠️ Please do not merge this pull request via the GitHub UI ⚠️ 🚨