Auto-tools/Projects/peptest: Difference between revisions

Jump to navigation Jump to search
Line 163: Line 163:
Mozmill doesn't use MessageManager when it interacts with content. This means that it will not work correctly with Electrolysis builds (which is mostly the entire point of Peptests). Mozmill will need to be refactored to use MessageManager and also to stop using the gBrowser object which doesn't exist in mobile Firefox.
Mozmill doesn't use MessageManager when it interacts with content. This means that it will not work correctly with Electrolysis builds (which is mostly the entire point of Peptests). Mozmill will need to be refactored to use MessageManager and also to stop using the gBrowser object which doesn't exist in mobile Firefox.


=== Detailed results ===
=== Integration with SPS ===


Dietrich has written some tools to determine exactly which Javascript calls were unresponsive. This is a very useful tool which should be incorporated into the Peptest harness. More details can be found [http://etherpad.mozilla.com:9000/responsiveness-profiling here]
For each function wrapped in a performAction() call, we should enable the profiler, so we can tell where each action spent its time. We can use [https://developer.mozilla.org/en/Performance/Profiling_with_the_Built-in_Profiler SPS] to this end.  This is filed as [https://bugzilla.mozilla.org/show_bug.cgi?id=706847 bug 706847].
 
I (ahal) would really like someone to own [https://bugzilla.mozilla.org/show_bug.cgi?id=580055 bug 580055], un-bitrot the patch and get it checked in (with ifdefs or something). If you want, I'll even un-bitrot the patch for you :)


=== Buildbot Integration  ===
=== Buildbot Integration  ===
Confirmed users
1,927

edits

Navigation menu