TechClimbs Blog: System Integration Testing

System Integration Testing Part IV

<div dir="ltr" style="text-align: left;" trbidi="on">
In Part I and Part II we discussed about web services testing types. 
In this blog I will explain the SOAPUI tool to test web services. 
What is SOAPUI 
SOAPUI is a free and open source cross-platform Functional Testing 
solution. With an easy-to-use graphical interface, and enterprise-class 
features, SOAPUI allows you to easily and rapidly create and execute 
automated functional, regression, compliance, and load tests 
<h2>
The step-by-step guide:</h2>
<h2>
1. Create a test from a request in your WSDL</h2>
<ol>
<li>Click on the plus sign next to the web service in the navigator to expand.</li>
<li>
Double click on the request.</li>
</ol>
In SoapUI Pro, the request editor comes up to the right. SoapUI Pro 
has an Outline Editor that simplifies the hierarchical structure of the 
XML, both in requests and responses, and at the same time is 
customizable. 
Learn more about <a href="http://www.soapui.org/About-SoapUI/10-reasons-to-go-pro/2-The-Form-Editor.html">The Form Editor</a> and <a href="http://www.soapui.org/About-SoapUI/10-reasons-to-go-pro/1-The-Outline-Editor.html">The Outline Editor.</a> 
 
 If you are using SoapUI Open Source, you have to enter your data 
manually in the code editor as shown below. To benefit fully from this 
tutorial you should use the Pro version. You can download the Pro Trial 
version for free <a href="http://www.eviware.com/Download-soapUI-Trial.html">here</a>, giving you 2 weeks access. 
<ol start="3">
<li>In the request editor, select Add This Request to TestCase.
 SoapUI Pro takes the definition of the request and makes a form for you
 to enter information in. This may be especially useful when doing 
manual testing or if you want non-technical staff to enter a request.</li>
<li>
Adding a request to a TestCase will open the Create TestSuite dialog box. Enter a name for your TestSuite and click OK.</li>
<li>
After clicking OK, you will be asked to create a TestCase. In the Create TestCase dialog, enter a name for your TestCase and click OK.</li>
<li>
Next, the dialog box Add Request to TestCase will appear. Click OK.</li>
<li>
SoapUI Pro will now generate a TestSuite and TestCase for you while the 
request will be added as a TestRequest. Below is a copy of the request 
that appears in the interface. A TestCase editor will also open with 
your new TestRequest.</li>
</ol>
The next step is to validate the response in your test by adding an Assertion. 
<h2>
2. Add an Assertion to the test</h2>
Now that we’ve created and run our first test, we are going to add a validation of the response. In SoapUI, this is called adding an assertion.
 SoapUI Pro contains several functions that enhances automation for 
those who spends their days (and nights) testing and are in need of 
extensive assertions. 
Examples of assertions that is possible in SoapUI are: 
<ul>
<li>Schema Compliance</li>
<li>Simple Contains</li>
<li>Simple Not Contains</li>
<li>SOAP Fault</li>
<li>Not SOAP Fault</li>
<li>SOAP Response</li>
<li>Response SLA</li>
<li>XPath Match</li>
<li>XQuery Match</li>
<li>Script Assertion</li>
<li>WS-Security Status</li>
<li>WS-Addressing Response Assertion</li>
<li>WS-Addressing Request Assertion</li>
</ul>
<ol>
<li>Close all windows you have open in soupUI before starting. Double Click on your Test Request as shown below. This will open the request editor.</li>
<li>
In the request editor, Click the Add an Assertion to Test Request button.</li>
</ol>
<ol start="3">
<li>Select Response SLA from the drop down in the Select Assertion dialog box.</li>
<li>
In the Configure Response SLA Assertion dialog box, write 500 and click 
OK. This will validate that the response of the SLA is under 500.</li>
<li>
Now that you’ve added the assertion, you are going to run the request to
 validate the response. If all assertions are successful, the SOAP icon 
should turn green in three places as shown below.</li>
</ol>
Tip! You can see how many assertions you have in a test 
by looking at the assertions tab. The number of assertions is written on
 the tab “Assertions (2)” 
<ol start="6">
<li>You can also validate the response by adding an XPath Match assertion.</li>
<li>
In SoapUI Pro you can open the Select XPath dialog, which let’s
 you select nodes to assert using point-and-click. As a result SoapUI 
creates the matching XPath expression that refers to the selected node.</li>
<li>SoapUI automatically populates the expected result to match what’s 
in the response. But of course, you can change this to what’s relevant 
for you.</li>
</ol>
Learn more about <a href="http://www.soapui.org/About-SoapUI/10-reasons-to-go-pro/3-Point-and-Click-Testing.html">Point and Click Testing.</a> 
<ol start="9">
<li>
Now let’s try and enter the ianacode SE (for Sweden) as a request, and execute the test.</li>
<li>
Oh no! The test failed! SoapUI gives us a red icon in three different 
places, and the Assertions-tab expands telling us that our XPath 
Assertion failed. This is because we said that the allregionslist should contain the US states, and we asked for the Swedish regions.</li>
<li>
Change back the ianacode to US and try executing the test again. You 
will now see that all assertion are set to “VALID”. This is because the 
we now get the list of US States in the response, which is what the 
XPath Assertion is looking for.</li>
</ol>
Now that you know what an assertion is and how you add one to the 
test, it is time for the final exam of this guide – to run the actual 
test. 
<h2>
3. Run a test</h2>
There are several different places in SoapUI where you can run the 
test. You can do it on a TestStep level, which is what we have done in 
this guide. 
You can also try running the TestCase from the TestCase Editor… 
…or from the TestSuite Editor. 
 
