Guideline: Reusable Service Testing Techniques
This guideline lists testing techniques that apply to services and solution building blocks.
Relationships
Main Description

Reusable Service Production

Testing should consist of verifying the following, for services and Solution Building Blocks:

  • The requirements (both functional and non-functional), that pertain to the service's variability points are met through the standalone implementation of the service.
  • The service can handle English and non-English characters.
  • The service is translated into multiple human languages.
  • Environment independence (e.g. portability, use on multiple operating systems).
  • The service is correctly packaged with its supporting artifacts, and correctly placed into the storage repository.
  • System-level use cases that pertain to the service's variability points are met through the implementation of the service.
  • The service's documentation describes how to customize and extend the service.
  • Where supported, it should be verified that the service has system management capabilities.
  • It should be verified that the performance and stress criteria of the service remains valid and achieved.
  • Performance requirements that pertain to the service's variability points are met, in addition to verifying robustness and efficiency.
  • Testing should be done in as much as full context (for multiple consumers) as possible.

Reusable Service Consumption Integration Testing

Testing should consist of verifying the following, for services and Solution Building Blocks, that are used to build solutions:

  • It is assumed and should be confirmed that the service has been through an appropriate amount of previous testing.
  • The requirements(both functional and non-functional), that correspond to the integration, installation, customization, extension and any modification of the service, as available, are met by the solution containing the service.
  • System-level use cases are met through the solution containing the service.
  • The solution's performance requirements, which utilize the service, are met through the solution containing the service.
  • If the service was harvested for reuse from an engagement that didn't require service reuse, there will likely be more test case modifications to be made, and a larger regression test suite will need to be executed.
  • Testing should also include a regression test suite for the service, one that is appropriately modified and enhanced.

Mini-Glossary

Context: Refers to the different environments in which an asset (or service) can be used. Examples include: Environments, geographies, and user populations.

Solution Building Block: Preconfigured bundle of interoperable hardware, middleware, and/or service bundle to enable a business or infrastructure solution, but requiring additional integration.