sca-assembly message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [sca-assembly] Which Normative Statements are Covered by the AssemblyTest Suite?
- From: Mike Edwards <mike_edwards@uk.ibm.com>
- To: sca-assembly@lists.oasis-open.org
- Date: Fri, 11 Mar 2011 08:03:05 +0000
Folks,
Comments inline
Yours, Mike
|
|
Dr Mike Edwards
| Mail Point 137, Hursley
Park
|
|
STSM
| Winchester, Hants SO21
2JN
|
SCA & Services
Standards
| United Kingdom
|
Co-Chair OASIS SCA
Assembly TC
|
|
|
IBM Software Group
|
|
|
Phone:
| +44-1962 818014
|
|
|
Mobile:
| +44-7802-467431 (274097)
|
|
|
e-mail:
| mike_edwards@uk.ibm.com
|
|
|
|
|
From:
| Anish Karmarkar <Anish.Karmarkar@oracle.com>
|
To:
| sca-assembly@lists.oasis-open.org
|
Date:
| 11/03/2011 00:33
|
Subject:
| Re: [sca-assembly] Which Normative Statements
are Covered by the Assembly Test Suite? |
On 3/10/2011 10:16 AM, Mike Edwards wrote:
>
> Martin,
>
> ASM40012 requires an implementation type that uses componentType side
> files (untestable in general)
True. But should be tested by the c/c++ testsuite, which does use CTs.
I see this similar to the wiredByImpl feature -- untestable in general
but the BPEL testsuite should test it.
Personally, I'm happy if a feature (any feature) is tested by at least
one of the SCA testsuites.
<mje>
I'd be grateful if you
could check with the folks writing those test suites
</mje>
> ASM50044 is basically untestable
Can you elaborate on this, please?
"When a property has multiple values set, all the values MUST be
contained within a single property element. [ASM50044]"
I can think of two tests for this:
a) positive: set a multi-valued property using a single property
element. eg:
<property name="currency">
<value>EUR</value>
<value>USD</value>
</property>
(I suspect we already have something like this, but haven't checked)
b) negative: set the same multi-valued property using two property
elements. eg:
<component ...>
...
<property name="currency">
<value>EUR</value>
</property>
<property name="currency">
<value>USD</value>
</property>
...
</component>
<mje>
There is a test like that
BUT it is really testing for a different normative statement - the
one that disallows 2 <property/>
elements with the same value for @name....
Hence "untestable".
Unless you want to claim that the @name testcase also tests this
one too....
</mje>
> ASM12013 relates to deployment behaviour (which takes alternative
forms)
I agree. But that raises the question:
Should we get rid of one of the MUSTs in there. It seems like it is
listing all possible things that an implementation can do. Which is a
nice thing to have, but doesn't have to have a 2119 keyword.
> ASM12028 relates to a feature that is optional - ie
> sca-contribution-generate.xml (even though the behaviour is mandated
if
> you do have one of these)
>
Right. Neither is sca-contribution.xml required to be there inside a
contribution.
But this feature isn't optional for the runtime. Since these are tests
for the *runtime*, I don't see why this won't be tested. In fact,
ASM12026 would require this to be tested as well.
<mje>
Umm, the sca-contribution-generated.xml
is supposed to be created only as part of the
deployment process, I believe.
If it is not so created, what is the value of any testcase?
Since THAT function is
optional, I don't see the value of a testcase.
</mje>
-Anish
--
> ASM60024 is tested by ASM_6016_TestCase
> ASM80003 is tested by ASM_8002_TestCase
> ASM12015 requires a (non standard) configuration update API - it was
> missed from the list below.
>
> Yours, Mike
> ------------------------------------------------------------------------
> Dr Mike Edwards
Mail Point 137, Hursley Park
> STSM
Winchester, Hants SO21 2JN
> SCA & Services Standards
United Kingdom
> Co-Chair OASIS SCA Assembly TC
> IBM Software Group
> Phone:
+44-1962 818014
> Mobile:
+44-7802-467431 (274097)
> e-mail:
mike_edwards@uk.ibm.com
>
>
>
>
>
> From:
Martin Chapman <MARTIN.CHAPMAN@ORACLE.COM>
> To:
Mike Edwards/UK/IBM@IBMGB, OASIS Assembly
> <sca-assembly@lists.oasis-open.org>
> Date:
10/03/2011 16:47
> Subject:
RE: [sca-assembly] Which Normative Statements are
Covered by
> the Assembly Test Suite?
>
>
> ------------------------------------------------------------------------
>
>
>
> Mike,
> I was just going through the list below and have the following questions.
> The following are not optional in the specification so why are they
not
> tested: ASM40012, ASM50044, ASM12013, ASM12028?
> The following are not on the list below but I can’t see tests in
the
> test suite either, why is this: ASM60024, ASM80003, ASM12015?
> Cheers,
> Martin.
>
> *From:* Mike Edwards [mailto:mike_edwards@uk.ibm.com]
*
> Sent:* 02 March 2011 10:52*
> To:* OASIS Assembly*
> Subject:* [sca-assembly] Which Normative Statements are Covered by
the
> Assembly Test Suite?
>
>
> Folks,
>
> This email is in response to the question posed by Eric Johnson in
one!
> of his emails - which of the Assembly spec normative
> statements are covered by the test suite?
>
> It is actually simpler to say: the Assembly test suite covers all
of the
> spec normative statements EXCEPT for the following:
>
> ASM40001
> ASM40006
> ASM40012
>
> ASM50006 *[1]
> ASM50010
> ASM50013
> ASM50016 *[1]
> ASM50044
>
> ASM60002 *[2]
> ASM60035
> ASM60036
>
> ASM80002 *[2]
> ASM80005 *[2]
>
> ASM12001
> ASM12002 *[3]
> ASM12007 *[3]
> ASM12008 *[3]
> ASM12013 *[3]
> ASM12014 *[3]
> ASM12016 *[3]
> ASM12017 *[3]
> ASM12018 *[3]
> ASM12020 *[3]
> ASM12028
> ASM12029 *[3]
> ASM12030 *[3]
>
> ASM14001 *[3]
> ASM14002 *[3]
> ASM14003 *[2]
> ASM14004 *[3]
>
>
>
> [1] This statement is actually tested by the Web Service binding test
suite
> [2] This statement is actually tested by the Java POJO test suite
> [3] Not tested as function is optional
>
> Please note that it was a deliberate decision not to test function
that
> was optional and that this decision did not raise comments during
the
> review process.
>
> Some function requires features that are specific to certain
> implementation types or to some binding types and this led to the
> testing being delegated to
> the test suite related to those implementation types / binding types
in
> the interests of avoiding the Assembly test suite being tied to specific
> implementation
> & binding technologies.
>
> Yours, Mike
>
> ------------------------------------------------------------------------
> Dr Mike Edwards
Mail Point 146, Hursley Park
> STSM
Winchester, Hants SO21 2JN
> SCA & Services Standards
United Kingdom
> Co-Chair OASIS SCA Assembly TC
> IBM Software Group
> Phone:
+44-1962 818014
> Mobile:
+44-7802-467431 (274097)
> e-mail:
mike_edwards@uk.ibm.com
>
>
>
>
>
> ------------------------------------------------------------------------
>
> /Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with
number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
PO6 3AU/
>
>
>
>
> ---------------------------------------------------------------------
> 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:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>
>
>
> ------------------------------------------------------------------------
>
> /
> /
>
> /Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with
number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
PO6 3AU/
>
>
>
>
>
>
---------------------------------------------------------------------
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:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]