wesj, Thanks for posting about this -- it's great stuff.
On 13-11-08 1:17 PM, Wesley Johnston wrote:
A few weeks ago, I landed a new capability to the testing framework to make it easier to write tests where you need chrome Javascript to cause changes in the Native UI. For instance, my initial goal was to use this to test the nsIPromptService. margaret has also used it to test the new Home banner API. Its in some ways a much less polished version of the JavscriptTest framework nalexander wrote. Nick's stuff is great if you're just testing some JS. This is helpful if you've got chrome JS that will trigger/interact with Java UI.
If I understand correctly, we could implement the Javascript testing pieces I wrote with roboextender. Is this correct?
It's not clear we'd want to do that, but in general, the more individual testing frameworks we build, the worse off we are. For example, we're going to want the framework pieces I landed for testing Javascript in the roboextender world pretty quickly, I imagine.
One reason we might not want to is that the Javascript test file is served via the mochitest server, which means you don't need to touch the device to update the test. (This means that building certain types of tests is *really* fast.)
Are there other advantages or disadvantages to each suite? Best, Nick _______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
