09.02.2015 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

168 Chapter 9 Test<strong>in</strong>g from <strong>SOA</strong> to the <strong>Cloud</strong>s<br />

built for specific purposes, <strong>and</strong> many more are hosted by cloud comput<strong>in</strong>g<br />

providers.<br />

Mov<strong>in</strong>g up the stack, we f<strong>in</strong>d composite services, or services made up of<br />

other services, <strong>and</strong> all services leveraged by the bus<strong>in</strong>ess process or process<br />

layer, which provides the agile nature of an <strong>SOA</strong> us<strong>in</strong>g cloud comput<strong>in</strong>g, s<strong>in</strong>ce<br />

we can create <strong>and</strong> change solutions us<strong>in</strong>g a configuration metaphor, as we discussed<br />

<strong>in</strong> Chapter 1.<br />

When test<strong>in</strong>g services, keep the follow<strong>in</strong>g <strong>in</strong> m<strong>in</strong>d:<br />

Services are not complete applications or systems <strong>and</strong> must be tested as such.<br />

They are a small part of an application. However, they are not subsystems;<br />

they are small parts of subsystems as well. They must be tested with a high<br />

degree of <strong>in</strong>dependence, mean<strong>in</strong>g that the services are able to properly<br />

function both by themselves <strong>and</strong> as part of a cohesive system. Services are<br />

analogous to traditional application functions <strong>in</strong> terms of design <strong>and</strong> how<br />

they are leveraged to form solutions, f<strong>in</strong>e- or coarse-gra<strong>in</strong>ed.<br />

The best approach to test<strong>in</strong>g services is to list the use cases for those services.<br />

Then we can design test<strong>in</strong>g approaches for that service, <strong>in</strong>clud<strong>in</strong>g test<strong>in</strong>g<br />

harnesses, or the use of <strong>SOA</strong> test<strong>in</strong>g tools that automate test<strong>in</strong>g at the <strong>in</strong>terface<br />

<strong>and</strong> service levels (see Figure 9.1). We must also consider any services<br />

the service may employ: they must be tested holistically as a s<strong>in</strong>gle<br />

Automated<br />

Test<strong>in</strong>g Software<br />

Monitor<strong>in</strong>g<br />

Figure 9.1 Automated test<strong>in</strong>g tools allow services to be tested us<strong>in</strong>g preprogrammed<br />

scripts <strong>and</strong> programs that simulate real usage.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!