Skip to main content

Choosing test description format

2 replies [Last post]
Joined: 2006-06-28

I noticed that in the samples provided with ME Framework (as well as in recently opened JCK) tests' descriptions formatted in HTML... So I have a couple of questions:

1. What are the reasons for using HTML-format for test descriptions (e.g. xml sounds more reasonable as a source for test descriptions and it's easier to convert from xml to the other JT test description formats)?

2. Is there any code-generation tools for creating HTML-files and converting between different test description formats.

Thanks in advance.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2006-10-12

Hello Evgeny,

the choice of HTML for test descriptions in JCK and JT Harness was mostly historical. Back in 1995/1996 when the first JCK version was designed HTML was chosen as it is a relatively simple and convenient human-readable format.

Many JT Harness test suites are still using HTML format, but there is a flexible finder mechanism which can support a variety of test description formats.
One of the ME Framework samples, SimplestTestSuite, shows how tags in source files can be used for test descriptions:

There are no publicly available tools for HTML test description generation or conversion that I know of. At Sun we are using a variety of internal scripts and tools for this.

thank you,

Joined: 2006-06-28

That's a pity. Tags looks more convenient (and usual) for me. But if would be even more convenient to have a mapping between formats instead of using ChameleonTestFinder or something for reusing tests :-).