[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #5290 [Quality Assurance and Testing]: Collect+write test pages for JavaScript hooks
#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):
Okay, here we go. I created some unit tests using Mozmill
(https://developer.mozilla.org/en/Mozmill/) which I am going to attach in
a second (yes, the current hooks are indeed not working properly if local
files are loaded...). I'd further propose to use Mozmill for other Gecko
based products as well (you know, new browsers and such kind of stuff ;)
). We could use it even for Torbirdy testing (which is not possible with
Mochitest) and it allows us to test everything reachable by a XPCOM
component. Thus, if there is ever need to write C++ unit tests that is
kept to a minimum, I assume.
The .zip file I'll attach contains a runTests shell script where you have
to enter your Torbrowser path manually in order to get the tests running
(you could also test just the Torbutton xpi which just needs different
parameters) (not very convenient yet).
I plan to convert Gregory Fleischer's and my own tests to Mozmill tests
step by step as well depending on available spare time.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5290#comment:9>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs