W3C home > Mailing lists > Public > www-dom-ts@w3.org > August 2001

RE: Distinguishing tests from resources

From: Arnold, Curt <Curt.Arnold@hyprotech.com>
Date: Mon, 13 Aug 2001 08:46:44 -0600
Message-ID: <70E215722F6AD511820A000103D141D40AA4B7@thor.aeathtl.com>
To: "'www-dom-ts@w3.org'" <www-dom-ts@w3.org>
Mary Brady [mailto:mbrady@nist.gov] wrote:

> 1) Is it necessary to keep all files in the same directory 
> to make use of relative URI's?

No.  The current build.xml copies the resource files into the same directory as the generated .class files and the implementation of DOMTestCase.load() resolves URI relative to the location of the
.class file in domunit.jar.  Keeping the resource and test definitions files in the same directory would make the relative URI's valid in the source.

> 2) Why would we change the extension on over 
> 1,000 tests versus changing the extension on 
> just a handful of resource files?

If the tests were already in the CVS, I would agree that this was too much of a disruptive change, hence the desire to resolve it before you add your tests.  The mechanism of changing the extensions
on a file system before committing to the CVS should be trivial (rename *.xml *.domtest and then copy in the resource files for Win32).

I now believe the targetURI attribute is redundant since we can determine the value from the context and additionally the current values can be readily changed (either before or after initial commit)
using a multifile regexp replacement, so I would not let concern about those being out-of-synch hold things up.  If it is trivial (less than 5 minutes) for you to remove both the targetURI and package
attributes before committing, you can do so or you leave them both in and we can ignore them and remove them up later.
Received on Monday, 13 August 2001 10:50:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:03 UTC