-
Notifications
You must be signed in to change notification settings - Fork 784
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
module name is not shown #3
Comments
This commit seems to have fixed the issue, although it is untested with asyncTest stuff (which is when this issue was introduced). http://github.com/zhaoz/qunit/commit/13eec8f1e6dbbde59aa07ee74dd25ca03ba80e87 |
This does work for me, though I haven't tested it with and asyncTests either. |
I merged in zhaoz's commit - hopefully this fixes the problem. |
vivin
added a commit
to vivin/qunit
that referenced
this issue
Aug 16, 2012
Approach qunitjs#3: Public "enum" used for assertion type. Removed some of the tests because it seemed like they were more trouble than they were worth. It does have a few tests that checks for the assertion type.
mgol
pushed a commit
to mgol/qunit
that referenced
this issue
Mar 24, 2021
…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
When modules are defined, their names do not appear (for me) next to the test names in the output.
The config object is defined on line 353, and config is assigned to in QUnit.init
config.currentModule
is set in the module function and accessed in the test function. It looks like a different config object is being referenced in each of the different functions.The text was updated successfully, but these errors were encountered: