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
Currently, using a string instead of a number as an argument for assert.async in QUnit causes the test page to hang indefinitely without providing diagnostic messages. To enhance this function and improve diagnostics, we propose adding type checking.
Code that reproduces the problem:
QUnit.test("Test type checking for async",function(assert){assert.async("the test should fail");});
What did you expect to happen?
While running the code above, the test should fail and deliver proper diagnostics message.
What actually happened?
The test hang indefinitely.
The text was updated successfully, but these errors were encountered:
What are you trying to do?
Currently, using a string instead of a number as an argument for assert.async in QUnit causes the test page to hang indefinitely without providing diagnostic messages. To enhance this function and improve diagnostics, we propose adding type checking.
Code that reproduces the problem:
What did you expect to happen?
While running the code above, the test should fail and deliver proper diagnostics message.
What actually happened?
The test hang indefinitely.
The text was updated successfully, but these errors were encountered: