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


Help: OASIS Mailing Lists Help | MarkMail Help

sca-j message

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

Subject: Re: [sca-j] [Issue 227] SCA-J POJO Component Implementation v1.1 TestCasesVersion 1.0

There are two points in this issue.  The first needs to be addressed while the second probably does not but I would like Martin's view.

For the first point  we should note that in both the Assembly and Policy test case documents in the Related Work section of the front matter there is a link to the zip file with all the test artifacts.  For example, from Assembly:

The Test Suite artifacts relating to this document can be found here:

The corresponding text and link is missing in the POJO CI Test case document (and for that matter the CAA test case document as well).

On the second point, both the test assertions and the test case document rise above the level of what I would consider appropriate for a Committee Note.  While they do not in and of themselves define any normative statements, they serve to define the expected behavior of any implementation claiming to satisfy the normative statements in the specification and as such are parallel documents with equal importance to the specification and as such the appropriate template is the specification template and not the note template.  Another way to think of this is that the test assertions and test cases are extension of the specification vs. examples or clarifications.

As an editorial observation, TC admin made an error in adding the Citation Format section of the front matter.  It contains a link to the spec, not the test case document.  You can only see this in the version in the OASIS repository (http://docs.oasis-open.org/opencsa/sca-j/sca-j-pojo-ci-1.1-testcases-1.0-csd01.pdf), not the version in Kavi.

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect
WW Center of Excellence for Enterprise Systems & Banking Center of Excellence Application Integration Architect

Research Triangle Park,  NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com

From:        Anish Karmarkar <Anish.Karmarkar@oracle.com>
To:        Patrick Durusau <patrick@durusau.net>
Cc:        sca-j-comment@lists.oasis-open.org, OASIS Java <sca-j@lists.oasis-open.org>
Date:        12/27/2010 05:26 PM
Subject:        [sca-j] [Issue 227] SCA-J POJO Component Implementation v1.1 TestCases Version 1.0

Thanks for your comments.
This is filed as issue JAVA-227 [1] and will be considered by the SCA-J
TC on one of their future calls after the holiday break.



On 12/23/2010 6:20 PM, Patrick Durusau wrote:
> 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

To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:

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