#5290: Collect+write test pages for JavaScript hooks
-------------------------------------------+--------------------------------
Reporter: mikeperry | Owner: cypherpunks
Type: task | Status: new
Priority: major | Milestone: TorBrowserBundle
2.3.x-stable
Component: Quality Assurance and Testing | Version:
Keywords: | Parent: #5292
Points: | Actualpoints:
-------------------------------------------+--------------------------------
Comment(by gk):
Replying to [comment:17 mikeperry]:
> The question remains as to how to actually use these in production. It
probably requires a dedicated person to create some kind of automation for
them.
Well, I don't think there is much effort needed here. The only things that
are required are IMO installing Mozmill on the build machines (which is a
one-time investment) and then a new target in the Makefile that builds the
browser which runs Mozmill with the browser executable, the profile
directory and the test directory as arguments. But on the other hand I
don't know how your build infrastructure is working. So, maybe there is
really more to it I am currently not aware of. And, yes, integrating these
tests into Mozilla's existing testing frameworks or adding Mozmill to the
ones already delivered with Firefox could indeed be time-consuming (if
that road is preferred).
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5290#comment:18>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
