424484 - Need way to run mochitests from file://

Status: REOPENED

(Testing :: Mochitest, defect)

Description

[Boris Zbarsky [:bzbarsky]]

Need this to test bug 418356 and bug 402983.  This can be gotten around by using UniversalXPConnect to create/remove the files (in /tmp, say) as part of an http:// test, but that makes the test a lot more confusing.  Ideally we would just have a directory tree running as file:// somewhere and we could point to a particular file in the tree as the testcase.  It's important that it be possible to have the "main" testcase _not_ be at the top of the tree, so we can test accessing ancestors.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Also needed for bug 425201.

Comment 3

[Jeff Walden [:Waldo]]

Moving a bunch of Core :: Testing bugs to Testing :: Mochitest to clear out the former, which is obsolete now that we have more specialized categories for such bugs; filter on the string "MochitestMmMm" to delete all these notifications.

Comment 4

[(not currently active) Ted Mielczarek]

Attachment: non-working proposal

Here's a proposal that would just add file:// tests into the current test runner. Of course, it doesn't work, because http:// content can't link to file:// content, so you get "Error: uncaught exception: [Exception... "Access to restricted URI denied"  code: "1012" nsresult: "0x805303f4 (NS_ERROR_DOM_BAD_URI)"  location: "http://localhost:8888/tests/SimpleTest/TestRunner.js Line: 92"]"

The patch works by just requiring the file tests to be named "test_file_...".

I'm going to file a Caps bug blocking this one to see if we can make that work. If not, the alternative would be to add a whole new method to runtests.py, like --file, which would load the whole harness from a file:// URL.

Comment 5

[Andrew Halberstadt [:ahal]]

Mass closing mochitest bugs that haven't had activity in the past 5 years. Please re-open or file a new bug with modern context if this is still relevant.

Comment 6

[Boris Zbarsky [:bzbarsky]]

This is still relevant.  We need it to be able to write tests for critical security code.  The fact that we haven't bothered to fix the harness to make this possible doesn't mean it doesn't actually need to happen...