On 10/26/13 10:22 PM, Caio Lima wrote:
These are my outputs when I'm trying to run gaia-ui-tests on emulator
Gecko console:
http://pastebin.mozilla.org/3340102
Test-runner console:
http://pastebin.mozilla.org/3340125
The path you've specified is not to the Python tests. Try the following
to run all clock tests:
$ gaiatest --address=localhost:2828 --testvars=gaiatest/my_vars.json
--type=b2g gaiatest/tests/functional/clock/manifest.ini
I've tested with the --emulator flag either;
Gecko Console:
http://pastebin.mozilla.org/3340127
Test-runner console:
http://pastebin.mozilla.org/3340126
This looks familiar and may be something I've encountered while working
on bug 916368, however other work has recently taken priority so I would
have to revisit that to get you a fix or suggest a workaround. I hope to
do that sometime this week. For now you should be able to start the
emulator before kicking off the tests.
BTW, I was dicussing with Julien about the Javascript-based
Integration tests, as you can see on
https://bugzilla.mozilla.org/show_bug.cgi?id=930556#c5
I agree with his comment about using Javascript tests, because It'll
be esier to new gaia developers write more integration tests. So, I
would like to know about the status of marionette-js-runner on
emulator. Is it working? From automation tem point of view, what do
you think about this?
I'm not sure, but I've CC'd James Lal who may be able to answer that.
Dave
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
