Cloud Computing and SOA Convergence in Your Enterprise: A Step ...

Testing from the Enterprise to the Clouds and Back 167
Leveraging white box testing, however, does not mean we can skip black
box testing. We still need to verify that the system functions correctly as a
whole system, even after we have traced through the code. White box testing is
not a replacement for black box testing; it is just another step we can leverage
to test the component more completely.
While white box testing is typically optimal, it is not always cost effective.
In the case of leveraging cloud computing providers, it is not possible. Understanding
black box testing and white box testing, and when and where to leverage
each approach, is important as we test our architecture.
As you may recall from Chapter 1, “Where We Are, How We Got Here,
and How to Fix It,” you can group the testing domains for SOA using cloud
computing into these major categories:
Service-level testing
Process-level testing
Governance-level testing
Information-level testing
We are now adding
Integration-level testing
Security-level testing
These are components of the architecture as well.
We focus more on service-level testing, on-premise and cloud-based, because
it is most critical to SOA using cloud computing. The categories or domains
that you choose to test within your architecture may differ depending
on the specific requirements for your architecture. Other areas need attention
as well, including quality assurance for the code, performance testing,
and auditing.
Service-Level Testing
Within the world of SOA using cloud computing, services are the building
blocks. Services become the base of an SOA and can be on-premise or cloudbased.
While some are abstract, existing “legacy services,” others are new and