- From: Dimitris Dimitriadis <dimitris.dimitriadis@improve.se>
- Date: Wed, 23 May 2001 11:54:39 +0200
- To: "'Arnold, Curt'" <Curt.Arnold@hyprotech.com>, "'www-dom-ts@w3.org'" <www-dom-ts@w3.org>
We were thinking in terms of having one source file per test description and using an outer tag basically to define a suite. This allows us to build different suites that consist of the same tests, if that were needed, as well as supply the test suite with information on how to treat the tests it consists of. I think your proposal as well as the NIST DTD could be used in this way -----Ursprungligt meddelande----- Från: Arnold, Curt [mailto:Curt.Arnold@hyprotech.com] Skickat: den 23 maj 2001 00:32 Till: 'www-dom-ts@w3.org' Ämne: RE: Using RDF to describe DOM tests > From: Dimitris Dimitriadis wrote: > Just a small addition: the test itself will also be > identified by a URI (proper) as it will exist as a separate file. > > A collection of those, ie. a suite, will also be identifiable > by a URI. Using a distinct file for each test does seem to be a better approach that inlining tests into suites since there are distinct sources for the tests and you want independent revision histories, etc. Do you have a particular pattern that you would like to use for the definition of a suite? My current schema reflected the earlier efforts and only supported in-lining of tests in suites and references to externally defined suites.
Received on Wednesday, 23 May 2001 05:55:25 UTC