TechClimbs Blog

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

0 Manual Testing, Software Testing, System Integration Testing

(adsbygoogle = window.adsbygoogle || …

Microsoft Certifications for QA professionals

0 Certifications for QA, Microsoft, Software Testing

<div dir="ltr" style="text-align: left;" trbidi="on"><h1>Overview</h1>Microsoft has reinvented its certification program to validate a broader and deeper set of skills on the latest technologies.Microsoft also introduced certification for QA professionals. 
This certification is helpful for 
<ul><li>Automation Testers using Visual Studio</li>
<li>ALM Specialist</li>
</ul><img alt="" class="confluence-embedded-image CSS_LIGHTBOX_SCALED_IMAGE_IMG confluence-external-resource" data-mce-src="https://infosharehouse.files.wordpress.com/2015/10/c2dba-mcsd.png" src="https://infosharehouse.files.wordpress.com/2015/10/c2dba-mcsd.png" /> 
 
<h2 id="ctl00_msl2LASOExamID0EAAABA_headingExamNumber">Exam 70-496: Administering Visual Studio Team Foundation Server 2012</h2><h2 id="ctl00_msl2LASOExamID0EAAABA_headingExamNumber">Please visit for details :<a data-mce-href="http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-496#fbid=rm1v8JbQXB4" href="http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-496#fbid=rm1v8JbQXB4"> http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-496#fbid=rm1v8JbQXB4</a> </h2><h3 id="ctl00_msl2LASOExamID0EAAABA_headingExamNumber">Exam 70-497:Software Testing with Visual Studio 2012</h3><h3 id="ctl00_msl2LASOExamID0EAAABA_headingExamNumber"> Please visit for details: <a data-mce-href="http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-497#fbid=rm1v8JbQXB4" href="http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-497#fbid=rm1v8JbQXB4">http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-497#fbid=rm1v8JbQXB4</a></h3><h2 id="ctl00_msl2LASOExamID0EAAABA_headingExamTitle">Exam 70-498: Delivering Continuous Value with Visual Studio 2012 Application Lifecycle Management</h2><h3 id="ctl00_msl2LASOExamID0EAAABA_headingExamNumber"> Please visit for details: <a data-mce-href="http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-498#fbid=rm1v8JbQXB4" href="http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-498#fbid=rm1v8JbQXB4">http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-498#fbid=rm1v8JbQXB4</a></h3><h3 id="ctl00_msl2LASOExamID0EAAABA_headingExamNumber">How to register for Microsoft exam:</h3>Visit : <a data-mce-href="http://www.register.prometric.com/" href="http://www.register.prometric.com/">http://www.register.prometric.com</a> 
Exam Fee for each paper: 80$ 
<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> 
For more details , please visit the official web site of Microsoft (<a data-mce-href="https://www.microsoft.com/learning/en-us/mcsd-application-lifecycle-management.aspx" href="https://www.microsoft.com/learning/en-us/mcsd-application-lifecycle-management.aspx">https://www.microsoft.com/learning/en-us/mcsd-application-lifecycle-management.aspx</a>) 
Visit : <a href="http://www.register.prometric.com/">http://www.register.prometric.com</a> 
Exam Fee for each paper: 80$ 
Fro registration steps please visit  blog <a href="http://www.proinformationtech.blogspot.com/2013/02/istqb-foundation-levelctfl-exam.html" target="_blank">" ISTQB Foundation Level(CTFL) Exam Preparation" </a> 
and select Microsoft option other than BCS. 
  </div>

Microsoft Certifications for QA professionals

0 Certifications for QA, Microsoft, Software Testing

OverviewMicrosoft has reinvented its certification program to validate a broader and deeper set of skills on the latest technologies.Microsoft also introduced certification for QA professionals. Th…

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

0 Manual Testing, Software Testing, System Integration Testing

v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} In Part I and Part II we discussed about web services…

How to use your QA Skills in a Scrum-Based Project Part I

0 Agile Testing, Manual Testing, Software 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> 
<h1>What is Agile Development?</h1>Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle (<a data-mce-href="http://en.wikipedia.org/wiki/Agile_software_development" href="http://en.wikipedia.org/wiki/Agile_software_development">Wikipedia</a>). 
Before the Agile methodology, methods of software development tended to be slow, bureaucratic and inconsistent. This created the need for a more adaptive method of software development.   A large number of IT project failures lead toward a new way of thinking and delivering the project:  IT teams around the world adapting the new ideas and getting them to work and deliver the success to their respective clients. 
Agile methodologies encourage teamwork, self-organization, and accountability. Most agile development teams comprise 5-9 team members and a single customer representative. These teams normally work in a single open office to promote teamwork and cooperation. The following are few agile methods currently being used in the IT industry. 
<ul><li>Scrum</li>
<li>Kanban</li>
<li>Agile Modeling</li>
<li>Agile Unified Process (AUP)</li>
<li>Agile Data Method</li>
<li>DSDM</li>
<li>Essential Unified Process (EssUP)</li>
<li>Extreme Programming (XP)</li>
<li>Feature Driven Development (FDD)</li>
<li>Getting Real</li>
<li>Open Unified Process (OpenUP)</li>
<li>Lean Software Development</li>
</ul><h1>What is Scrum?</h1>Scrum is an iterative and incremental agile software development framework for managing software projects and product or application development. 
<ul><ul><li>Scrum can be defined as “A small number of people with complementary skills who are committed to a common purpose, performance goals, and approach for which they hold themselves mutually accountable” (Katzenbach and Smith, The Wisdom of Teams)</li>
<li>Scrum, as a process, is incremental. Each increment is called sprint and each sprint may last for up to four weeks</li>
<li>In order to work as Scrum suggests, the entire team must possess solid knowledge in analysis design, implementation, testing and documentation.</li>
<li>Prior to the sprint, there is a sprint planning meeting where the user determines what features should be developed and followed in the next sprint.</li>
</ul></ul>The following are the major areas of Scrum 
<ul><ul><ul><li> Artifacts in Scrum</li>
<li>Scrum Roles</li>
<li>Scrum Meetings</li>
</ul></ul></ul>The next section is dedicated to providing more details on each of these areas. 
Please note that in this document, the focus is to introduce the audience to the basic terms and definitions only.  Please refer to the ‘reference’ section below for further details. 
<h2>Artifacts in Scrum</h2>In Scrum, there are many artifacts produced and used by the team.  However, the following three artifacts play a key role in overall communication and definition of the requirements and understanding. 
<ul><ul><ul><li>Product Backlog</li>
<li>Sprint Backlog</li>
<li>Burn down Chart</li>
</ul></ul></ul><h3>Product Backlog</h3>The product backlog is a prioritized features list, containing short descriptions of all functionality desired in the product. Typically, a Scrum team and its product owner begin by writing down everything they can easily think of. This is almost always more than enough for a first sprint. The Scrum product backlog is then allowed to grow and change as more is learned about the product and its customers. 
<ul><ul><ul><li>List of task that needs to be done</li>
<li>Requirements are defined in the form of user stories.</li>
<li>The product owner sets the Priority and Business Value for each user story.</li>
<li>Priority means how “important & urgent” a feature is for the business users and how other features are depending on it</li>
<li>“Business Value” means the overall impact of the completed feature on the business process.</li>
<li>Anyone can contribute</li>
<li>Maintained and posted visibly</li>
<li>An example would be, "As a shopper, I can review the items in my shopping cart before checking out so that I can see what I've already selected."</li>
</ul></ul></ul>A typical product backlog comprises the following different types of items: 
<ul><ul><ul><li>Features</li>
<li>Bugs</li>
<li>Technical work</li>
<li>Knowledge acquisition</li>
</ul></ul></ul>Please note that there might be some other item types which can be included in this list. However this is sufficient to start. Feel free to add more as needed. 
<h3>Sprint Backlog</h3>The sprint backlog is the list of tasks identified by the Scrum Team during sprint planning. During sprint planning, the team selects some number of product backlog items, usually in the form of user stories, and identifies the tasks necessary to complete each user story. Most teams also estimate how many hours each task will take someone on the team to complete. 
<ul><ul><ul><li>List of highest priority task from the product backlog</li>
<li>Tasks are estimated in hours, usually 1-16</li>
<li>Task with more than 16 hours are broken down later</li>
<li>Estimated work remaining is updated daily</li>
<li>If the work is unclear, define a Sprint Backlog with a larger amount of time, then break it down later</li>
<li>Update work remaining as more is known and as items are worked</li>
</ul></ul></ul><h3>Burn Down Chart</h3>On a Scrum project, the team tracks its progress against a release plan by updating a release burn down chart at the end of each sprint. 
<ul><ul><ul><li>Work remaining on each task is reported during the Daily Scrum meeting, and updated by the Scrum Master</li>
<li>Notice that this is different than measuring how many hours have been spent on a task</li>
<li>Time reporting is not a part of Scrum</li>
<li>Scrum is results oriented, not effort driven. The team reports how time is needed to complete the task rather than how much has been spent.</li>
</ul></ul></ul><h2>Scrum Roles</h2>Scrum suggests three main roles for the execution of a successful project. 
<ul><ul><ul><li>Product Owner – When working with Scrum, the product owner is typically a project's key stakeholder. It is important that this person has a vision of what they wish to build and that he or she is able to convey that vision to the Scrum team.</li>
<li>Scrum Master – The Scrum Master is responsible for making sure a Scrum team lives by the values and practices of Scrum. The Scrum Master is often considered a coach for the team, helping the team do the best work it possibly can. The Scrum Master can also be thought of as a process owner for the team, creating a balance with the project's key stakeholder, who is referred to as the Product Owner.</li>
<li>Team – A Scrum team does not include any of the traditional software engineering roles such as programmer, designer, tester, or architect. Everyone on the project works together to accomplish the work they have collectively committed to complete within a sprint.</li>
</ul></ul></ul>The following diagram describes each of these roles along with their respective responsibilities and functions. 
<a data-mce-href="http://infosharehouse.files.wordpress.com/2013/01/untitled.png" href="http://infosharehouse.files.wordpress.com/2013/01/untitled.png"><img alt="Untitled" class="aligncenter size-medium wp-image-45" data-mce-src="http://infosharehouse.files.wordpress.com/2013/01/untitled.png?w=300" height="360" src="http://infosharehouse.files.wordpress.com/2013/01/untitled.png?w=300" width="534" /></a></div>