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

 


Help: OASIS Mailing Lists Help | MarkMail Help

tag message

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


Subject: Re: [tag] Extended TA model suggestion with cardinalities





Quoting Dave Pawson <dave.pawson@gmail.com>:

> On 22/09/2007, stephen.green@systml.co.uk <stephen.green@systml.co.uk> wrote:
>> Extended TA model suggestion with cardinalities (? where more debatable):
>>
>> 1..1   Test Assertions List or Group
>> <further data here perhaps related to list/group>
>> 0..n   Test Assertion
>> 1..1   Test Assertion ID: <ID>
>> 0..n   Specification requirement
>> 0..1   Specification requirement Cross Reference: <Link>
>> 0..1   Specification requirement quote: <Text>
>
> Last 3 are likely to be alternates?

Not sure about that - it isn't always either/or but sometimes both/and
see SOAP tests collection

>
>
>> 0..?   Item under test: <Text>
>> 0..1   Assertion Description: <Text>


>> 0..1   Comment: <Text>
>
> Assume this is non normative comment by the test designer?

The type of comment I mean is, for example, in SOAP tests where some
spec requirements have corresponding TAs for completeness but those
TAs aren't actually testable so there is a comment in the TA to say so.
Other examples are where the tests do not completely cover the spec item.
So they are probably normative in such cases. The test designer would
use them but it might be the spec and/or TA writer who makes the comments.
Maybe they should be 0..n rather than 0..1

>

-Steve



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