El 04/01/13 04:29, "Jonas Sicking" <[email protected]> escribió:
>The flow right now when developing mochitest for B2G is as follows: > >1. Write test >2. Run mochitest in simulator >3. See test failures >4. Edit test >5. Go back to step 2. > >The problem here is that step 2 takes a very long time. It requires >starting both gecko and the emulator. AFAIK, and concerning the Gaia unit tests, that is not needed if you start B2G with a debug profile which basically loads the Web resources through HTTP instead of the app:// package. However the issue is that that test-agent app is not usable to be run from B2G desktop as the UI is horrible and does not allow to find the test you want to run >And it runs gecko under an ARM >emulator. The turnaround time after having edited a test is several >minutes. Which slows down test development quite dramatically when you >have to wait several minutes for every missing parenthesis. > >This is actually a poor enough experience that unless we can figure >out hacks to work around this, it probably makes sense to give up on >this and put Bobby on writing code rather than tests. > >Another problem with the current setup is that once you run into a >bug, you are forced to debug through the emulator rather than simply >attaching to a normal desktop gecko process and use the same tools >that we have years of polish and experience. I think that would be useful for platform code debugging > >As far as I understand it writing marionette tests have all the same >problems. And would meant that we couldn't reuse the tests for Fennec >and Desktop once these APIs work there too. Additionally marionette >tests require writing mixed javascript and python and generally >requires doing more complex things than mochitests currently do, >especially for platform developers who are mostly experienced in >javascript as well as the APIs they are testing. I'm definitely not >complaining about marionette. It's solving a much more complex set of >problems than mochitest is. But I don't think we can or should push >them as an alternative to mochitest. Probably I don't understand the problem as a whole but wouldn't be sufficient to have the capability to remotely dispatch events to the pages loaded in the phone, through a WebSocket to simulate user events? > >Especially great would be if we make it possible to have the Desktop >Firefox test writing flow where reloading a test is possible and you >don't have to restart the whole test suite. > >/ Jonas >_______________________________________________ >dev-b2g mailing list >[email protected] >https://lists.mozilla.org/listinfo/dev-b2g > ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
