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.

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

DEV: Print usedJSHeapSize to the console after QUnit run #14462

Merged
merged 1 commit into from Sep 28, 2021
Merged

Conversation

@davidtaylorhq
Copy link
Member

@davidtaylorhq davidtaylorhq commented Sep 28, 2021

This is console.log'd to the browser console. run-qunit will print this to stdout. testem will not, so a custom reporter is implemented to print this message.

The --enable-precise-memory-info is added so that chrome provides high-resolution memory information. This API is not supported by firefox. The logic will degrade gracefully.

TestEm output:

...
Built project successfully. Stored in "/var/folders/c7/3jzsz23s16l3_jtzrttkxwfw0000gn/T/tests-dist-2021828-53762-zyrvye.43hq".

Used JS Heap Size: 0.080GB

1..5
# tests 5
# pass  5
# skip  0
# todo  0
# fail  0

# ok
✨  Done in 21.07s.

Run-qunit output:

...
↪ Integration | Component | Widget | discourse-poll-option::multi, selected [✔]

Used JS Heap Size: 0.232GB

Slowest tests
----------------------------------------------
...
This is `console.log`'d to the browser console. run-qunit will print this to stdout. testem will not, so a custom reporter is implemented to print this message.

The `--enable-precise-memory-info` is added so that chrome provides high-resolution memory information. This API is not supported by firefox. The logic will degrade gracefully.
CvX
CvX approved these changes Sep 28, 2021
@davidtaylorhq davidtaylorhq merged commit 4fa296c into main Sep 28, 2021
10 of 11 checks passed
@davidtaylorhq davidtaylorhq deleted the qunit-memory branch Sep 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants