On Wednesday, 10 October 2012 03:51:23 UTC+2, Tony Chung wrote: > Hi, > > > > Our current smoketests do not rigorously define the quality of performance > and stability of the builds. They mainly focus on functional regressions. > Given the builds have are still crashy, lagging performance, and reboots > randomly, please share your thoughts on how can improve the build quality. > > > > * What factors define stability to you? How would you measure it? (there is > crash reporting, but the crash signatures are not hooked up to socorro yet) > > * What factors define performance to you? How would you measure it? (eg. > Number of phone reboots? App startup time?) > > > > Note: The current smoketests do track the # of reboots and # of crashes > within a testrun. > > > > If there are tools and tips that you know would help, please do share. > > > > Thanks, > > > > Tony > > Mozilla QA
* What factors define stability to you? --> Ability to have a huge uptime & a yet stable system (eg my Android phone got 3000 hours uptime, still running, no memory issue) --> Ability to recover transparently after an app crash (on B2GD/LNX64, i got a lot of zombie process issue) *How would you measure it? (there is crash reporting, but the crash signatures are not hooked up to socorro yet) --> Uptime, numbers of crashs * What factors define performance to you? --> Reactiveness, FPS, multitasking *How would you measure it? (eg. Number of phone reboots? App startup time?) --> Number of kernel threads or number of process ? Just my 2 cents _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
