Skip to content
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.

Sign up for GitHub

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

Jump to bottom

The assesrtions inside an QUnit.asyncTest are not evaluated asynchronously #4

Closed
gurdiga opened this issue Nov 5, 2009 · 2 comments
Closed

The assesrtions inside an QUnit.asyncTest are not evaluated asynchronously #4

gurdiga opened this issue Nov 5, 2009 · 2 comments

Comments

@gurdiga
Copy link

gurdiga commented Nov 5, 2009

Hi!

As far as I can understand from the code*, the assertions are always evaluated at the parsing time even if the test is asynchronous. One would expect them to be evaluated at the time QUnit.start() is called.
@gurdiga
Copy link
Author

gurdiga commented Nov 5, 2009

I misunderstood the thing... the actual and expected values are evaluated when the assertion method (ok, equals, same) is called.

Sorry for the noise.

@jeresig
Copy link
Contributor

jeresig commented Nov 15, 2009

That's ok! Let me know if you have any other questions.

mgol pushed a commit to mgol/qunit that referenced this issue Mar 24, 2021
@prathe
QUnit: testrunner.js: Ensures equality of types (String, Boolean, Num…
be7f675 
…ber) declared with the 'new' prefix.

See comments qunitjs#3, qunitjs#4 and qunitjs#5 on http://philrathe.com/articles/equiv
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jeresig @gurdiga