Reference: <a href="http://www.soapui.org/" rel="nofollow">http://www.soapui.org</a></div>

System Integration Testing Part IV

In Part I and Part II we discussed about web services testing types. In this blog I will explain the SOAPUI tool to test web services. Wh...

System Integration Testing Part III

<div dir="ltr" style="text-align: left;" trbidi="on">In this blog we will discuss testing types in details. How we can test web services. 
How to test Web Services 
There is not interface available to test web services. In some case you have the interface but in normal cases you don’t have any interface. Following are few testing techniques that can be used for web services testing. 
Testing Techniques 
<ul><li>Functional testing</li>
<li>Regression testing</li>
<li>Security Testing</li>
<li>Load/stress testing</li>
<li>Monitoring</li>
</ul>Tools than can be used for Web Services Testing 
<ul><li>SOAPUI</li>
<li>LOADUI</li>
</ul>Functional Testing 
<ul><li>To ensure that the functionality of the web service is as expected</li>
<li>Does your web service support all the communications protocols it is meant to</li>
<li>Does your web service implement security/authentication as it is meant to Because your web service can be accessed by clients that you can’t control, what happens if they make requests you aren’t expecting</li>
<li>Since no interface is available to test web services so to test web services an open source tool SOAPUI is available for Functional Testing</li>
<li>Analyses the service logs to find the issues</li>
</ul>Example: 
If you have a web service that take two inputs(a, b) and divides two numbers, you will verify 
<ul><li>Does it give the expected result?</li>
<li>If you pass in a 0 as the denominator, does it handle this correctly</li>
</ul>Regression testing 
<ul><li>A regression test is normally a cut-down version of a functional test</li>
<li>Its aim is to ensure that the web service is still working between builds or releases</li>
</ul>Example: 
If your development team has changed the method that divides two numbers, does that method still work? Does the method that multiplies two numbers still work? Is the performance still affordable? 
Load/stress testing 
<ul><li>The aim of load/stress testing is to find how your web service scales as the number of clients accessing it increases</li>
<li>LOADUI(an open source tool)  or Load Runner can be used for performance testing.</li>
</ul>Monitoring 
Once your web service is live and being used by real clients, you will need to keep an eye on it 
<ul><li>Is it still working?</li>
<li>Are response times adequate?</li>
<li>At what times of day is it busiest?</li>
<li>See the service logs regularly</li>
</ul>In next part we will explore the tool(SOAPUI/LOADUI) that is used to test web services.</div>

System Integration Testing Part III

In this blog we will discuss testing types in details. How we can test web services. How to test Web Services There is not interface avail...

System Integration Testing

0 Manual Testing, Software Testing, System Integration Testing

<div dir="ltr" style="text-align: left;" trbidi="on"><div><script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script> 
 
<ins class="adsbygoogle"
 style="display:inline-block;width:300px;height:250px"
 data-ad-client="ca-pub-3427941912749308"
 data-ad-slot="1095870475"></ins> 
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script> 
System Integration 
 
<div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">System integration is the bringing together of the component Sub Systems into one system and ensuring that the subsystems function together as a system (Wikipedia).</div> 
<div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">Integration is the process of inter-connecting multiple systems with each other in order to provide a useful exchange of information, data and/or control between the systems.</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> 
</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">System </div> 
<div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">A system is a group of hardware and software components that work together in a cohesive manner to perform a task. </div> 
<div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">A system may be as simple as a single controller or as complex as the telephone network. A personal computer with a video card, memory, a disk drive and an operating system is also a system. </div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> 
</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> </div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">Interface </div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">An interface is a point where interaction occurs between multiple systems, devices, programs, etc . BizTalk Server is an example of Interface</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> 
</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> 
</div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjrSdFh_Ai18q7vyuy-z1Ag3IGl4EKAv5Kbv_dwy5mvthFQdPd8yGeEzKup7czHsd3344AxU5SbfwE9Zwqcgi0Ij6PVCFl9uvoA2EC0ocDZhiV0xF1G6vZ-U8AndD_aVYCaR4Okc3pYG4Y/s1600/Untitled.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="232" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjrSdFh_Ai18q7vyuy-z1Ag3IGl4EKAv5Kbv_dwy5mvthFQdPd8yGeEzKup7czHsd3344AxU5SbfwE9Zwqcgi0Ij6PVCFl9uvoA2EC0ocDZhiV0xF1G6vZ-U8AndD_aVYCaR4Okc3pYG4Y/s400/Untitled.png" width="400" /></a></div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> 
</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> </div>System integration can be performed through Biztalk Server(Microsoft) , Cost  Iron(IBM). In this blog I will discuss System Integration with Biztalk. 
 
 
 Biztalk Server Introduction 
