chore: Run tests in real browser #292
Merged
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
lemuel-stripe
approved these changes
Nov 4, 2021
|
thanks for fixing the linter error @Feiyang1 |
This was referenced Nov 4, 2021
Merged
Merged
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.
We currently run tests using mocha (nodejs) + jsdom to emulate a browser environment. It loads the Nodejs version of the Firestore SDK which throws
TypeError: Invalid URL: index.node.cjs.jsbecause jsdom confuses it to think it's executing in a browser.The PR changes the tests to run in a real browser (chrome) to workaround this issue, and it's a more reliable test setup because tests will execute in the same environment where the SDK will be used.