Rethink running tests for all browsers in each browser #2523
Labels
package:paste-from-office
resolution:expired
This issue was closed due to lack of feedback.
status:discussion
status:stale
type:task
This issue reports a chore (non-production change) and other types of "todos".
Some time ago we have concluded that it will be good to run tests for all browsers in each browser (see #2481 and #2480). This allows to check if anything fails just by running tests in one browser. And since most of the things happening are detached from the DOM and use native API rarely it makes sense as browser environment does not affect those tests so much.
However, recently I have encountered a case were same input data, generates same normalization data but different model data in Chrome/Firefox vs Edge. Since test utils assumed that all tests are run in each browser, it required some not-good-looking tests skipping (see
skip
option):Of course it could be written in a different ways to be more readable, but the point is, that skipping test like this is kind of hackish and not straight forward. I think we can live with one case like this, but if we encounter few more in the future it will be good to rethink testing approach.
The text was updated successfully, but these errors were encountered: