mozmill vs mochitest
Tomas Pelka
I'm trying to understand mozmill. Why do we have two different
frameworks/suites mozmill and mochitest? I know that mochitest is in
tree and it require recompile Firefox every time somebody want to
use/run it, mozmill don't. But it is really huge. If I understand it
correctly mochitest is more like blackbox testing tool, right?
On the other hand mozmill is from my point of view more like whitebox
testing tool. Am I right?
What is the relation of mozmill and mochitest?
I saw some failures in mozmill tests, do you mozilla guys have some how
to debug mozmill test cases?
Thank you all for your comments.
--
Tomas Pelka
Key fingerprint = 06C0 23C6 9EB7 0761 9807 65F4 7F6F 7EAB 496B 28AA
see http://www.gpg.cz/
Geo Mealer
Mochitest is the white-box oriented testsuite and Mozmill is the black/gray-box oriented test suite. More specifically, mochitest is mostly used by the developers to build unit tests, and Mozmill is mostly used by the QA team to build end-to-end regression tests.
The debugging features of Mozmill aren't particularly well-developed. We debug by using dump() to output to command line, or controller.window.alert() to pause execution with a modal dialog, as well as simply by watching the tests execute.
Geo
--
Geo Mealer
gme...@mozilla.com
Hello,
--
Tomas Pelka
--
You received this message because you are subscribed to the Google Groups "MozMill Developers" group.
To post to this group, send email to mozmi...@googlegroups.com.
To unsubscribe from this group, send email to mozmill-dev...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mozmill-dev?hl=en.
Clint Talbert
a browser, it really doesn't make sense to use it.
Mozmill also has a few other interesting features like a common way to
share modules among tests, ability to restart the application under test
between tests, some level of record/replay testing, etc. Mozmill has an
API that attempts to make it easier to write the tests without digging
through the internals of interfaces to make things happen. We're going
to be simplifying that API in 2.0 as well to make it even easier and
align more with selenium 2.0's API which more people will be familiar
with, so it won't be a large jump for folks to start writing Mozmill tests.
Clint
PS Sorry about not responding to this group earlier, my email client has
not been checking this folder for messages and it appeared to be "READ". :(
Tomas Pelka
--
Tomas Pelka
Henrik Skupin
> Mozmill also has a few other interesting features like a common way to
> share modules among tests, ability to restart the application under test
> between tests, some level of record/replay testing, etc. Mozmill has an
> API that attempts to make it easier to write the tests without digging
Oh and something which hasn't been said yet:
In case of our Firefox tests, all of them are executable even in
localized builds. Mochitest would have this capability but nearly all
the tests written so far, are only en-US compatible.
Beside the restart tests we have an alive connection between the CLI
process and the application under test and could do a lot of nifty
things on the CLI side by simply sending messages. We don't really use
that feature at the moment, but it will probably come into play once we
want to have access to system dialogs and events.
Further Mozmill can send reports in plain JSON format which we are using
to display results in our dashboard (under construction):
http://mozmill-release.brasstacks.mozilla.com/
--
Henrik Skupin
QA Execution Engineer
Mozilla Corporation