<div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">BizTalk Server is Microsoft’s Integration and connectivity server solution. BizTalk Server provides a solution that allows organizations to more easily connect disparate systems. In addition to integration functionality, BizTalk also provides strong durable messaging, a rules engine, EDI connectivity(Electronic Data Interchange), Business Activity Monitoring (BAM).</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> 
</div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhd-KVORmehGmJQ41ka4ggbpOhAEyJReMMTUtg2xrloHj9OfDedhotR9yeljk1uxa0ILHSq6dfLAcLqhMOWmkbPaqjBRtd75x2VUd_QCDxIclz5hSKRAQNq6eq6M3r_1FchMvJ5-NN6S1c/s1600/Untitled.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="207" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhd-KVORmehGmJQ41ka4ggbpOhAEyJReMMTUtg2xrloHj9OfDedhotR9yeljk1uxa0ILHSq6dfLAcLqhMOWmkbPaqjBRtd75x2VUd_QCDxIclz5hSKRAQNq6eq6M3r_1FchMvJ5-NN6S1c/s400/Untitled.png" width="400" /></a></div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> 
</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">Components of Biztalk</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> 
</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> </div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">Receive Pipelines</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> </div><ul style="text-align: left;"><li>Provide a way to examine, verify, and potentially modify messages as they are received </li>
<li>Used to do operations on inbound messages </li>
<li>Operations include</li>
</ul> </div><blockquote class="tr_bq"><ul style="text-align: left;"><li>Decoding </li>
<li>Disassembling </li>
<li>Verification</li>
</ul></blockquote><div>Receive Ports</div><div> 
<ul style="text-align: left;"><li>How messages get into BizTalk </li>
<li>Variety of transport mechanisms</li>
</ul> 
<blockquote class="tr_bq"><ul style="text-align: left;"><li>Http </li>
<li>SOAP </li>
<li>SQL </li>
<li>File </li>
<li>EDI </li>
<li>Message Queue</li>
</ul></blockquote>  <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjIlGICeo-w8Vx4Xi-Ke0TiMPkh9k_frrZUU7bA_mEpUyL194SYAOXScqkWJtbSyJOL9HXeGtxdgsoOLVhR1gIqBYCdeZYYJqui71dP5x_yIWcMrclO3rhLctpDh_wHV6LwGUqj8AAo-7w/s1600/Untitled.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="207" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjIlGICeo-w8Vx4Xi-Ke0TiMPkh9k_frrZUU7bA_mEpUyL194SYAOXScqkWJtbSyJOL9HXeGtxdgsoOLVhR1gIqBYCdeZYYJqui71dP5x_yIWcMrclO3rhLctpDh_wHV6LwGUqj8AAo-7w/s400/Untitled.png" width="400" /></a> </div><div></div><div></div><div>Orchestrations  </div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjyb-_ORd0790JWbpGkNSHy4vn5RTeJJAVaBWacOVa9xXCmaJIokNkyPH4PJpkNCEI82ufk-K7RZaEPRCnicK4vWpzyTsGQnzSksD6X0goQ5sHHgYh9D7dlK3wx03_vkgo6bWna29Yu-T0/s1600/Untitled.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"> 
</a></div><div> 
<ul style="text-align: left;"><li>How business processes are implemented</li>
<li>Visual display of process implementation</li>
<li>Developed in Visual Studio</li>
<li>Similar to flow charts </li>
</ul> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjyb-_ORd0790JWbpGkNSHy4vn5RTeJJAVaBWacOVa9xXCmaJIokNkyPH4PJpkNCEI82ufk-K7RZaEPRCnicK4vWpzyTsGQnzSksD6X0goQ5sHHgYh9D7dlK3wx03_vkgo6bWna29Yu-T0/s1600/Untitled.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="162" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjyb-_ORd0790JWbpGkNSHy4vn5RTeJJAVaBWacOVa9xXCmaJIokNkyPH4PJpkNCEI82ufk-K7RZaEPRCnicK4vWpzyTsGQnzSksD6X0goQ5sHHgYh9D7dlK3wx03_vkgo6bWna29Yu-T0/s400/Untitled.png" width="400" /> </a></div><div></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjqNIsvkx-EdPDJbNBUAVWE6lbeXXN1tewjZk9G9D2VfSrO2idlQ4M9nUbjdusklG5uFx2G35VpFdIAID92367kpD1fq2nGyEracNfBnJ8-1t7eEwA3KRfQwDUVqi491bFVa7mkJDfPzmE/s1600/Untitled.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"> 
</a></div><div style="text-align: left;"> 
<div style="margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">Send Pipeline</div>  
<ul style="text-align: left;"><li>Opposite of receive pipelines. Used on outbound messages </li>
<li>Operations include</li>
</ul><blockquote class="tr_bq"><ul style="text-align: left;"><li>Encoding</li>
<li> Assembling </li>
<li>Signing   </li>
</ul></blockquote> 
 
