Closed Bug 762744 Opened 12 years ago Closed 9 years ago

Add support for webapp run time mini-mochitest suite


(Release Engineering :: General, defect, P3)

Windows 7


(Not tracked)



(Reporter: cmtalbert, Unassigned)



(Whiteboard: [unittests][try])

Bug 733631 is building a unittest system for webapps. The code is based on mochitest, so as far as buildbot is concerned this is adding two more steps calling mochitest's file with different arguments.

They are still ensuring the tests work properly, but you should be able to use the following command lines on Windows, Linux and Mac OS's. (Note, there is no mobile support for this at this time).

= webapps Content test =
python mochitest/ --appname=<appname> --utility-path=bin --extra-profile-file=bin/plugins --certificate-path=certs --autorun --close-when-done --console-level=INFO --symbols-path=<symbol_path> --webapprt-content

Use the normal content mochitest log parser for the webapp content tests in order to determine pass/fail status.

= webapps Chrome test =
python mochitest/ --appname=<appname> --utility-path=bin --extra-profile-file=bin/plugins --certificate-path=certs --autorun --close-when-done --console-level=INFO --symbols-path=<symbol_path> --webapprt-chrome

Use the normal browser-chrome mochitest log parser for the webapp chrome tests in order to determine their pass/fail status.

= Trees =
We need these tests on the following trees:
* Mozilla-central
* Mozilla-inbound
* Try

= Further Changes to downstream tools =
Once we have buildbot running these jobs, we'll need to make the corresponding changes to tbpl, and orange factor's log parser to accept the new test framework. Edmorley and Jgriffin I'll let both of you file the corresponding bugs for that work. Armenzg, we'll also need to modify the try chooser to be able to accept these tests and conditionally turn them on/off.
I think we should probably just stick these into mochitest-other.
(In reply to Ted Mielczarek [:ted] from comment #1)
> I think we should probably just stick these into mochitest-other.

If we stick them there, we get orange factor and TBPL support for free!
Hey guys, what's the status here?  Let me know if I can help.  A few things:

* These tests only work on OS X for now.  Bug 770771 and bug
  770772 track Windows and Linux.
* This probably goes without saying, but I'd like to do some
  realistic trial runs before they're turned on "for real" to
  make sure they actually work in the buildbot environment.
* The arguments have changed a little since this bug
  was filed.  See the webapprt-test-{content,chrome} targets for
  current syntax:
Depends on: 770771, 770772
Catlee, what would it take to get this onto try? That's really all we need here in the beginning.
not too bad, I don't think...first guess would be to add it here:
Priority: -- → P3
Whiteboard: [unittests][try]
Product: → Release Engineering
See Also: → 920569
Still wanted?
Flags: needinfo?(jgriffin)
This has already been done actually.
Closed: 9 years ago
Flags: needinfo?(jgriffin)
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.