- From: Dimitris Dimitriadis <dimitris@ontologicon.com>
- Date: Tue, 16 Apr 2002 00:16:12 +0200
- To: bclary@netscape.com (Robert Clary)
- Cc: Curt Arnold <carnold@houston.rr.com>, www-dom-ts@w3.org, Edward Hieatt <edward@jsunit.net>
comment inlined On Tuesday, April 16, 2002, at 12:11 , Robert Clary wrote: > Curt Arnold wrote: >> Another thing that would be useful is a clean-up function that runs >> after >> all the tests have been completed. The existing jsUnit based HTML >> tests >> leave a large number of windows open since they keep unmodified >> documents >> around for potential later use, however there is nothing to hook to >> close >> them all down when the tests are over. My recollection is tearDown() >> fires >> after each test and would not be appropriate, but I could wrong on >> that. > > The caching of unmodified test documents seemed to me to introduce a > great deal of complexity without necessarily adding a corresponding > degree of benefit. However that is the subject of a different > discussion I think. > > It may be possible to do what you want by organizing the tests into > suite of suites and having the final suite perform the cleanup. > > This reminds me however that the Document Loader in jsUnit currently is > limited to a single document at a time. This may be a limitation that > needs to be addressed in the proposed jsUnit. How important is it to > load multiple test documents at the same time in general and in the DOM > TS in particular? > [dd] Am I off track presuming that this could be useful if we utilize the JsUnit TestSuite option? > /bc >
Received on Monday, 15 April 2002 18:19:27 UTC