-
Notifications
You must be signed in to change notification settings - Fork 664
Navigation: Fix unstable Qunit tests #32192
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
base: 26_1
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
packages/devextreme/testing/tests/DevExpress.viz.vectorMap/projection.tests.js
Show resolved
Hide resolved
| } else { | ||
| QUnit.test(name, callback); | ||
| } | ||
| function conditionalTest(name, isUnsupportedConfig, callback) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At the moment, it looks the same as before. I suggest we fix the current valid values for unsupported scenarios here and consider them correct.
| }); | ||
| }; | ||
|
|
||
| QUnit.assert.arraysRoughEqual = function(actual, expected, message, percentTolerance = 10) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let’s not add new helper functions for this purpose. I suggest removing it and fixing the current expected values directly in the tests
No description provided.