Created attachment 480348 [details] [diff] [review] add xpcshell tests schema-validation currently has some tests, but those need to be run manually. I converted them to xpcshell tests that can be run the usual way from the objdir: TEST_PATH=_tests/xpcshell/extensions/schema-validation/tests/unit make xpcshell-tests This also uncovered some leaks, but I'll look into those another time. The goal behind this is to have automated tests for schema-validation and xforms that can be run every night to discover Gecko changes that affect us faster than it's the case right now and speed up the process of fixing those bugs (while not regressing existing functionality).
Created attachment 481613 [details] [diff] [review] patch v1.1: add xpcshell tests changes in v1.1: take the components out of the build dirs, not out of FINAL_TARGET (it's not there any more with bug 601570). This also removes the need to check for already registered components as they will registered only once.
Comment on attachment 481613 [details] [diff] [review] patch v1.1: add xpcshell tests This is rs.
Attachment #481613 - Flags: review?(Olli.Pettay) → review+
I don't feel myself as a right person to review this. But I think that's ok to land it with Olli's rs only until anybody has objections.
Doron, Aaron: Does this look ok to you? Essentially this patch only automates the existing tests for schema-validation.
Status: NEW → ASSIGNED
AFAICT it looks good. But I don't know much about these shell tests. Can they be run standalone (i.e run easily, outside of a harness)? If not I'd like the old tests to still remain in the tree.
You only need to add --enable-tests when building Mozilla/XForms. Then you can use the command in comment 0 to run the tests. Nothing else needs to be set up or configured first.
If nobody objects I'll commit this tomorrow.
(In reply to comment #7) > If nobody objects I'll commit this tomorrow. You could always fix future comments after the checkin. That's not preferable but it works in general.
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.