<div style="margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">Send Ports</div><div style="margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> </div><ul style="text-align: left;"><li>Similar to receive ports but used to send messages out of BizTalk</li>
<li>Multiple possible transports like receive ports</li>
</ul><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhuxt_mVNeFoHuqJJASsjdjxt_w9EZXMDDRlCXTenyQSJzz5pnrXpCPZCji8X0gGBKufMSu9R4-RQdO_SUazX9pXRfJU8DrkbW-2G-Xig80zHBikuoODPSUFi-DLSD6ScOqi6tBvTOJKFg/s1600/Untitled.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="176" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhuxt_mVNeFoHuqJJASsjdjxt_w9EZXMDDRlCXTenyQSJzz5pnrXpCPZCji8X0gGBKufMSu9R4-RQdO_SUazX9pXRfJU8DrkbW-2G-Xig80zHBikuoODPSUFi-DLSD6ScOqi6tBvTOJKFg/s400/Untitled.png" width="400" /> </a> </div><div class="separator" style="clear: both; text-align: center;"> 
</div><div style="margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">Business Rules Engine</div> 
<div class="separator" style="clear: both; text-align: left;">  </div><ul><li>Its engine to implement the business logic in a decoupled way. </li>
<li>Its has a graphical interface BRC(Business Rule Composer) </li>
<li>A means of implementing business rules away from core system </li>
</ul><blockquote class="tr_bq"><ul style="text-align: left;"><li>English like syntax for non technical person to define business rules </li>
<li>Versioned </li>
<li>Stored in a SQL Server database </li>
<li>After implement any change in business rule , user don’t have to update or rebuild existing applications</li>
</ul></blockquote> 
<ul><li>Can allow the business to control the rules used in systems </li>
<li>Main artefacts of BRE are </li>
</ul><blockquote class="tr_bq"><ul style="text-align: left;"><li>Vocabulary(data facts) </li>
<li>Policies(Rules/Conditions)</li>
</ul></blockquote><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgtnjtOOspkxWNHRFOKWMCZycNohRQkLWx8A4T5qIua7F8XzohfM9wMRmL2YoulJa0CG4vrlGXiG1ENLVJsOtY7urUPGyHUW9PWftuZGJfQgCrsPEqX4-AfqAhAbqph3JZrM2ydyHoDgLc/s1600/fig9.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="357" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgtnjtOOspkxWNHRFOKWMCZycNohRQkLWx8A4T5qIua7F8XzohfM9wMRmL2YoulJa0CG4vrlGXiG1ENLVJsOtY7urUPGyHUW9PWftuZGJfQgCrsPEqX4-AfqAhAbqph3JZrM2ydyHoDgLc/s400/fig9.jpg" width="400" /></a></div><div style="margin-bottom: 0pt; margin-left: 0.5in; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> 
</div><div style="margin-bottom: 0pt; margin-left: 0.5in; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> </div>Business Activity Monitoring (BAM) 
<ul style="text-align: left;"><li>Business end user empowerment through the BAM portal </li>
<li>Business alerts and notifications End-to-end visibility of the business process</li>
</ul>  
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjqNIsvkx-EdPDJbNBUAVWE6lbeXXN1tewjZk9G9D2VfSrO2idlQ4M9nUbjdusklG5uFx2G35VpFdIAID92367kpD1fq2nGyEracNfBnJ8-1t7eEwA3KRfQwDUVqi491bFVa7mkJDfPzmE/s1600/Untitled.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="167" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjqNIsvkx-EdPDJbNBUAVWE6lbeXXN1tewjZk9G9D2VfSrO2idlQ4M9nUbjdusklG5uFx2G35VpFdIAID92367kpD1fq2nGyEracNfBnJ8-1t7eEwA3KRfQwDUVqi491bFVa7mkJDfPzmE/s400/Untitled.png" width="400" /></a></div><div style="text-align: left;"><div style="margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> 
</div>  
<div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">System Integration Testing Overview</div><div style="margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">Introduction</div><div style="margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> </div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">System Integration Testing is the testing performed when multiple systems, generally presumed stable themselves, are integrated with one another.</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> 
</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> </div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">Test Strategy</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> </div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">In System integration testing there is no interface like web applications or desktop applications. You will have only Biztalk interfaces. You needs to know the received ports and send ports. verification is on both these two ports. Logs will be generated on both two ports. You should have the ability to understand the logs . You can only identify issues from logs.</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> 
</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">There are few concepts for System Integration testing. </div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">Integration Portal</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">In integration portal all error logs when a action failed. its all depends on programing logic which request will be in integration portal. You should test the integration portal in parallel with your testing</div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">  </div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">BAM </div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">In BAM , business users can see what is going on with their systems. Business Activity Monitoring is done in BAM. You should also test the BAM in parallel with you testing. </div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"></div><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">Testing types can be divided into two main categories </div> 
<ul style="text-align: left;"><li>Functional Testing   </li>
</ul><blockquote class="tr_bq"><ul style="text-align: left;"><li> Smoke testing </li>
<li>Components’ Functionality testing </li>
<li>End to End testing </li>
<li>Data Integrity testing </li>
<li>Regression testing </li>
</ul></blockquote></div><div style="text-align: left;"><ul style="text-align: left;"><li>Non-Functional Testing. </li>
</ul><blockquote class="tr_bq"><ul style="text-align: left;"><li>Performance Testing</li>
</ul></blockquote></div><div style="text-align: left;">Smoke testing 
Testing a critical subset of Functionality and End to End tests to verify the System Under Test works in a general sense before additional testing is performed 
Components’ Functionality testing 
The primary focus of this testing is to validate that the developed solution meets the approved business requirements. Additional test scenarios are executed to validate the system under test’s capabilities on handling exceptions. 
 
