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

RE: SURVEY: Test case naming / Now VOTE

From: Arnold, Curt <Curt.Arnold@hyprotech.com>
Date: Thu, 23 Aug 2001 15:59:49 -0600
Message-ID: <70E215722F6AD511820A000103D141D40AA509@thor.aeathtl.com>
To: "'www-dom-ts@w3.org'" <www-dom-ts@w3.org>
> From: Joseph Kesselman [mailto:keshlam@us.ibm.com] 
> Restatement: It could be dangerous to _rely_ on 
> mixed case _file_ names. 
> If we're willing to accept that the test name may 
> not be case-identical to the filename, and can design 
> the tools to cope(*) with that...

I was thinking of the case where the tests were in the CVS repository with MixedCaseNames and were coerced to lowercase within NIST resulting in intended modifications never committed or tests
differing only by capitalization got into the repository.

Having the filenames and the case names out of synch even by case would complicate the build since the Ant <style> task would create .java files with the same capitalization as the test and if the
/test/@name was not consistent the javac step would fail.

If the NIST infrastructure is prone to force file names to lower case, it just seems more expedient to preempt it.  I prefer not to cope, but we won't get into that.

After the little " " directory debacle and previous capitalization nightmares with CVS, I'm just a little paranoid.
Received on Thursday, 23 August 2001 18:17:35 UTC

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