Add cross-browser interoperability testing #576
Closed
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
update twin tap disable remote address test which is blocked by mDNS in chrome update twin tap fix race condition with close listener update twintap coveralls add badge to README fix test paths update twintap update twintap update twintap update twintap update twintap fix race condition with close/destroy
…peer into feature/twintap
|
Merged with #694 |
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.
Currently, all the tests only run within a single page on the same browser. This adds tests for interoperability between different browsers. (Safari->Firefox, Firefox->Chrome, etc).
To do this, I've modified
airtapto allow splitting a single unit test onto two different browers. (twintap). This works in Saucelabs and locally.All of these tests pass.