Hi Ken,
Here's the original from the fifth paragraph of 5.4.2 Testing
and the SOA Ecosystem
"...Testing of SOA artifacts for use in the SOA ecosystem differs
from traditional software testing for several
reasons. First, a highly touted benefit of SOA is to enable
unanticipated consumers to make use of
services for unanticipated purposes. Examples of this could include
the consumer using a service for a
result that was not considered the primary one by the provider, or
the service may be used in combination
with other services in a scenario that is different from the one
considered when designing for the initial
target consumer community. It is unlikely that a new consumer will
push the services back to anything
resembling the initial test phase to test the new use, and thus
additional paradigms for testing are
necessary. Some testing may depend on the availability of test
resources made available as a service
outside the initial test community, while some testing is likely to
be done as part of limited use in the
operational setting. The potential responsibilities related to such
"consumer testing" is discussed further
below.
Here's How I would add a subheading:
"... Testing of SOA artifacts for use in the SOA ecosystem differs
from traditional software testing for several
reasons. First, a highly touted benefit of SOA is to enable
unanticipated consumers to make use of
services for unanticipated purposes. Examples of this could include
the consumer using a service for a
result that was not considered the primary one by the provider, or
the service may be used in combination
with other services in a scenario that is different from the one
considered when designing for the initial target consumer community.
5.4.2.1 Continuous & Adaptive Testing
Because it is unlikely that a new consumer will push the services
back to anything resembling the initial test phase to test the new
use, there is a need for additional paradigms for testing, namely
Continuous & Adaptive Testing.. Some testing may depend on the
availability of test resources made available as a service outside
the initial test community, and this is what we refer to as Adaptive
Testing. Meanwhile some testing is likely to be done as part of
limited use in the operational setting.We often think of these as
one-offs, the market has shown thee ability push beyond boundaries
and if we fail to discover these instances and incorporate them into
Continuous Testing, we face the possiblity of failing unexpectedly.
Such Limited uses have the potential for rapid changes. Without the
paradigm of testing continuously by using such novel and possibly
subtle unexpected changes introduced by innovative users we will
encounter difficulties.. The potential responsibilities related to
such "consumer testing" is discussed further below.
On 4/22/2012 5:08 PM, Ken Laskey wrote:
Rex,
I’ve spent considerable quality time
cutting accepted comments into the latest RAF draft. I also
wanted to cut in the revised testing section and to
incorporate your comments there. The simple ones were easy
but there are a few that could use some additional guidance
from you. In the attached spreadsheet, comments rb42-rb44
have augmented responses in blue type in column H. I also
attached the testing draft modified for your other comments.
(I also remember dozens of open ended comments from Boris that
I need to figure what to do with.) I may just be running low
on creative cycles, so if you still think changes are needed,
please provide me some creative nudges.
Thanks,
Ken
---------------------------------------------------------------------------
Dr. Kenneth Laskey
MITRE Corporation, M/S H305
phone: 703-983-7934
7515 Colshire
Drive fax:
703-983-1379
McLean VA 22102-7508
--
Rex Brooks
GeoAddress:
1361-A Addison
Berkeley, CA 94702
Phone: 510-898-0670
|