- From: Arnold, Curt <Curt.Arnold@hyprotech.com>
- Date: Thu, 13 Sep 2001 10:00:49 -0600
- To: "'www-dom-ts@w3.org'" <www-dom-ts@w3.org>
Mary Brady [mailto:mbrady@nist.gov] wrote: >I'm just getting back to working on the DOM Level 2 Core tests -- That is good news. > did we come to some agreement on naming conventions? The general feeling was that over-descriptive test names are a nuisance and MixedCase file names and test names would be preferable. MethodNameXX or PropertyNameXX should be sufficient. If a test can't be keyed to one specific property, then you could name it something like "EventPropagation01.xml". The test matrix should provide much better organization than could be achieved by relying on file names. I would also suggest that assertion ids be made shorter, they only have to be unique within the test. For <assertEquals> that the id of the assertion be either the variable checked or the property that produced the value when possible. Something like: <assertEquals actual="value" expected="expectedValue" id="value"/> For assertDOMException, I would recommend that the id be "throw_" + exception code: <assertDOMException id="throw_INDEX_SIZE_ERR"> <INDEX_SIZE_ERR> ...
Received on Thursday, 13 September 2001 12:03:31 UTC