RE: Knowing which tests are in the repository

> >As far as I know we still haven't solved the problem of determining which files in the repository are tests and of what type. As I understand it there have been two serious proposals:

>>a) Use file naming conventions
>>b) Use a manifest

Yes, that's the critical thing. Actually, in our real testing, we use a solution similar to option b), but only the manifest format is xml based. In addition to entry html, type, timeout information, it also track others such as spec_statement coverage, precondition, purpose etc. Although I know some information can be self-contained in test html, right now I don't see a clear agreement yet.
 
Rgds
jwang

Received on Friday, 16 August 2013 01:01:44 UTC