Closed
Bug 1358180
Opened 9 years ago
Closed 8 years ago
Add more DAMP tests for the console
Categories
(DevTools :: Console, enhancement, P3)
DevTools
Console
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: nchevobbe, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file, 1 obsolete file)
|
6.03 KB,
patch
|
Details | Diff | Splinter Review |
We should have a DAMP test to check the time the console takes to open when there are some messages in cache.
It would also be nice to see how we perform when we log messages with lots of arguments.
Just FYI, DAMP might not survive the move to GitHub, so you may only get results for the next few months or so. That could still be quite helpful for console, just wanted to make sure you were aware.
| Reporter | ||
Comment 2•9 years ago
|
||
Comment 3•9 years ago
|
||
(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #1)
> Just FYI, DAMP might not survive the move to GitHub, so you may only get
> results for the next few months or so. That could still be quite helpful
> for console, just wanted to make sure you were aware.
Hm, I wonder if in that case we should move these measurements to be something run locally that we can use for perf testing - either in https://dxr.mozilla.org/mozilla-central/source/devtools/client/webconsole/new-console-output/test/chrome/test_render_perf.html or more likely in a mochitest-browser test
Comment 4•9 years ago
|
||
I'll still use this patch for perf testing the html document on try, though
Updated•9 years ago
|
Summary: Add DAMP tests for the console → Add more DAMP tests for the console
Updated•9 years ago
|
Priority: -- → P3
Comment 7•8 years ago
|
||
The new custom page for the console cover various usages of the console (bug 1419328):
https://searchfox.org/mozilla-central/source/testing/talos/talos/tests/devtools/addon/content/pages/custom/console.html#24,30,44
(In reply to Nicolas Chevobbe [:nchevobbe] from comment #0)
> We should have a DAMP test to check the time the console takes to open when
> there are some messages in cache.
The streamlogs + asynclogs being done *after* page load should simulate cached message,
otherwise, the openwithcachedmessages test covers exactly that.
> It would also be nice to see how we perform when we log messages with lots
> of arguments.
The custom page does:
console.log("sync log", i, window, document.body, bigArray);
Is it enough?
window is a significant JS object. Compared to the attached patch, we don't have an array made of objects.
Do you think we can close this bug, or is there some tweaks to be made, still?
Flags: needinfo?(nchevobbe)
| Reporter | ||
Comment 8•8 years ago
|
||
Yes, let's close this, we also have other bugs open for specific test case on DAMP like filter.
Thanks Alex
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(nchevobbe)
Resolution: --- → INVALID
Updated•8 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•