Open Bug 1066158 Opened 10 years ago Updated 2 years ago

Running (and rerunning) single tests in the full-up harness is pretty slow

Categories

(Testing :: Mochitest, defect)

Product:
Testing
Component:
Mochitest
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

People

(Reporter: bzbarsky, Unassigned)

Details

I added some performance.now() logging at various strategic points in TestRunner.js, setup.js, and server.js where it spits out the HTML, with the goal of seeing what we spend time on before starting to load the actual test in the iframe.  Some numbers, based on running 5 or 6 times:

Initial test startup:

* Time from load start to running <script> at the beginning of the harness page
  <head>:  ~1200ms
* Time from that to onload for harness page running: ~1300ms 
* Time from that to fetchManifest finishing and calling hookupTests: ~160ms
* Time from that to entering _makeIframe in TestRunner.js: ~20ms
* Time waiting for the focus setTimeout _makeIframe does: 1000-3000ms (though
    there was only one retry call in all cases; we just didn't make it back to
    the event loop for an extra 0-2s for some reason)

Test reload via hitting enter in URL bar:

* Time from load start to running <script> at the beginning of the harness page
  <head>:  ~450ms
* Time from that to onload for harness page running: ~600ms 
* Time from that to fetchManifest finishing and calling hookupTests: ~160ms
* Time from that to entering _makeIframe in TestRunner.js: ~20ms
* Time waiting for the focus setTimeout _makeIframe does: ~1000ms

So summary: Really slow load of the harness page itself, and silly 1s focus timeout...
(In reply to Boris Zbarsky [:bz] from comment #0)
> So summary: Really slow load of the harness page itself, and silly 1s focus
> timeout...

That's done here: http://mxr.mozilla.org/mozilla-central/source/testing/mochitest/tests/SimpleTest/TestRunner.js#484

I think it can be removed.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.