You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 2, 2021. It is now read-only.
Hi. Looking for issues to contribute to, and this seems potentially like a good one. A few questions:
Do you expect the browser emulation to happen in CI?
Do you use any existing browser testing framework at the moment?
When considering "compatibility", what errors do you expect to arise? My naive guess is that there are two broad types:
Backend logic not being supported by the browser (non-UI related). The project seems to have some logic tests already, so some of these types of errors should be caught by those tests, if we run on an unsupported browser. (Though I also don't really know what it means to run the tests "on" a given browser, or if it's even possible.)
UI-related bugs due to unsupported/differently-supported features. I'm not sure how to test these at the moment, but I'm going to guess there are a million frameworks for doing UI testing of webapps (seems like Selenium is one of the de-facto frameworks?)
I'm definitely new to webapp dev, but hoping I can learn this stuff quick! Thanks!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We need to understand and document how to determine the lowest browser setting
Related to #41 .
The text was updated successfully, but these errors were encountered: