Title: call Monday July 26
Could not send these comments before (had
email problems):
(will have more to send later)
------------Introduction:
1.1. : totally inappropriate! (an import from
interop test suite spec !!)
Would rather propose: "This
document describes a test framework for automatically running test suites for - but not limited to - ebXML
specifications. The framework includes an architecture design based on components that can be combined
and distributed in different ways, to
accommodate different test harnesses. It also includes an extensible test
scripting language for coding test suites in an executable way. It can
accommodate third-party plug-ins, that would perform advanced verifications for example on message
material (e.g. semantic verification using
rule engine), or that would help build testing material (e.g. digital
signature)."
---------- Section 2:
In 2.1:
- retitle as "Objectives", add two subsections
(2.1.1 "General", and new 2.1.2 "Usage Requirements", to be insrted in Line
258)
- Need bullet lists.
- XMI-based --> XML-based
- add "An objective in specifying this test framework, is that test suites
for
future ebXML versions can be written that will run on all implementations of
this framework."
---------- Section 3:
- section 3.1.1 should be structured as a bullet list.
Jacques
-----Original Message-----
From: Michael Kass
[mailto:]
Sent: Monday, August 09, 2004 9:12
AM
To: 'Jacques Durand'; 'ebXML IIC - main list (E-mail)
(E-mail)'
Subject: [ebxml-iic] Latest Update to Test Framework
posted to IIC Documents site
Jacques and
all,
I posted a revised spec, specifically working on section 7.1 (abstract
representation of workflow using Threads).
I used the 3 use
cases that we have been working on. This section gives a more concrete
meaning to “pass”, “fail” and “undetermined”
using the 3 use cases
as examples.
Modified spec is available at:
http://www.oasis-open.org/apps/org/workgroup/ebxml-iic/documents.php?
Cheers,
Mike
