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

Measure performance (duration) of each test #344

Closed
gibson042 opened this issue Nov 3, 2012 · 1 comment
Closed

Measure performance (duration) of each test #344

gibson042 opened this issue Nov 3, 2012 · 1 comment
Labels
Type: Enhancement New idea or feature request.

Comments

@gibson042
Copy link
Member

QUnit shows a convenient "Tests completed in milliseconds" upon suite completion, but doesn't break that down to individual tests/modules.

I'd like to get the jQuery suite completing locally in under a minute, and having timing data available on the <li> output for each test would help tremendously.
@Krinkle
Copy link
Member

Krinkle commented Nov 3, 2012

This has been brought up before at jquery/testswarm#156, I didn't create an issue here in QUnit yet, but this is essentially the implied dependency for jquery/testswarm#156 that is now explicit.

We want to record the performance of each test execution and make it available through the logging API (for TestSwarm in this case), so that we can see the performance of of tests and modules over time (also depends on jquery/testswarm#183). Then we'll have reports like these for QUnit tests suits for builds over time:

And of course in QUnit itself we can display times as well (which is what you're asking for here).

gibson042 added a commit to gibson042/qunit that referenced this issue Nov 3, 2012
@gibson042
Fix qunitjs#344: capture and show test duration
804bb44
@gibson042 gibson042 mentioned this issue Nov 15, 2012
Closed
@jzaefferer jzaefferer mentioned this issue Jan 20, 2013
Closed
@jzaefferer jzaefferer mentioned this issue Jan 3, 2014
Closed
leobalter added a commit that referenced this issue Aug 25, 2014
@leobalter
Test: Removes unreacheable code
435a1dd 
The body of this check will never run, since an exception thrown
in the run() method, while notrycatch is set, will prevent the
teardown() from ever running. We're therefore removing the
entire check.

Ref #344
Ref #345
@Krinkle Krinkle mentioned this issue Aug 8, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type: Enhancement New idea or feature request.
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Issue #344 - Capture and show test duration gibson042/qunit
3 participants
@jzaefferer @Krinkle @gibson042