For Example if two or more than two systems are integrated through BizTalk we will verify 
<ul style="text-align: left;"><li>BizTalk Send Ports , Received Ports are verified </li>
<li>Window services and Web services are verified. </li>
<li>BizTalk orchestration's are verified </li>
<li>We verify all instances of BizTalk server are working fine no instances is suspended due to unexpected exceptions </li>
<li>Business Rule Engine policies are verified. </li>
<li>Schemas of web services are verified. </li>
<li>Logs of Window service for database records extraction are verified </li>
<li>Event logs , and wiretaps are verified- requests are logged properly in wiretaps. </li>
<li>Queues are verified</li>
<li>Verify logs files that generated while performing testing </li>
</ul><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> 
</div>End to End testing 
In END to END testing our focus is on complete system. We test the whole system working from starting point to the end point. 
 
For Example 
 
There are four servers. Server1, Server2, Server3 , Server4 
 
The source system is Server1 and others are the target systems. Data flow is from server 1 to server2 then server3 then server4 and then response to Server1 
<ul style="text-align: left;"><li>We will verify the whole system is working fine, </li>
<li>BAM is working fine </li>
<li>No error produced </li>
<li>No instances are suspended </li>
<li>Integration Portal is working fine </li>
<li>Data Integrity in all servers</li>
</ul><div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">Data Integrity testing </div>Testing to validate the accuracy of data displayed/captured during and after the functional transactions Regression testing 
Testing functionality and integration of systems that are not changed during the project, but that may be impacted by project-related updates 
<div style="direction: ltr; margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"></div>Performance Testing </div><ul style="text-align: left;"><li>Testing the system under load (user, data and/or duration) to verify performance requirements are met</li>
<li>Test performance of Web services and identify bottlenecks. </li>
<li>In case of multiple requests of different systems the behaviors of the Integrated system. </li>
</ul><div style="text-align: left;"> 
 
<div style="margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;">  </div><div style="margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> 
</div><div style="margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"><script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script> 
 
<ins class="adsbygoogle"
 style="display:inline-block;width:300px;height:250px"
 data-ad-client="ca-pub-3427941912749308"
 data-ad-slot="1095870475"></ins> 
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script> 
</div><div style="margin-bottom: 0pt; margin-top: 0pt; text-align: left; unicode-bidi: embed; vertical-align: baseline;"> 
</div></div></div>

System Integration Testing

System Integration System integration is the bringing together of the component Sub Systems into one system and ensuring that the subs...

Web Services Testing Part III

0 Manual Testing, Software Testing, System Integration Testing

<div dir="ltr" style="text-align: left;" trbidi="on"> <div class="MsoNormal" style="line-height: normal; margin-bottom: 0.0001pt;">In Part I and Part II we discussed about web services testing types. In this blog I will explain the SOAPUI tool to test web services.</div> <div class="MsoNormal" style="line-height: normal; margin-bottom: 0.0001pt;"> 
</div> <div class="MsoNormal" style="line-height: normal; margin-bottom: 0.0001pt;">What is SOAPUI</div> 
 
<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script> 
 
<ins class="adsbygoogle"
 style="display:inline-block;width:300px;height:250px"
 data-ad-client="ca-pub-3427941912749308"
 data-ad-slot="1095870475"></ins> 
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script> 
 </html> <div class="MsoNormal" style="line-height: normal; margin-bottom: 0.0001pt; vertical-align: baseline;">SOAPUI is a free and open source cross-platform Functional Testing solution. With an easy-to-use graphical interface, and enterprise-class features, SOAPUI allows you to easily and rapidly create and execute automated functional, regression, compliance, and load tests</div> <div class="MsoNormal" style="line-height: normal; margin-bottom: 0.0001pt; vertical-align: baseline;"> 
</div> 
<h2>The step-by-step guide:</h2> <a href="http://www.blogger.com/blogger.g?blogID=364078455121201764" name="create_test"></a> <h2>1. Create a test from a request in your WSDL</h2> 1. Click on the plus sign next to the web service in the navigator to expand. 
 <img alt="Web Services in the navigator" src="http://www.soapui.org/images/stories/newfunctesting/func_test_image1.jpg" title="Web Services in the navigator" /> 
 
2. Double click on the request. 
 <img alt="Request" src="http://www.soapui.org/images/FunctionalTesting/2.png" /> 
 
In SoapUI Pro, the request editor comes up to the right. SoapUI Pro has an Outline Editor that simplifies the hierarchical structure of the XML, both in requests and responses, and at the same time is customizable. 
 <a href="http://www.blogger.com/blogger.g?blogID=364078455121201764" name="form_editor"></a> <img alt="SoapUI Pro" src="http://www.soapui.org/images/stories/newfunctesting/feature-focus_2.png" title="SoapUI Pro" /> 
 Learn more about <a href="http://www.soapui.org/About-SoapUI/10-reasons-to-go-pro/2-The-Form-Editor.html" target="_blank" title="The Form Editor">The Form Editor</a> and <a href="http://www.soapui.org/About-SoapUI/10-reasons-to-go-pro/1-The-Outline-Editor.html" target="_blank" title="The Outline Editor">The Outline Editor.</a> 
 
 If you are using SoapUI Open Source, you have to enter your data manually in the code editor as shown below. To benefit fully from this tutorial you should use the Pro version. You can download the Pro Trial version for free <a href="http://www.eviware.com/Download-soapUI-Trial.html" title="SoapUI_Trial">here</a>, giving you 2 weeks access. 
 <img alt="Open source view of SoapUI" src="http://www.soapui.org/images/stories/newfunctesting/func_test_3.jpg" title="Open source window in SoapUI" /> 
 
 
 3. In the request editor, select Add This Request to TestCase. SoapUI Pro takes the definition of the request and makes a form for you to enter information in. This may be especially useful when doing manual testing or if you want non-technical staff to enter a request. 
 <img alt="Add This Request to TestCase" src="http://www.soapui.org/images/stories/newfunctesting/func_test_4.jpg" title="Add This Request to TestCase" /> 
 
4. Adding a request to a TestCase will open the Create TestSuite dialog box. Enter a name for your TestSuite and click OK. 
 <img alt="Create TestSuite" src="http://www.soapui.org/images/FunctionalTesting/6.png" /> 
 
5. After clicking OK, you will be asked to create a TestCase. In the Create TestCase dialog, enter a name for your TestCase and click OK. 
 <img alt="Create TestCase" src="http://www.soapui.org/images/FunctionalTesting/7.png" /> 
 
6. Next, the dialog box Add Request to TestCase will appear. Click OK. 
 <img alt="Add Request to TestCase" src="http://www.soapui.org/images/stories/newfunctesting/func_test_5.jpg" title="Add Request to TestCase" /> 
 
7. SoapUI Pro will now generate a TestSuite and TestCase for you while the request will be added as a TestRequest. Below is a copy of the request that appears in the interface. A TestCase editor will also open with your new TestRequest. 
 <img alt="TestRequest" src="http://www.soapui.org/images/stories/newfunctesting/func_test_6.jpg" title="TestRequest" /> 
 
The next step is to validate the response in your test by adding an Assertion. 
 
 <a href="http://www.blogger.com/blogger.g?blogID=364078455121201764" name="add_assertion"></a> <h2>2. Add an Assertion to the test</h2> Now that we've created and run our first test, we are going to add a validation of the response. In SoapUI, this is called adding an assertion. SoapUI Pro contains several functions that enhances automation for those who spends their days (and nights) testing and are in need of extensive assertions. 
 Examples of assertions that is possible in SoapUI are: 
 <ul><li>Schema Compliance</li>
<li>Simple Contains</li>
<li>Simple Not Contains</li>
<li>SOAP Fault</li>
<li>Not SOAP Fault</li>
<li>SOAP Response</li>
<li>Response SLA</li>
<li>XPath Match</li>
<li>XQuery Match</li>
<li>Script Assertion</li>
<li>WS-Security Status</li>
<li>WS-Addressing Response Assertion</li>
<li>WS-Addressing Request Assertion</li>
</ul> 
 1. Close all windows you have open in soupUI before starting. Double Click on your Test Request as shown below. This will open the request editor. 
 <img alt="Request" src="http://www.soapui.org/images/stories/newfunctesting/func_test_7.jpg" title="Request" /> 
 
2. In the request editor, Click the Add an Assertion to Test Request button. 
 <img alt="Test Request" src="http://www.soapui.org/images/stories/newfunctesting/func_test_8.jpg" title="Test Request" /> 
 
 3. Select Response SLA from the drop down in the Select Assertion dialog box. 
 <img alt="Add an assertion to test request" src="http://www.soapui.org/images/stories/newfunctesting/func_test_9.jpg" title="Add an assertion to test request" /> 
 
4. In the Configure Response SLA Assertion dialog box, write 500 and click OK. This will validate that the response of the SLA is under 500. 
 <img alt="Select assertion" src="http://www.soapui.org/images/stories/newfunctesting/func_test_10.jpg" title="Select assertion" /> 
 
 5. Now that you've added the assertion, you are going to run the request to validate the response. If all assertions are successful, the SOAP icon should turn green in three places as shown below. 
 <img alt="How Many Assertions" src="http://www.soapui.org/images/stories/newfunctesting/func_test_11.jpg" title="How Many Assertions" /> 
 
Tip! You can see how many assertions you have in a test by looking at the assertions tab. The number of assertions is written on the tab "Assertions (2)" 
 6. You can also validate the response by adding an XPath Match assertion. 
 <img alt="Select assertion - XPath Match" src="http://www.soapui.org/images/stories/functionaltesting/select%20assertion%20-%20xpath%20match.png" title="Select assertion - XPath Match" /> 
 
7. In SoapUI Pro you can open the Select XPath dialog, which let's you select nodes to assert using point-and-click. As a result SoapUI creates the matching XPath expression that refers to the selected node. 
 <img alt="XPath Match - Select XPath Pro" src="http://www.soapui.org/images/stories/newfunctesting/xpath_grayout.png" title="XPath Match - Select XPath Pro" /> 
 <img alt="Select XPath - Chosen Node" src="http://www.soapui.org/images/stories/newfunctesting/feature-focus-12.png" title="Select XPath - Chosen Node" /> 
 8. SoapUI automatically populates the expected result to match what's in the response. But of course, you can change this to what's relevant for you. 
 <img alt="XPath Match Expected Results" src="http://www.soapui.org/images/stories/newfunctesting/func_test_13_new.png" title="XPath Match Expected Results" /> 
 Learn more about <a href="http://www.soapui.org/About-SoapUI/10-reasons-to-go-pro/3-Point-and-Click-Testing.html" target="_blank" title="Point and Click Testing">Point and Click Testing.</a> 
 
9. Now let's try and enter the ianacode SE (for Sweden) as a request, and execute the test. 
 <img alt="Search for SE" src="http://www.soapui.org/images/stories/newfunctesting/func_test_22.jpg" title="Search for SE" /> 
 
10. Oh no! The test failed! SoapUI gives us a red icon in three different places, and the Assertions-tab expands telling us that our XPath Assertion failed. This is because we said that the allregionslist should contain the US states, and we asked for the Swedish regions. 
 <img alt="Xpath Assertion Fails" src="http://www.soapui.org/images/stories/newfunctesting/func_test_23.jpg" title="XPath Assertion Fails" /> 
 
11. Change back the ianacode to US and try executing the test again. You will now see that all assertion are set to "VALID". This is because the we now get the list of US States in the response, which is what the XPath Assertion is looking for. 
 <img alt="Xpath Assertion Valid" src="http://www.soapui.org/images/stories/newfunctesting/func_test_24.jpg" title="Xpath Assertion Valid" /> 
 
Now that you know what an assertion is and how you add one to the test, it is time for the final exam of this guide - to run the actual test. 
 
 <a href="http://www.blogger.com/blogger.g?blogID=364078455121201764" name="run_test"></a> <h2>3. Run a test</h2> There are several different places in SoapUI where you can run the test. You can do it on a TestStep level, which is what we have done in this guide. 
 You can also try running the TestCase from the TestCase Editor… 
 <img alt="TestCase Editor" src="http://www.soapui.org/images/stories/newfunctesting/func_test_19.jpg" title="TestCase Editor" /> 
 
…or from the TestSuite Editor. 
 
 
 
 
 
<img alt="TestSuite Editor" src="http://www.soapui.org/images/stories/newfunctesting/func_test_20.jpg" title="TestSuite Editor" />  
 
 Reference: http://www.soapui.org 
 
 
 
 
 
 
 
 
</div>

Web Services Testing Part III

In Part I and Part II we discussed about web services testing types. In this blog I will explain the SOAPUI tool to test web services. ...

System Integration Testing Part II

0 Manual Testing, Software Testing, System Integration Testing

<div dir="ltr" style="text-align: left;" trbidi="on"><script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script> 
 
<ins class="adsbygoogle"
 style="display:inline-block;width:300px;height:250px"
 data-ad-client="ca-pub-3427941912749308"
 data-ad-slot="1095870475"></ins> 
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script> 
In this blog I will discuss how to perform web services testing. To test web services one should know about 
<ul><li>What is XML</li>
<li>What are web services</li>
</ul>What is XML 
<ul><li>XML stands for Extensible Markup Language</li>
<li>XML is a markup language much like HTML</li>
<li>XML was designed to carry data, not to display data</li>
<li>XML tags are not predefined. You must define your own tags</li>
<li>XML is designed to be self-descriptive</li>
<li>XML is a W3C Recommendation</li>
</ul><a href="https://infosharehouse.files.wordpress.com/2013/01/xml.png"><img alt="xml" class="alignnone size-medium wp-image-24" height="192" src="https://infosharehouse.files.wordpress.com/2013/01/xml.png?w=300&h=192" width="300" /></a> 
Web Services Overview 
Web services are distributed application components that are externally available. You can use them to integrate computer applications that are written in different languages and run on different platforms. Web services are language and platform independent because vendors have agreed on common web service standards. 
There are three type of Web services platform elements: 
<ul><li>SOAP (Simple Object Access Protocol)</li>
<li>WSDL (Web Services Description Language)</li>
</ul><a href="https://infosharehouse.files.wordpress.com/2013/01/xml1.png"><img alt="xml" class="alignnone size-medium wp-image-25" height="133" src="https://infosharehouse.files.wordpress.com/2013/01/xml1.png?w=300&h=133" width="300" /></a> 
SOAP 
SOAP is an XML-based protocol to let applications exchange information over HTTP. 
Or more simple: SOAP is a protocol for accessing a Web Service. 
<ul><li>SOAP stands for Simple Object Access Protocol</li>
<li>SOAP is a communication protocol</li>
<li>SOAP is a format for sending messages</li>
<li>SOAP is designed to communicate via Internet</li>
<li>SOAP is platform independent</li>
<li>SOAP is language independent</li>
<li>SOAP is based on XML</li>
<li>SOAP is simple and extensible</li>
<li>SOAP allows you to get around firewalls</li>
<li>SOAP is a W3C standard</li>
</ul>WSDL 
WSDL is an XML-based language for locating and describing Web services. 
<ul><li>WSDL stands for Web Services Description Language</li>
<li>WSDL is based on XML</li>
<li>WSDL is used to describe Web services</li>
<li>WSDL is used to locate Web services</li>
<li>WSDL is a W3C standard</li>
</ul>How to test Web Services 
There is not interface available to test web services. In some case you have the interface but in normal cases you don’t have any interface. Following are few testing techniques that can be used for web services testing. 
Testing Techniques 
<ul><li>Functional testing</li>
<li>Regression testing</li>
<li>Security Testing</li>
<li>Load/stress testing</li>
<li>Monitoring</li>
</ul>Tools than can be used for Web Services Testing 
<ul><li>SOAPUI</li>
<li>LOADUI</li>
</ul>Challenges in testing web services 
Like all software, web services need to be tested. Like websites, they are often highly visible, so they need to be very robust.  Some example of challenge’s are 
<ul><li>No Graphical User Interface available to test web services</li>
<li>Troubleshooting of issues not an easy job</li>
<li>Security Issues</li>
<li>Performance Issues</li>
</ul>In <a href="https://infosharehouse.wordpress.com/2013/01/30/web-services-testing-part-ii/">next blog</a> we will discuss these testing techniques in details. Your feedback will be highly appreciated 
Reference:  “<a href="http://www.w3schools.com/">w3schools</a>“</div>

System Integration Testing Part II

In this blog I will discuss how to perform web services testing. To test web services one should know about What is XML What are web s...

System Integration Testing Part I

2 Software Testing, System Integration Testing

<div dir="ltr" style="text-align: left;" trbidi="on"><script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script> 
 
<ins class="adsbygoogle"
 style="display:inline-block;width:300px;height:250px"
 data-ad-client="ca-pub-3427941912749308"
 data-ad-slot="1095870475"></ins> 
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script> 
In this blog I will discuss how to perform web services testing. To test web services one should know about 
<ul><li>What is XML</li>
<li>What are web services</li>
</ul>What is XML 
<ul><li>XML stands for Extensible Markup Language</li>
<li>XML is a markup language much like HTML</li>
<li>XML was designed to carry data, not to display data</li>
<li>XML tags are not predefined. You must define your own tags</li>
<li>XML is designed to be self-descriptive</li>
<li>XML is a W3C Recommendation</li>
</ul> 
Web Services Overview 
Web services are distributed application components that are externally available. You can use them to integrate computer applications that are written in different languages and run on different platforms. Web services are language and platform independent because vendors have agreed on common web service standards. 
There are three type of Web services platform elements: 
<ul><li>SOAP (Simple Object Access Protocol)</li>
<li>WSDL (Web Services Description Language)</li>
</ul> 
<ul></ul> 
SOAP 
SOAP is an XML-based protocol to let applications exchange information over HTTP. 
Or more simple: SOAP is a protocol for accessing a Web Service. 
<ul><li>SOAP stands for Simple Object Access Protocol</li>
<li>SOAP is a communication protocol</li>
<li>SOAP is a format for sending messages</li>
<li>SOAP is designed to communicate via Internet</li>
<li>SOAP is platform independent</li>
<li>SOAP is language independent</li>
<li>SOAP is based on XML</li>
<li>SOAP is simple and extensible</li>
<li>SOAP allows you to get around firewalls</li>
<li>SOAP is a W3C standard</li>
</ul>WSDL 
WSDL is an XML-based language for locating and describing Web services. 
<ul><li>WSDL stands for Web Services Description Language</li>
<li>WSDL is based on XML</li>
<li>WSDL is used to describe Web services</li>
<li>WSDL is used to locate Web services</li>
<li>WSDL is a W3C standard</li>
</ul>How to test Web Services 
There is not interface available to test web services. In some case you have the interface but in normal cases you don’t have any interface. Following are few testing techniques that can be used for web services testing. 
Testing Techniques 
<ul><li>Functional testing</li>
<li>Regression testing</li>
<li>Security Testing</li>
<li>Load/stress testing</li>
<li>Monitoring</li>
</ul>Tools than can be used for Web Services Testing 
<ul><li>SOAPUI</li>
<li>LOADUI</li>
</ul>Challenges in testing web services 
Like all software, web services need to be tested. Like websites, they are often highly visible, so they need to be very robust.  Some example of challenge’s are 
<ul><li>No Graphical User Interface available to test web services</li>
<li>Troubleshooting of issues not an easy job</li>
<li>Security Issues</li>
<li>Performance Issues</li>
</ul>In next blog we will discuss these testing techniques in details. Your feedback will be highly appreciated 
 
Reference:  “<a href="http://www.w3schools.com/">w3schools</a>“</div>

System Integration Testing Part I

In this blog I will discuss how to perform web services testing. To test web services one should know about What is XML What are web s...

System Integration Testing Part IV

System Integration Testing Part III

System Integration Testing

Web Services Testing Part III

System Integration Testing Part II

System Integration Testing Part I

Popular Posts

Archives

Categories