Closed Bug 459236 Opened 16 years ago Closed 16 years ago

Why are "postMessage_chrome" test files split between two directories ?

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
trivial

Tracking

()

RESOLVED INVALID

People

(Reporter: sgautherie, Unassigned)

References

Details

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1b2pre) Gecko/20081009 SeaMonkey/2.0a2pre] (home, optim default) (W2Ksp4)

I noticed that
<objdir>\mozilla\_tests\testing\mochitest\chrome\dom\tests\mochitest\whatwg\test_postMessage_chrome.html
needs
<objdir>\mozilla\_tests\testing\mochitest\tests\dom\tests\mochitest\whatwg\postMessage_chrome_helper.html

The two files are copied from
<src>\dom\tests\mochitest\whatwg\*
See
http://mxr.mozilla.org/mozilla-central/source/dom/tests/mochitest/whatwg/Makefile.in?mark=63,82#47

I find it odd that the "chrome" tests can't be run without the "mochitest" tests directory being present.
I would expect the two files to be in the same (test) directory (= one or the other)...
I don't understand what the problem is here -- can you explain more clearly?  I dumped all the postMessage tests in one location and didn't particularly care to differentiate the various flavors, to be honest, if that's the gist of the complaint.
While working on finding out which tests were leaking, I noticed that I couldn't fulling remove one directory when I was actually narrowing the tests in the other directory.

The two files are together in the src tree, but not in the objdir tree.
No big deal, but I thought that maybe this was not mandatory and could be improved.
(_Maybe_ even by duplicating a file, if it's needed in both objdir directories !?)
Er, oh.  What happens here is that _CHROME_FILES are copied to a location where they can be mapped to a chrome: URL, while _TEST_FILES are copied to a location where they can be served by the dizzying array of HTTP servers and hosts the harness provides.  The test requires running from a chrome: location and needs to talk to a page running from a non-chrome: location, so the former must be in _C_F and the latter must be in _T_F.  The name/misnomer _TEST_FILES is a slight anachronism from the time when when ran tests from HTTP simply because it more faithfully emulated the real web, not because it was a necessary.  Make sense?  I'm now pretty sure this is INVA.
R.Invalid then
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Component: DOM: Mozilla Extensions → DOM
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.