CloudServices/Sync/FxSync/Crossweave2: Difference between revisions

m
 
(4 intermediate revisions by 2 users not shown)
Line 37: Line 37:
** memory usage (from <code>nsIMemoryReporterManager</code>)
** memory usage (from <code>nsIMemoryReporterManager</code>)
** GC operations (setting <code>javascript.options.mem.log</code> and grepping the error console for the corresponding log messages would already help; better even use build with <code>--enable-gctimer</code>)
** GC operations (setting <code>javascript.options.mem.log</code> and grepping the error console for the corresponding log messages would already help; better even use build with <code>--enable-gctimer</code>)
** GC + CC graphs: {{bug|680482}}, https://github.com/amccreight/heapgraph
** JITing (what's trace or method JITed and more importantly, what isn't? no instrumentation yet?!?)
** JITing (what's trace or method JITed and more importantly, what isn't? no instrumentation yet?!?)
** object allocations (no instrumentation yet?!?)
** object allocations (no instrumentation yet?!?)
Line 45: Line 46:
* support fuzz consistency tests
* support fuzz consistency tests
* more operations (restore from bookmarks to test wipe, for example)
* more operations (restore from bookmarks to test wipe, for example)
= QA desires =
* port mozmill API on top of TPS, so we can have tests against client side setup wizard work
* create headless TPS, and create javascript/python tests against XPShell
* support TPS against a fully integrated test staging server, with configurable settings (eg. disabling Captcha)
* Support for running on mobile?.  Start with porting and running against desktop fennec
canmove, Confirmed users
1,173

edits