 |
Page History
...
SOA Testing Functional Profile
Conformance testing leverages the artifact and service metadata to validate that an implementation adequately addresses the requirements stated in the service specification. An example of service requirement is the ability to specify a response time in the specification (design time) and validate that this response time is valid for an implementation of the service. Additional test points include but are not limited to binding to specific terminologies and domain models.
Requirements include;
- Validation of harmonization
- Ensure mappings between terminologies are "semantically valid". In other words, to detect mappings that can cause semantic and logical inconsistencies in the terminologies involved in those mappings
- Support validation for use; for example a protocol designer will need to be able to build and validate the SEC based on programmatic retrieval of metadata.
- Validate consistency of model representations across multiple repositories
This Functional Profile includes, but is not limited to, the following capability elaborations:
Derived From Requirements
...
Testing
...
for
...
SOA Testing Model create, destroy, edit, maintain. Testing for SOA combines the typical challenges of software testing and certification with the additional needs of accommodating the distributed nature of the resources, the greater access of a more unbounded consumer population, and the desired flexibility to create new solutions from existing components over which the solution developer has little if any control. The purpose of testing is to demonstrate a required level of reliability, correctness, and effectiveness that enable prospective consumers to have adequate confidence in using a service. Adequacy is defined by the consumer based on the consumer's needs and context of use. Absolute correctness and completeness cannot be proven by testing; however, for SOA, it is critical for the prospective consumer to know what testing has been performed, how it has been performed, and what were the results.
The discussion of SOA Testing indicates numerous architectural implications on the SOA ecosystemSemantic Infrastructure include:
- The distributed, boundary-less nature of the SOA ecosystem makes it infeasible to create and maintain a single mock of the entire ecosystem to support testing activities.
- A standard suite of monitoring services needs to be defined, developed, and maintained. This should be done in a manner consistent with the evolving nature of the ecosystem.
- Services should provide interfaces that support access in a test mode.
- Testing resources must be described and their descriptions must be catalogued in a manner that enables their discovery and access.
- Guidelines for testing and ecosystem access need to be established and the ecosystem must be able to enforce those guidelines asserted as policies.
- Services should be available to support automated testing and regression testing.
- Services should be available to facilitate updating service description by anyone who has performed testing of a service.
This Functional Profile includes, but is not limited to, the following capability elaborations:
Derived From Requirements
- Semantic Infrastructure Requirements::Conformance Testing::Test for Conformance Conformance testing allows both CBIIT and other HL7 SAIF adopters to validate specifications.
| Anchor | ||||
|---|---|---|---|---|
|
SOA Testing Model with capabilities to create, destroy, edit, maintain test specifications, resources, and artifacts.
The SOA Testing Model implementation includes the following capabilities:
- Definition, development, and maintainenance of monitoring services
- Test point extensions for Service definitions
- Construction, maintenance, access, cataloging, and discovery of Test resource description models
- Construction, maintenance, and enforcement of policies derived from test Guidelines
- Services to support automated testing and regression testing.
- Services to facilitate updating service description by anyone who has performed testing of a service.
...
