-
Notifications
You must be signed in to change notification settings - Fork 46
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
Add SauceLabs or BrowserStack tests #238
Comments
Could https://github.com/resin-io-modules/resin-config-karma be useful here? |
I already use it, but the target is currently PhantomJS which runs on the
CI box. The key is to use the real browsers like actual version of Chrome.
If it works with the same config it's great, but in my understanding it
should be run on a different platform, like SauceLabs.
Correct me if I'm wrong.
…On Tue, Dec 13, 2016 at 5:52 PM, Juan Cruz Viotti ***@***.***> wrote:
Could https://github.com/resin-io-modules/resin-config-karma be useful
here?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#238 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAgGCMWxskTQ41vfnfi244d-5fw3RKcSks5rHrFFgaJpZM4LLr3X>
.
--
Eugene Mirotin
Senior Frontend Engineer
site: Resin.io <https://resin.io/>, twitter: @resin_io
<https://twitter.com/resin_io>
|
We do use SauceLabs for |
Feel free to tweak the list of browsers we should support! |
Oh, I didn't know about it, great.
…On Tue, Dec 13, 2016 at 6:27 PM, Juan Cruz Viotti ***@***.***> wrote:
Feel free to tweak the list of browsers we should support!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#238 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAgGCOihqwd-bZJx718oCdAmf4ir4Up_ks5rHrlLgaJpZM4LLr3X>
.
--
Eugene Mirotin
Senior Frontend Engineer
site: Resin.io <https://resin.io/>, twitter: @resin_io
<https://twitter.com/resin_io>
|
Closing in favor of using balenaCI. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need to test this module (and ideally lower-level sub-modules) in the real browsers. PhantomJS is OK to check the compatibility with generic browser environment, but it's not the real browser.
I've recently hit a bug where Chrome had different implementation of some internal property.
The text was updated successfully, but these errors were encountered: