A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2019; you can also visit <a rel="external noopener" href="https://static.aminer.org/pdf/20170130/pdfs/sigsoft/hcrddanomim1abk7svj9rylebfz4pnqh.pdf">the original URL</a>. The file type is <code>application/pdf</code>.
Whitening SOA testing
<span title="">2009</span>
<i title="ACM Press">
<a target="_blank" rel="noopener" href="https://fatcat.wiki/container/dj7g645z6zfl5lut4iwy5walyu" style="color: black;">Proceedings of the 7th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering on European software engineering conference and foundations of software engineering symposium - ESEC/FSE '09</a>
</i>
Preserved Fulltext
Service Oriented Architectures (SOAs) are becoming increasingly popular and powerful. Fueling that growth is the availability of independent web services that can be costeffectively composed with other services to provide richer functionality. The reasons that make these systems easier to build, however, also make them more challenging to test. Independent web services usually provide just an interface, enough to invoke them and develop some general (black-box) tests, but insufficient for a
<span class="external-identifiers">
<a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1145/1595696.1595721">doi:10.1145/1595696.1595721</a>
<a target="_blank" rel="external noopener" href="https://dblp.org/rec/conf/sigsoft/BartoliniBEM09.html">dblp:conf/sigsoft/BartoliniBEM09</a>
<a target="_blank" rel="external noopener" href="https://fatcat.wiki/release/tnebgwrhbvcfbdh3xtagl5hkau">fatcat:tnebgwrhbvcfbdh3xtagl5hkau</a>
</span>
more »
... er to develop an adequate understanding of the integration quality between the application and independent web services. To address this lack we propose a "whitening" approach to make web services more transparent through the addition of an intermediate coverage service. The approach, named Service Oriented Coverage Testing (SOCT), provides a tester with feedback about how a whitened service, called a Testable Service, is exercised. In this paper we introduce the SOCT approach, implement an instance of it, and perform a preliminary study to show its feasibility and potential value. SOCT enables SOA white-box testing, while maintaining SOA flexibility, dynamism and loose coupling.
<a target="_blank" rel="noopener" href="https://web.archive.org/web/20190216104522/https://static.aminer.org/pdf/20170130/pdfs/sigsoft/hcrddanomim1abk7svj9rylebfz4pnqh.pdf" title="fulltext PDF download" data-goatcounter-click="serp-fulltext" data-goatcounter-title="serp-fulltext">
<button class="ui simple right pointing dropdown compact black labeled icon button serp-button">
<i class="icon ia-icon"></i>
Web Archive
[PDF]
<div class="menu fulltext-thumbnail">
<img src="https://blobs.fatcat.wiki/thumbnail/pdf/07/82/07827d5c9eabbe37360a54e769337c8587f1e081.180px.jpg" alt="fulltext thumbnail" loading="lazy">
</div>
</button>
</a>
<a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1145/1595696.1595721">
<button class="ui left aligned compact blue labeled icon button serp-button">
<i class="external alternate icon"></i>
acm.org
</button>
</a>