OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tag-discuss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [tag-discuss] Re: Test case metadata is not in scope (was: Re: Reasonsto wait...)


Jacques responded to my message that delineated three roles and whether 
they are producers and consumers of TAs. To summarize:
I. People in the documentation (spec-writing) role would produce TAs.
II. People in the test-writing (and testing) roles would consume TAs.
III. People in the software/system development roles MAY consume TAs, if 
there were tooling to do so.

JD>Are we talking of gathering all this in a kind of "memorandum of 
understanding" document, authored by people on this list, that provides 
some background to potential TC members, and that may be referred to by 
the charter?

I wasn't thinking of that, but I see no problem if others want to.

Regarding Role I...
JD>Suggest to replace " documentation-type people" with "domain experts".
That certainly changes the connotation. I think the role is more about 
communication skills than about domain expertise. I am suggesting that the 
people who currently write our specs, which are very precise and intended 
to be testable, would apply their documentation skills more deeply to 
write the TAs.

Regarding Role II...
DM>>Some of them also use test case metadata, either in portable
>>standalone files (e.g., XQuery Test Suite) or managed by a tool such
>>as Rational TestManager. These people are the ones who write test
>>case metadata, and they are doing so without standards.
>
JD>do we mean: "These people are the ones who need test case metadata,
>and in the absence of standards they usually write their own."

I think some need it, but not necessarily all. When test cases are shared 
across several test labs, as in the case of conformance testing for 
OASIS/W3C/OMG/etc. specs, the need for test case metadata becomes much 
stronger. Putting the test case data in XML promotes platform agility of 
the test suite. The nature of the "need" depends on the tools and 
practices of the particular test lab.

A subsidiary question is how many test labs need (or would use, at least) 
pointers to TAs in their test case metadata. Once again, I think that 
depends on tools.
.................David Marston


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]