SCA-J POJO Component Implementation v1.1 TestCases Version 1.0

[Patrick Durusau <patrick@durusau.net>]

Greetings!

Comments on behalf of the TAB.

General comment: It was unclear where the Java classes could be found 
that are used in the test assertions. Seems like that would be fairly 
critical to the test cases. Yes?

Test Artifact Organization

read (in part):

> Note that the design of these testcases promotes reuse of artifacts 
> between testcases, so that many testcases share components. For 
> example, components implementing simple invokable services are all 
> implemented using a single parameterized implementation artifact.
> All the test artifacts are contained in a number of Contributions, 
> which are simply filesystem directories which are all peers in the 
> filesystem hierarchy. The names of the directories are the names of 
> the Contributions and the names are significant. The names of 
> Contributions containing implementation type specific artifacts (such 
> as Java classes) are also specially structured to allow for 
> replacement of one type of implementation artifact with another.

Really should have a clear separation between normative and 
non-normative material. Such as starts with "Note that..." is 
non-normative.

In the absence of the Java classes or specification of the purpose of 
those classes, it isn't possible to evaluate the various test cases.

5 Conformance

No conformance clauses? Contrary to OASIS policy.

Hope everyone is having a great holiday season!

Patrick

-- 
Patrick Durusau
patrick@durusau.net
Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau