• Compliance to requirements (unit tests)
• Which optional statements are used (generate data guide and see which parts are used)
• How were abstract contexts used (how was AgreementInitiator represented? which guarantees were realized? were there any problems modeling something with WS-Agreement?)

Ideas for Unit Tests by Dominic

The following sections describe ideas for unit tests. Each unit test is assigned the corresponding section number of WS-Agreement.

Each unit test consists of a set of preconditions and the actual test. The outcome can be fulfilled, violated, or n/a (in case the precondition is not met).

4 Agreement Structure

Each agreement has a /wsag:Agreement/wsag:AgreementContext.

The /wsag:Terms contain one or more service description terms

4.1 Agreement Context

If an agreement is derived from a template, the /wsag:Context/wsag:TemplateId must be set

4.2 Agreement Terms

4.2.1 Term Types

4.2.2 Term Compositor Structure

4.2.3 Service Description Terms

4.2.3.1 Service Description Term Structure

Each SDT has a /wsag:ServiceDescriptionTerm/@wsag:Name

Each SDT has a /wsag:ServiceDescriptionTerm/@wsag:ServiceName

Descriptions of usage

4.1 Agreement Context

How are agreement parties represented? Did WS-Agreement provide sufficient support for what was required?

4.2.3.1 Service Description Term Structure

How are SDTs used? Did WS-Agreement provide sufficient support for what was required?