On 2015/03/13 7:51, Jonathan Griffin wrote:
The A-Team is embarking on a project to improve the developer experience
when running unittests locally.
Is this about C++ unittests or about mochitests etc.?
If it's the latter, most of my pain points would be around debugging B2G
failures. Similar to what Gijs wrote, in particular I find:
* Running a single test often behaves differently or doesn't work (e.g.
bug 927889 for B2G) so I sometimes edit the mochitest.ini etc. to remove
all the other tests.
* Running mochitests on B2G desktop on Windows (with mach
mochitest-b2g-desktop) seems to size the window to 0x0 for me. (I've
never looked into why but I've just sometimes worked around this by
using setTimeout so I can manually resize the window before the test
continues.)
* No sooner do I fix an intermittent failure on B2G desktop, than one
pops up on B2G emulator which often means a lot of time rebuilding (and
I always have trouble getting mochitests to run on emulator--it worked
for a while, now it doesn't, some marionette error).
* Setting up a custom gaia with a custom gecko and remembering how to
run gaia tests again often takes me a while.
Thanks,
Brian
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
