Before adding a chrome domain for conkeror-test, I'd like to take a step
back and just ask, does this really represent a qualitative improvement to
our unit testing capabilities? What kinds of things does it let us test,
beyond this particular case?
I don't have a strong justification for it, I just thought it was neat.
It gives us a way to refer to local test data. The only other (pretty
weak) instances I can think of are:
* Test html files for automated testing of basic browser navigation.
* A test html file for a page mode. Such a test case is probably not
very useful though, as page modes depend entirely on the vagaries of
changes to web sites out of our control.
* Invoking test cases from anywhere with
conkeror -q -batch -l chrome://conkeror-test/content/simple/keymap.js
(This will need changes to load_rc().)
regards, David
_______________________________________________
Conkeror mailing list
[email protected]
https://www.mozdev.org/mailman/listinfo/conkeror
