Skip to content

chore(test): expand browser coverage #1133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

kwonoj
Copy link
Member

@kwonoj kwonoj commented Jan 5, 2016

  • expand browser test coverage, now includes ff, chrome, latest ios & latest android.
  • test timeout are increased due to mobile browser testing, which takes time to boot up emulator

These sets are 'known good' coverage, while other browser version / platforms are failing for some reason requires some of codebase updates (i.e, ie fails by promise impl, edge fails by test hang, etcs..) which'll be updated further.

@kwonoj
Copy link
Member Author

kwonoj commented Jan 5, 2016

relates to #998 .

@kwonoj
Copy link
Member Author

kwonoj commented Jan 6, 2016

Merged with d2e852c.

@kwonoj kwonoj closed this Jan 6, 2016
@kwonoj kwonoj deleted the test-browser branch January 6, 2016 07:35
@staltz
Copy link
Member

staltz commented Jan 7, 2016

@kwonoj how about adding a big Sauce Labs banner showing the browser support?

In Cycle.js we do this in README.md:

[![Sauce Test Status](https://saucelabs.com/browser-matrix/cyclejs-dom.svg)](https://saucelabs.com/u/cyclejs-dom)

screen shot 2016-01-07 at 12 07 50

@kwonoj
Copy link
Member Author

kwonoj commented Jan 7, 2016

@staltz That's plan, after moving test execution account. Currently test is executed via my account, (https://saucelabs.com/u/ojkwon) and account for RxJS need to be created. Once it's done, I'll add big, shine green banner to repo. :)

@lock
Copy link

lock bot commented Jun 7, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants