Closed
Bug 860790
Opened 11 years ago
Closed 11 years ago
Add an eideticker page load test which attempts to load a page from an already started browser
Categories
(Testing Graveyard :: Eideticker, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: wlach, Assigned: wlach)
Details
The current startup tests measure a useful metric, but loading a page inside an already open browser is (obviously) a common use case as well. It would also be useful for isolating how many of our problems in bug 857359 are due to slow startup/initialization vs. problems when the browser is already loaded. This bug will track adding support to that in eideticker, as well as the addition of that to the dashboard.
Assignee | ||
Updated•11 years ago
|
QA Contact: wlachance
Assignee | ||
Comment 1•11 years ago
|
||
Landed support for this: https://github.com/mozilla/eideticker/commit/d5073f6999e95e6a4ac8233b3f572005c86fd5a1 https://github.com/mozilla/eideticker/commit/84e9d0ce0ce57fad177acbb23cc724cf0da6805a The results seem to show that we're seeing really slow page loads, even after startup: http://eideticker.wrla.ch/#/samsung-gn/nytimes-load-poststartup/timetostableframe
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → wlachance
Updated•7 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•