tag:blogger.com,1999:blog-63875404709505264492024-03-28T15:05:08.219+05:30Software Testing Tutorials - Manual and Automation Questions AnswersSoftware Testing Tutorials, Manual, Automation Testing Interview Questions Answers are available.Unknownnoreply@blogger.comBlogger68125tag:blogger.com,1999:blog-6387540470950526449.post-75511623269069593022013-07-15T19:12:00.000+05:302016-07-28T22:12:58.668+05:30Compatibility Testing - Definition, Types, Tools Used<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: left;">
What is Compatibility Testing</h2>
<div style="text-align: justify;">
<ul>
<li>Compatibility testing is to check whether your software is capable of running on different hardware, operating systems, applications , network environments or mobile devices.</li>
<li>Compatibility Testing is a type of the Non-functional testing</li>
<li>Initial phase of compatibility testing is to define the set of environments or platforms the application is expected to work on.</li>
<li>Tester should have enough knowledge on the platforms / software / hardware to understand the expected application behavior under different configurations.</li>
<li>Environment needs to be set-up for testing with different platforms, devices, networks to check whether your application runs well under different configurations.</li>
<li>Report the bugs .Fix the defects. Re-test to confirm defect fixing.</li>
</ul>
<div>
<br /></div>
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjFdYECRAXQrx7HVKWCP8twWHsX9kxNPxmlUnOJnv1-5Z9EPa3Eh2zCx6ovBlk8ltaoeCcprwIWlAGOhIWv3O7y7Xg-CaCvfM7dVVDvfIAn0qKKatRVFGIxIewLmLkK5rvHjG93jllqu7Qi/s800/compatibility-testing.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="compatibility-testing" border="0" height="200" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjFdYECRAXQrx7HVKWCP8twWHsX9kxNPxmlUnOJnv1-5Z9EPa3Eh2zCx6ovBlk8ltaoeCcprwIWlAGOhIWv3O7y7Xg-CaCvfM7dVVDvfIAn0qKKatRVFGIxIewLmLkK5rvHjG93jllqu7Qi/s400/compatibility-testing.png" title="compatibility-testing" width="400" /></a></div>
<h2 style="text-align: left;">
</h2>
<h2 style="text-align: left;">
Types of Compatibility testing :</h2>
<div style="text-align: justify;">
<ul>
<li>Hardware</li>
<li>Operating Systems</li>
<li>Software</li>
<li>Network</li>
<li>Browser</li>
<li>Devices</li>
<li>Mobile</li>
<li>Versions of the software</li>
</ul>
</div>
<div style="text-align: justify;">
Let’s look into compatibility testing types briefly.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b><u>Hardware</u></b> : It checks software to be compatible with different hardware configurations .</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b><u>Operating Systems</u></b>: It checks your software to be compatible with different Operating Systems like Windows , Unix , Mac OS etc.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b><u>Software</u></b>: It checks your developed software to be compatible with other software’s.For example: MS Word application should be compatible with other softwares like MS Outlook,MS Excel , VBA etc.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b><u>Network</u></b>: Evaluation of performance of system In network with varying parameters such as Bandwidth, Operating speed, Capacity. It also checks application in different networks with all parameters mentioned earlier.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b><u>Browser</u></b>: It checks compatibility of your website with different browsers like Firefox , Google Chrome , Internet Explorer etc.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b><u>Devices</u></b> : It checks compatibility of your software with different devices like USB port Devices, Printers and Scanners, Other media devices and Blue tooth.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b><u>Mobile</u></b>: Checking you software is compatible with mobile platforms like Android , iOS etc.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b><u>Versions of the software</u></b>: It is verifying you software application to be compatible with different versions of software.For instance checking your Microsoft Word to be compatible with Windows 7, Windows 7 SP1 , Windows 7 SP 2 , Windows 7 SP 3.</div>
<div style="text-align: justify;">
<br /></div>
<div>
There are two types of version checking.<br />
<h4>
<ul style="text-align: left;">
<li>Types of Version Checking</li>
</ul>
</h4>
<ul style="text-align: left;"><ul>
<li>Backward compatibility Testing</li>
<li>Forward compatibility Testing</li>
</ul>
</ul>
<div>
<b><u>Backward compatibility Testing </u>:</b> is to verify the behavior of the developed hardware/software with the older versions of the hardware/software.</div>
<div>
<br /></div>
<div>
<b><u>Forward compatibility Testing</u></b> : is to verify the behavior of the developed hardware/software with the newer versions of the hardware/software.</div>
<h3 style="text-align: left;">
Tools for compatibility testing</h3>
<div>
<ul style="text-align: left;">
<li>Adobe Browser Lab – Browser Compatibility Testing - This tool helps check your application in different browsers.</li>
<li>Secure Platform – Hardware Compatibility tool - This tools includes necessary drivers for a specific hardware platform and it provides information on tool to check for CD burning process with CD burning tools.</li>
<li>Virtual Desktops - Operating System Compatibility - This is used to run the applications in multiple operating systems as virtual machines. N Number of systems can be connected and compare the results.</li>
</ul>
</div>
</div>
</div>
Unknownnoreply@blogger.com38tag:blogger.com,1999:blog-6387540470950526449.post-68556207237811079922013-07-08T18:53:00.000+05:302013-07-08T18:53:00.148+05:30Adhoc Testing - Definition, Types, Advantages, Disadvantages<div dir="ltr" style="text-align: left;" trbidi="on">
<div style="text-align: justify;">
<h2>
Adhoc Testing</h2>
</div>
<div style="text-align: justify;">
<h3>
Definition :</h3>
</div>
<div style="text-align: justify;">
</div>
<ul>
<li>Adhoc testing is an informal testing type with an aim to break the system.</li>
<li>This testing is usually an unplanned activity.</li>
<li>It does not follow any test design techniques to create test cases. In fact is does not create test cases altogether!</li>
<li>It is primarily performed if the knowledge of testers in the system under test is very high.</li>
<li>Testers randomly test the application without any test cases or any business requirement document.</li>
<li>Adhoc testing can be achieved with the testing technique called Error Guessing.</li>
<li>Error guessing can be done by the people having enough experience on the system to “geuss” the most likely source of errors.</li>
</ul>
<div>
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgdv62grcJdI8fzJ9cvf9NS8bZsbV6Zx6R6NblAZ_xBvDKzkYkKeD_CD9wtk1KImJGWkIpjSwkcADFwNpylyjdT6XV4PjbMqLXj26E_wMmBMLGZmc-zEUhpXBmWV8szUYZvZ3t07sHldoaz/s360/Adhoc-testing-defintion.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Adhoc-testing-defintion" border="0" height="192" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgdv62grcJdI8fzJ9cvf9NS8bZsbV6Zx6R6NblAZ_xBvDKzkYkKeD_CD9wtk1KImJGWkIpjSwkcADFwNpylyjdT6XV4PjbMqLXj26E_wMmBMLGZmc-zEUhpXBmWV8szUYZvZ3t07sHldoaz/s320/Adhoc-testing-defintion.jpg" title="Adhoc-testing-defintion" width="320" /></a></div>
<div>
<br /></div>
<br />
<hr />
<h3 style="text-align: left;">
Types of adhoc testing</h3>
<div style="text-align: justify;">
</div>
<ol>
<li>Buddy Testing</li>
<li>Pair testing</li>
<li>Monkey Testing</li>
</ol>
<h4 style="text-align: left;">
Buddy Testing</h4>
<div style="text-align: justify;">
Two buddies mutually work on identifying defects in the same module. Mostly one buddy will be from development team and another person will be from testing team. Buddy testing helps the testers develop better test cases and development team can also make design changes early. This testing usually happens after unit testing completion.</div>
<h4 style="text-align: left;">
Pair testing</h4>
<div style="text-align: justify;">
Two testers are assigned modules, share ideas and work on the same machines to find defects. One person can execute the tests and another person can take notes on the findings. Roles of the persons can be a tester and scriber during testing.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Buddy testing is combination of unit and system testing together with developers and testers but Pair testing is done only with the testers with different knowledge levels.(Experienced and non-experienced to share their ideas and views)</div>
<h4 style="text-align: left;">
Monkey Testing</h4>
<div style="text-align: justify;">
Randomly test the product or application without test cases with a goal to break the system</div>
<hr />
<h3 style="text-align: left;">
<u>Advantages of Adhoc Testing :</u></h3>
<div style="text-align: justify;">
</div>
<ul>
<li>Adhoc Testing saves lot of time as it doesn’t require elaborate test planning , documentation and test case design.</li>
<li>It checks for the completeness of testing and find more defects then planned testing.</li>
</ul>
<h3 style="text-align: left;">
<u>Disadvantages of Adhoc Testing : </u></h3>
<div style="text-align: justify;">
</div>
<ul>
<li>This testing requires no documentation/ planning /process to be followed. Since this testing aims at finding defects through random approach, without any documentation, defects will not be mapped to test cases. Hence, sometimes, it is very difficult to reproduce the defects as there are no test-steps or requirements mapped to it.</li>
</ul>
</div>
Unknownnoreply@blogger.com20tag:blogger.com,1999:blog-6387540470950526449.post-38916602528077898332013-07-01T15:56:00.000+05:302013-07-01T15:58:21.779+05:30Define Equivalence Partitioning with Examples<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: left;">
<span style="font-family: inherit;">Define Equivalence Partitioning with Examples</span></h2>
<div style="text-align: justify;">
<h2>
<span style="font-family: inherit;">What is </span>Equivalence Partitioning ?</h2>
</div>
<div style="text-align: justify;">
<span style="font-family: inherit;">The technique is to divide (i.e. to partition) a set of test conditions into groups or sets that can be considered the same (i.e. the system should handle them equivalently), hence ‘equivalence partitioning’. Equivalence partitions are also known as equivalence classes – the two terms mean exactly the same thing.</span></div>
<h3 style="text-align: left;">
<span style="font-family: inherit;">Example 1 for Equivalence partitioning :</span></h3>
<div style="text-align: justify;">
<span style="font-family: inherit;">Test cases for input box accepting numbers between 1 and 1000 using Equivalence Partitioning:</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">1) One input data class with all valid inputs. Pick a single value from range 1 to 1000 as a valid test case. If you select other values between 1 and 1000 then result is going to be same. So one test case for valid input data should be sufficient.</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">2) Input data class with all values below lower limit. I.e. any value below 1, as a invalid input data test case.</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">3) Input data with any value greater than 1000 to represent third invalid input class.</span></div>
<hr />
<h3 style="text-align: left;">
<span style="font-family: inherit; text-align: left;">Example 2 for Equivalence partitioning :</span></h3>
<div style="text-align: justify;">
<span style="font-family: inherit;">For example in a savings Bank account,</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">3% rate of interest is given if the balance in the account is in the range of $0 to $100,</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">5% rate of interest is given if the balance in the account is in the range of $100 to $1000,</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">And 7% rate of interest is given if the balance in the account is $1000 and above.</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">We would initially identify three valid equivalence partitions and one invalid partition as shown below. [Click on the image for Zoom view]</span><br />
<span style="font-family: inherit;"><br /></span>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEisFO8AYu5WJS3KoFIU_Cnyt0CiOomHMVP_6I-D0yADzVIqSEmJfWqGfVH7GFNSKTpWteTG5aN_iay2opVc6-rWWPaB8Gdctb3-sXXntRW50o-LUEGSZX2YgoGRuwPThsZqsjDxrP3j7ehS/s611/Equivalence-partitioning.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Equivalence-partitioning" border="0" height="52" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEisFO8AYu5WJS3KoFIU_Cnyt0CiOomHMVP_6I-D0yADzVIqSEmJfWqGfVH7GFNSKTpWteTG5aN_iay2opVc6-rWWPaB8Gdctb3-sXXntRW50o-LUEGSZX2YgoGRuwPThsZqsjDxrP3j7ehS/s400/Equivalence-partitioning.jpg" title="Equivalence-partitioning" width="400" /></a></div>
<span style="font-family: inherit;"><br /></span></div>
<hr />
<h3 style="text-align: left;">
<span style="font-family: inherit;">Example 3 for Equivalence partitioning :</span></h3>
<div style="text-align: justify;">
<span style="font-family: inherit;">A store in city offers different discounts depending on the purchases made by the individual. In order to test the software that calculates the discounts, we can identify the ranges of purchase values that earn the different discounts. For example, if a purchase is in the range of $1 up to $50 has no discounts, a purchase over $50 and up to $200 has a 5% discount, and purchases of $201 and up to $500 have a 10% discounts, and purchases of $501 and above have a 15% discounts.</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">Now we can identify 4 valid equivalence partitions and 1 invalid partition as shown below:</span></div>
<div style="text-align: justify;">
<br /></div>
<table border="1" cellpadding="0" cellspacing="0" style="text-align: justify;">
<tbody>
<tr>
<td><b><span style="font-family: inherit;">Invalid Partition</span></b></td>
<td><b><span style="font-family: inherit;">Valid Partition(No Discounts)</span></b></td>
<td><b><span style="font-family: inherit;">Valid Partition(5%)</span></b></td>
<td><b><span style="font-family: inherit;">Valid Partition(10%)</span></b></td>
<td><b><span style="font-family: inherit;">Valid Partition(15%)</span></b></td>
</tr>
<tr>
<td><span style="font-family: inherit;">$0.01</span></td>
<td><span style="font-family: inherit;">$1-$50</span></td>
<td><span style="font-family: inherit;">$51-$200</span></td>
<td><span style="font-family: inherit;">$201-$500</span></td>
<td><span style="font-family: inherit;">$501-Above</span></td>
</tr>
</tbody>
</table>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Happy Sharing! :)</div>
</div>
Unknownnoreply@blogger.com7tag:blogger.com,1999:blog-6387540470950526449.post-74225230282633690002013-07-01T15:40:00.001+05:302013-07-01T15:58:59.666+05:30Define Boundary Value Analysis with Examples<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: justify;">
<u>
Define Boundary Value Analysis with Examples :</u></h2>
<h2 style="text-align: justify;">
<span style="font-family: inherit;">What is Boundary Value Analysis ?</span></h2>
<div style="text-align: justify;">
<span style="font-family: inherit;">A test data selection technique in which values are chosen to lie along data extremes. Boundary values include maximum, minimum, just inside/outside boundaries, typical values, and error values. The hope is that, if a systems works correctly for these special values then it will work correctly for all values in between.</span></div>
<h3 style="text-align: left;">
<span style="font-family: inherit;">
Example 1 for Boundary Value Analysis : </span></h3>
<div style="text-align: justify;">
<span style="font-family: inherit;">Password field accepts minimum 6 characters and maximum 12 characters. [Range is 6-12]</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">Write Test Cases considering values from Valid region and each Invalid Region and Values which define exact boundary.</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">We need to execute 5 Test Cases for our Example 1.</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">1. Consider password length less than 6</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">2. Consider password of length exactly 6</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">3. Consider password of length between 7 and 11</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">4. Consider password of length exactly 12</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">5. Consider password of length more than 12 </span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">Note : 1st and 5th Test Cases are considered for Negative Testing</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;"><br /></span></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh2Q06P7vrBZRHR6h01dEVzuvZQmxhYjI80oWiyJg-nXuYElXg_-KJHFNkTLMyaQN7GyiBEOnCx8t30H0zrGzvWOvPG-dD0N-a7GS-p7qNylgoUMfL2eNgauUpSX7Z2OTrEfQEUWtfv236R/s640/boundary-value-analysis.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><span style="font-family: inherit;"><img alt="Boundary-Value-Analysis-Examples" border="0" height="150" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh2Q06P7vrBZRHR6h01dEVzuvZQmxhYjI80oWiyJg-nXuYElXg_-KJHFNkTLMyaQN7GyiBEOnCx8t30H0zrGzvWOvPG-dD0N-a7GS-p7qNylgoUMfL2eNgauUpSX7Z2OTrEfQEUWtfv236R/s400/boundary-value-analysis.jpg" title="Boundary-Value-Analysis-Examples" width="400" /></span></a></div>
<div style="text-align: justify;">
<span style="font-family: inherit;"><br /></span></div>
<hr />
<h3 style="text-align: left;">
<span style="font-family: inherit;"><b>Example 2 for </b>Boundary Value Analysis<b> :</b></span></h3>
<div style="text-align: justify;">
<span style="font-family: inherit;">Test cases for input box accepting numbers between 1 and 1000 using Boundary value analysis:</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">1) Test cases with test data exactly as the input boundaries of input domain i.e. values 1 and 1000 in our case.</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">2) Test data with values just below the extreme edges of input domains i.e. values 0 and 999.</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">3) Test data with values just above the extreme edges of input domain i.e. values 2 and 1001.</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;"><br /></span></div>
<hr />
<h3 style="text-align: left;">
<span style="font-family: inherit;"><b>Example 3 for </b>Boundary Value Analysis<b> :</b></span></h3>
<div style="text-align: justify;">
<span style="font-family: inherit;">Name text box which allows 1-30 characters. So in this case writing test cases by entering each character once will be very difficult so then will choose boundary value analysis.</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">So in this case at max 5 test cases will come:</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">Test case1: minimum -1 character: Validating not entering anything in text box</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">Test case2: minimum +1 character: Validating with only one char</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">Test case3: maximum -1 character: Validating with 29 chars</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">Test case4: minimum +1 character: Validating with 31 characters</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">Test case1: any one middle number: validating with 15 chars</span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: inherit;">Happy Sharing!</span></div>
</div>
Unknownnoreply@blogger.com10tag:blogger.com,1999:blog-6387540470950526449.post-6115574575721768592013-06-30T01:49:00.000+05:302013-07-06T15:29:23.174+05:30What Is System Testing<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: justify;">
What Is System Testing</h2>
<div style="text-align: justify;">
Testing the behavior of the whole software/system as defined in software requirements specification (SRS) is known as system testing, its main focus is to verify that the customer requirements are fulfilled.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
System testing is done after integration testing is complete. </div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
In system testing, there are two type of testing</div>
<div style="text-align: justify;">
<a href="http://www.jobsnewstoday.com/2013/05/functional-testing.html" target="_blank">1. Functionality testing</a></div>
<div style="text-align: justify;">
<a href="http://www.jobsnewstoday.com/2013/05/non-functional-testing.html" target="_blank">2.Non-functionality testing</a></div>
<div style="text-align: justify;">
<br /></div>
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEivFfNURQe4L41p09qQ55ZA1AqOFynY4P93bY8runCTyER0Vc0A1DetWe15emkNUt8MPcwHTEfU_AtiaIyPFCPbjQDTUyCokPLBY_V6ZpWBe19BTKx5wELnQ-44KLe0Z_H3oSuzgtxLedxZ/s1600/system-testing.bmp" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img alt="System Testing" border="0" height="390" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEivFfNURQe4L41p09qQ55ZA1AqOFynY4P93bY8runCTyER0Vc0A1DetWe15emkNUt8MPcwHTEfU_AtiaIyPFCPbjQDTUyCokPLBY_V6ZpWBe19BTKx5wELnQ-44KLe0Z_H3oSuzgtxLedxZ/s400/system-testing.bmp" title="System Testing" width="400" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;"><b>Click on the image for zoom view</b></td></tr>
</tbody></table>
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
<div style="text-align: justify;">
Functionality testing is to test whether application functioning as per requirement or not.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Non-functionality testing are several types :</div>
<div style="text-align: justify;">
</div>
<ul>
<li>Load,</li>
<li>Stress,</li>
<li>Performance,</li>
<li>Reliability,</li>
<li>Security,</li>
<li>Usability</li>
<li>Configuration,</li>
<li>Compatibility (forward & Backward),</li>
<li>Scalability, Etc...</li>
</ul>
<br />
<div>
<blockquote class="tr_bq" style="text-align: justify;">
Click on the links to read more about <a href="http://www.jobsnewstoday.com/2013/05/functional-testing.html" target="_blank">Functionality testing</a> and <a href="http://www.jobsnewstoday.com/2013/05/non-functional-testing.html" target="_blank">Non-functionality testing</a></blockquote>
</div>
</div>
Unknownnoreply@blogger.com51tag:blogger.com,1999:blog-6387540470950526449.post-91808329268769751002013-06-27T01:55:00.000+05:302013-07-06T15:28:34.508+05:30 Different Types Of White Box Testing<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: justify;">
Different Types Of White Box Testing</h2>
<h3 style="text-align: justify;">
Path Testing :</h3>
<div style="text-align: justify;">
Taking up each and every individual path through which the flow of code taken place.</div>
<h3 style="text-align: justify;">
Loop Testing :</h3>
<div style="text-align: justify;">
A Piece of code executing continuously until the condition becomes false and testing whether it is proper or not.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Ex: For (Loop=1; Loop<=10; Loop++)</div>
<div style="text-align: justify;">
{</div>
<div style="text-align: justify;">
------</div>
<div style="text-align: justify;">
------</div>
<div style="text-align: justify;">
}</div>
<div style="text-align: justify;">
<a name='more'></a></div>
<h3 style="text-align: justify;">
Condition Testing :</h3>
<div style="text-align: justify;">
The process of condition testing ensures that a controlling expression has been adequately exercised whilst the software is under test by constructing a constraint set for every expression and then ensuring that every member on the constraint set is included in the values which are presented to the expression. </div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
if ( cond1 AND cond2)</div>
<div style="text-align: justify;">
{</div>
<div style="text-align: justify;">
stmt1;</div>
<div style="text-align: justify;">
}</div>
<div style="text-align: justify;">
else</div>
<div style="text-align: justify;">
{</div>
<div style="text-align: justify;">
stmt2;</div>
<div style="text-align: justify;">
}</div>
<div style="text-align: justify;">
<br /></div>
<table style="text-align: justify;"><colgroup></colgroup>
<tbody>
<tr>
<th><div style="text-align: center;">
Cond1</div>
</th>
<th><div style="text-align: center;">
Cond2</div>
</th>
<th><div style="text-align: center;">
AND</div>
</th>
<th><div style="text-align: center;">
OR</div>
</th>
</tr>
<tr>
<td>F</td>
<td>F</td>
<td>Stmt2</td>
<td>Stmt2</td>
</tr>
<tr>
<td>F</td>
<td>T</td>
<td>Stmt2</td>
<td>Stmt1</td>
</tr>
<tr>
<td>T</td>
<td>F</td>
<td>Stmt2</td>
<td>Stmt1</td>
</tr>
<tr>
<td>T</td>
<td>T</td>
<td>Stmt1</td>
<td>Stmt1</td>
</tr>
</tbody>
</table>
<h3 style="text-align: left;">
Performance perceptive :</h3>
<div style="text-align: justify;">
1) If you are using AND condition, as the result is fail for 3 cases, it is better to write failure condition first.</div>
<div style="text-align: justify;">
2) If you are using OR , True condition should be written first.</div>
<div style="text-align: justify;">
When we have multiple conditions we need to use switch case rather than using if else if.</div>
</div>
Unknownnoreply@blogger.com4tag:blogger.com,1999:blog-6387540470950526449.post-18209877407542395362013-06-24T02:05:00.000+05:302013-07-06T15:28:42.891+05:30Bug Life Cycle Or Defect Life Cycle In Software Testing<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: justify;">
Bug Life Cycle Or Defect Life Cycle In Software Testing</h2>
<div style="text-align: justify;">
Defect life cycle is a cycle which a defect goes through during its lifetime. It starts when defect is found and ends when a defect is closed, after ensuring it’s not reproduced. Defect life cycle is related to the bug found during testing.</div>
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiF-V-MevC-3Qr7ng-2-59ydZxDegbYqlETedOR65PALAuICt4j4r_vgmVY0UEowfNySsMRHzOOVNWMyta63an7qz4QvaTzACXNDGSegWOa2JvZZNfouT7EMVTwF1fgYaXiQp7ki2SXnu_L/s1600/Bug-life-cycle1.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img alt="Bug-life-cycle" border="0" height="300" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiF-V-MevC-3Qr7ng-2-59ydZxDegbYqlETedOR65PALAuICt4j4r_vgmVY0UEowfNySsMRHzOOVNWMyta63an7qz4QvaTzACXNDGSegWOa2JvZZNfouT7EMVTwF1fgYaXiQp7ki2SXnu_L/s320/Bug-life-cycle1.jpg" title="Bug-life-cycle" width="320" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;"><b>Click on the image for zoom view</b></td></tr>
</tbody></table>
<br />
<a name='more'></a><div style="text-align: justify;">
<br /></div>
<br />
<div style="text-align: justify;">
The bug has different states in the Life Cycle. The Life cycle of the bug can be shown diagrammatically as follows:</div>
<br />
<ol style="text-align: left;">
<li style="text-align: justify;"><b>New</b>: When a defect is logged and posted for the first time. It’s state is given as new.</li>
<li style="text-align: justify;"><b>Assigned</b>: After the tester has posted the bug, the lead of the tester approves that the bug is genuine and he assigns the bug to corresponding developer and the developer team. It’s state given as assigned.</li>
<li style="text-align: justify;"><b>Open</b>: At this state the developer has started analyzing and working on the defect fix.</li>
<li style="text-align: justify;"><b>Fixed</b>: When developer makes necessary code changes and verifies the changes then he/she can make bug status as ‘Fixed’ and the bug is passed to testing team.</li>
<li style="text-align: justify;"><b>Pending retest</b>: After fixing the defect the developer has given that particular code for retesting to the tester. Here the testing is pending on the testers end. Hence its status is pending retest.</li>
<li style="text-align: justify;"><b>Retest</b>: At this stage the tester do the retesting of the changed code which developer has given to him to check whether the defect got fixed or not.</li>
<li style="text-align: justify;"><b>Verified</b>: The tester tests the bug again after it got fixed by the developer. If the bug is not present in the software, he approves that the bug is fixed and changes the status to “verified”.</li>
<li style="text-align: justify;"><b>Reopen</b>: If the bug still exists even after the bug is fixed by the developer, the tester changes the status to “reopened”. The bug goes through the life cycle once again.</li>
<li style="text-align: justify;"><b>Closed</b>: Once the bug is fixed, it is tested by the tester. If the tester feels that the bug no longer exists in the software, he changes the status of the bug to “closed”. This state means that the bug is fixed, tested and approved.</li>
<li style="text-align: justify;"><b>Duplicate</b>: If the bug is repeated twice or the two bugs mention the same concept of the bug, then one bug status is changed to “duplicate“.</li>
<li style="text-align: justify;"><b>Rejected</b>: If the developer feels that the bug is not genuine, he rejects the bug. Then the state of the bug is changed to “rejected”.</li>
<li style="text-align: justify;"><b>Deferred</b>: The bug, changed to deferred state means the bug is expected to be fixed in next releases. The reasons for changing the bug to this state have many factors. Some of them are priority of the bug may be low, lack of time for the release or the bug may not have major effect on the software. </li>
<li style="text-align: justify;"><b>Not a bug</b>: The state given as “Not a bug” if there is no change in the functionality of the application. For an example: If customer asks for some change in the look and field of the application like change of color of some text then it is not a bug but just some change in the looks of the application.</li>
</ol>
</div>
Unknownnoreply@blogger.com6tag:blogger.com,1999:blog-6387540470950526449.post-77040523708945634542013-06-21T05:06:00.000+05:302013-07-06T15:28:21.177+05:30Automation Testing Interview Questions<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: center;">
Automation Testing Interview Questions</h2>
<ol style="text-align: left;">
<li style="text-align: justify;">What are principles of good testing scripts for automation?</li>
<li style="text-align: justify;">What are some of the common misconceptions during implementation of an automated testing tools for the first time?</li>
<li style="text-align: justify;">What are the limitations of automating software testing?</li>
<li style="text-align: justify;">What are the main attributes of test automation?</li>
<li style="text-align: justify;">Can test automation improve test effectiveness?<a name='more'></a></li>
<li style="text-align: justify;">How to find that tools work well with your existing system?</li>
<li style="text-align: justify;">How to find that tools work well with your existing system?</li>
<li style="text-align: justify;">How you will evaluate the tool for test automation?</li>
<li style="text-align: justify;">What are main benefits of test automation?</li>
<li style="text-align: justify;">How will you choose a tool for test automation?</li>
<li style="text-align: justify;">How you will describe testing activities?</li>
<li style="text-align: justify;">Can the activities of test case design be automated?</li>
<li style="text-align: justify;">What automating testing tools are you familiar with?</li>
<li style="text-align: justify;">What could go wrong with test automation?</li>
<li style="text-align: justify;">What testing activities you may want to automate?</li>
<li style="text-align: justify;">What tools are available for support of testing during software development life cycle?</li>
<li style="text-align: justify;">Describe some problem that you had with automating testing tool.</li>
<li style="text-align: justify;">Describe some problem that you had with automating testing tool.</li>
<li style="text-align: justify;">Does automation replace manual testing?</li>
<li style="text-align: justify;">How did you use automating testing tools in your job?</li>
<li style="text-align: justify;">How do you plan test automation?</li>
<li style="text-align: justify;">What is data – driven automation?</li>
<li style="text-align: justify;">What skills needed to be a good software test automator?</li>
<li style="text-align: justify;">What types of scripting techniques for test automation do you know?</li>
<li style="text-align: justify;">Describe common problems of test automation.</li>
<li style="text-align: justify;">What testing activities you may want to automate in a project?</li>
<li style="text-align: justify;">What are the main attributes of test automation?</li>
</ol>
</div>
Unknownnoreply@blogger.com5tag:blogger.com,1999:blog-6387540470950526449.post-24902597119361947522013-06-15T01:39:00.000+05:302013-07-06T15:28:06.471+05:30Integration Testing And Types Of Integration Testing<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: justify;">
Define Integration Testing And Types Of Integration Testing</h2>
<h3 style="text-align: justify;">
Integration Testing:</h3>
<div style="text-align: justify;">
Combining the modules and testing the flow of data between them. Integration Testing is divided into 2 types.</div>
<h4 style="text-align: left;">
<ul style="text-align: left;">
<li style="text-align: justify;">Incremental Integration Testing:</li>
</ul>
</h4>
<div style="text-align: justify;">
Adding the modules incrementally and checking the data flow between them. Modules are added in a sequential fashion.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
This can be done in two ways </div>
<div style="text-align: justify;">
</div>
<ul><ul>
<li>Top-Down Approach</li>
<li>Bottom-Up approach.</li>
</ul>
</ul>
<a name='more'></a><br />
<br />
<div style="text-align: justify;">
<b>a) Top-Down Approach:</b></div>
<div style="text-align: justify;">
In this Approach child should be direct descendant of parent. Data flow is from top to bottom, child module is added in incremental fashion.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b>b) Bottom-Up Approach:</b></div>
<div style="text-align: justify;">
It is exact reverse of Top-Down approach.</div>
<div style="text-align: justify;">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjJm1sp0BYRnqqPHx_yiNnjtewvexnTl2JN01jahi5i1oBL5h7VbDmzDaL0uF5DGsBp7gabNbPXcVrfRPat9Sx69ICjkraTqlFNSL6rLmqRuRh9VVnwUkkpSlYDsljF19qAb-Ep4ANRmW4S/s1600/difference-between-topdown-bottomup-approach.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="difference-between-topdown-bottomup-approach" border="0" height="256" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjJm1sp0BYRnqqPHx_yiNnjtewvexnTl2JN01jahi5i1oBL5h7VbDmzDaL0uF5DGsBp7gabNbPXcVrfRPat9Sx69ICjkraTqlFNSL6rLmqRuRh9VVnwUkkpSlYDsljF19qAb-Ep4ANRmW4S/s320/difference-between-topdown-bottomup-approach.jpg" title="difference-between-topdown-bottomup-approach" width="320" /></a></div>
<div style="text-align: justify;">
<br /></div>
<h4 style="text-align: left;">
<ul style="text-align: left;">
<li style="text-align: justify;">Non Incremental Integration Testing:</li>
</ul>
</h4>
<div style="text-align: justify;">
It is also called as Big Bang Method. In this approach modules are added simultaneously, it is going to be difficult to know why the particular issue is happening.</div>
</div>
Unknownnoreply@blogger.com10tag:blogger.com,1999:blog-6387540470950526449.post-91041380446336866212013-06-15T01:29:00.002+05:302013-07-06T15:28:00.097+05:30Define Agile Model and its Advantages<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: justify;">
Define Agile Model and its Advantages</h2>
<h2 style="text-align: justify;">
Agile Model or Agile Methodology :</h2>
<div style="text-align: justify;">
Agile development methodology attempts to provide many opportunities to assess the direction of a project throughout the development life cycle. Agile methods break tasks into small increments with minimal planning and do not directly involve long-term planning. Iterations are short time frames that typically last from one to four weeks. Each iteration involves a cross functional team working in all functions: planning, requirements analysis, design, coding, unit testing, and acceptance testing. At the end of the iteration a working product is demonstrated to stakeholders. This minimizes overall risk and allows the project to adapt to changes quickly. An iteration might not add enough functionality to warrant a market release, but the goal is to have an available release at the end of each iteration. Multiple iterations might be required to release a product or new features.</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_hsSNUUnOcILqmUbuRX_G-d2zKIfmQPnp80dp7qwJcWMIoKVyEh-b5L_Js5i3zrRt9_HtCJvqZbUZAZvRi6TmbmsxMYhWWe7oW3k_F1qPpKfVF40j7l-t0LwQ-oKMZSaWGQB10NVYCkOk/s1600/agile-model.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="agile-model" border="0" height="268" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_hsSNUUnOcILqmUbuRX_G-d2zKIfmQPnp80dp7qwJcWMIoKVyEh-b5L_Js5i3zrRt9_HtCJvqZbUZAZvRi6TmbmsxMYhWWe7oW3k_F1qPpKfVF40j7l-t0LwQ-oKMZSaWGQB10NVYCkOk/s400/agile-model.png" title="agile-model" width="400" /></a></div>
<a name='more'></a><br />
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Agile as the name refers implies something to do very quickly. Hence Agile Testing refers to validate the client requirements as soon as possible and make it customer friendly. As soon as the build is out, testing is expected to get started and report the bugs quickly if any found. As a Tester, you need to provide your thoughts on the client requirements rather than just being the audience at the other end. Emphasis has to be laid down on the quality of the deliverable in spite of short time-frame which will further help in reducing the cost of development and your feedback's will be implemented in the code which will avoid the defects coming from the end user.</div>
<h3 style="text-align: left;">
Advantages of Agile Methodology:</h3>
<div style="text-align: justify;">
</div>
<ul>
<li>Agile first priority is to fulfill the customer need from beginning to end and continuous improvement to ad into valuable software.</li>
<li>Agile allow change in requirements in the late in the development as well.</li>
<li>Agile works on delivering software regularly interval i.e. from couple of weeks to couple of month based on project.</li>
<li>Close, daily cooperation between business people and developers throughout the project.</li>
<li>Key point is to trust, support and motivate individuals to get it projects build on time.</li>
<li>Daily face-to-face conversation is key point in agile testing. This is most efficient & effective way of communication.</li>
<li>Measuring progress by the amount of completed work.</li>
<li>Continually seeking excellence</li>
<li>Harnessing change for competitive advantage</li>
<li>Simplicity</li>
<li>Self-organizing team come out with best architectures, requirements, and designs.</li>
<li>Regular adaptation to changing circumstances with more effective way.</li>
</ul>
</div>
Unknownnoreply@blogger.com10tag:blogger.com,1999:blog-6387540470950526449.post-34567017774043386712013-06-15T01:17:00.001+05:302013-07-06T15:27:50.158+05:30Software Testing Life Cycle (STLC)<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: justify;">
Software Testing Life Cycle (STLC)</h2>
<div style="text-align: justify;">
Software Testing Life Cycle (STLC) defines the steps/stages/phases in testing of software. </div>
<h3 style="text-align: justify;">
The different stages in Software Testing Life Cycle:</h3>
<br />
<ol style="text-align: left;">
<li style="text-align: justify;">Requirement Analysis</li>
<li style="text-align: justify;">Test Planning</li>
<li style="text-align: justify;">Test Case Design / Development</li>
<li style="text-align: justify;">Environment setup</li>
<li style="text-align: justify;">Test Execution / Reporting / Defect Tracking</li>
<li style="text-align: justify;">Test Cycle Closure / Retrospective study</li>
</ol>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgq5DYRMYhMwdOGwvbahfdNlD85yJhUmg8Yg2y4y12IVY0AVhJPuwueif8nFfnYNA7P_gDGXY_WlIRcRg1iHCmkSrojxk9Hvhhl1-wX_TE8YBFI80EyP6JY6GIT8Y5eH-_WDBLngdtAGsdc/s1600/Software_Testing_Life_Cycle.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Software_Testing_Life_Cycle" border="0" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgq5DYRMYhMwdOGwvbahfdNlD85yJhUmg8Yg2y4y12IVY0AVhJPuwueif8nFfnYNA7P_gDGXY_WlIRcRg1iHCmkSrojxk9Hvhhl1-wX_TE8YBFI80EyP6JY6GIT8Y5eH-_WDBLngdtAGsdc/s320/Software_Testing_Life_Cycle.png" title="Software_Testing_Life_Cycle" width="251" /></a></div>
<h3 style="text-align: justify;">
<a name='more'></a></h3>
<h3 style="text-align: justify;">
1) Requirement Analysis</h3>
<div style="text-align: justify;">
During this phase, test team studies the requirements from a testing point of view to identify the testable requirements. The QA team may interact with various stakeholders (Client, Business Analyst, Technical Leads, System Architects etc) to understand the requirements in detail. Requirements could be either Functional (defining what the software must do) or Non Functional (defining system performance /security availability ) .Automation feasibility for the given testing project is also done in this stage.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Activities</div>
<div style="text-align: justify;">
</div>
<ol>
<li>Identify types of tests to be performed. </li>
<li>Gather details about testing priorities and focus.</li>
<li>Prepare Requirement Traceability Matrix (RTM).</li>
<li>Identify test environment details where testing is supposed to be carried out. </li>
<li>Automation feasibility analysis (if required).</li>
</ol>
<br />
<div style="text-align: justify;">
Deliverables </div>
<div style="text-align: justify;">
</div>
<ol>
<li>RTM</li>
<li>Automation feasibility report. (if applicable)</li>
</ol>
<br />
<h3 style="text-align: left;">
2) Test Planning</h3>
<div style="text-align: justify;">
This phase is also called Test Strategy phase. Typically , in this stage, a Senior QA manager will determine effort and cost estimates for the project and would prepare and finalize the Test Plan.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Activities</div>
<div style="text-align: justify;">
</div>
<ol>
<li>Preparation of test plan/strategy document for various types of testing</li>
<li>Test tool selection </li>
<li>Test effort estimation </li>
<li>Resource planning and determining roles and responsibilities.</li>
<li>Training requirement</li>
</ol>
<br />
<div style="text-align: justify;">
Deliverables </div>
<div style="text-align: justify;">
</div>
<ol>
<li>Test plan /strategy document.</li>
<li>Effort estimation document.</li>
</ol>
<br />
<h3 style="text-align: left;">
3) Test Case Design / Development</h3>
<div style="text-align: justify;">
This phase involves creation, verification and rework of test cases & test scripts. Test data , is identified/created and is reviewed and then reworked as well.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Activities</div>
<div style="text-align: justify;">
</div>
<ol>
<li>Create test cases, automation scripts (if applicable)</li>
<li>Review and baseline test cases and scripts </li>
<li>Create test data (If Test Environment is available)</li>
</ol>
<br />
<div style="text-align: justify;">
Deliverables </div>
<div style="text-align: justify;">
</div>
<ol>
<li>Test cases/scripts </li>
<li>Test data</li>
</ol>
<br />
<h3 style="text-align: left;">
4) Test Environment Setup</h3>
<div style="text-align: justify;">
Test environment decides the software and hardware conditions under which a work product is tested. Test environment set-up is one of the critical aspects of testing process and can be done in parallel with Test Case Development Stage. Test team may not be involved in this activity if the customer/development team provides the test environment in which case the test team is required to do a readiness check (smoke testing) of the given environment.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Activities </div>
<div style="text-align: justify;">
</div>
<ol>
<li>Understand the required architecture, environment set-up and prepare hardware and software requirement list for the Test Environment. </li>
<li>Setup test Environment and test data </li>
<li>Perform smoke test on the build</li>
</ol>
<br />
<div style="text-align: justify;">
Deliverables </div>
<div style="text-align: justify;">
</div>
<ol>
<li>Environment ready with test data set up </li>
<li>Smoke Test Results.</li>
</ol>
<br />
<h3 style="text-align: left;">
5) Test Execution / Reporting / Defect Tracking</h3>
<div style="text-align: justify;">
During this phase test team will carry out the testing based on the test plans and the test cases prepared. Bugs will be reported back to the development team for correction and retesting will be performed.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Activities </div>
<div style="text-align: justify;">
</div>
<ol>
<li>Execute tests as per plan</li>
<li>Document test results, and log defects for failed cases </li>
<li>Map defects to test cases in RTM </li>
<li>Retest the defect fixes </li>
<li>Track the defects to closure</li>
</ol>
<br />
<div style="text-align: justify;">
Deliverables </div>
<div style="text-align: justify;">
</div>
<ol>
<li>Completed RTM with execution status </li>
<li>Test cases updated with results </li>
<li>Defect reports</li>
</ol>
<br />
<h3 style="text-align: left;">
6) Test Cycle Closure / Retrospective study</h3>
<div style="text-align: justify;">
Testing team will meet , discuss and analyze testing artifacts to identify strategies that have to be implemented in future, taking lessons from the current test cycle. The idea is to remove the process bottlenecks for future test cycles and share best practices for any similar projects in future.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Activities</div>
<div style="text-align: justify;">
</div>
<ol>
<li>Evaluate cycle completion criteria based on Time,Test coverage,Cost,Software,Critical Business Objectives , Quality</li>
<li>Prepare test metrics based on the above parameters. </li>
<li>Document the learning out of the project </li>
<li>Prepare Test closure report </li>
<li>Qualitative and quantitative reporting of quality of the work product to the customer. </li>
<li>Test result analysis to find out the defect distribution by type and severity.</li>
</ol>
<br />
<div style="text-align: justify;">
Deliverables </div>
<div style="text-align: justify;">
</div>
<ol>
<li>Test Closure report </li>
<li>Test metrics</li>
</ol>
</div>
Unknownnoreply@blogger.com19tag:blogger.com,1999:blog-6387540470950526449.post-89702246851908348612013-06-15T01:07:00.000+05:302013-07-06T15:27:40.221+05:30Difference Between Severity And Priority<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: left;">
Difference Between Severity And Priority</h2>
<table style="text-align: justify;"><colgroup><col width="*"></col><col width="*"></col></colgroup>
<tbody>
<tr>
<th><div style="text-align: center;">
Severity</div>
</th>
<th><div style="text-align: center;">
Priority</div>
</th>
</tr>
<tr>
<td>Severity: It is with respect to the Impact on the functionality.</td>
<td>It is with respect to the impact on the business.</td>
</tr>
<tr>
<td>Example for High Severity:<br />
<br />
The Quarterly statement event is not triggering from the website and we are just at the beginning of the new quarter after a new release. In this case the Severity is High but priority could be low because we have time till the quarter end to fix the bug.</td>
<td>Example for High Priority:<br />
<br />
The client logo is not appearing on the web site but the site is working fine. in this case the severity is low but the priority is high because from company's reputation it is most important to resolve. After all the reputation wins more clients and projects and hence increases revenue.</td>
</tr>
</tbody>
</table>
<div style="text-align: justify;">
<br /></div>
</div>
Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-6387540470950526449.post-65517592441523632532013-06-15T00:57:00.002+05:302013-07-06T15:27:33.672+05:30What If There Isn't Enough Time For Thorough Testing?<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: left;">
What If There Isn't Enough Time For Thorough Testing?</h2>
Use risk analysis to determine where testing should be focused. This requires judgment skills, common sense and experience. The checklist should include answers to the following questions:<br />
<br />
<ul style="text-align: left;">
<li>Which functionality is most important to the project's intended purpose? </li>
<li>Which functionality is most visible to the user? </li>
<li>Which functionality has the largest safety impact? </li>
<li>Which functionality has the largest financial impact on users? <a name='more'></a></li>
<li>Which aspects of the application are most important to the customer? </li>
<li>Which aspects of the application can be tested early in the development cycle? </li>
<li>Which parts of the code are most complex and thus most subject to errors? </li>
<li>Which parts of the application were developed in rush or panic mode? </li>
<li>Which aspects of similar/related previous projects caused problems? </li>
<li>Which aspects of similar/related previous projects had large maintenance expenses? </li>
<li>Which parts of the requirements and design are unclear or poorly thought out? </li>
<li> What do the developers think are the highest-risk aspects of the application? </li>
<li>What kinds of problems would cause the worst publicity? </li>
<li>What kinds of problems would cause the most customer service complaints? </li>
<li>What kinds of tests could easily cover multiple functionality? </li>
<li>Which tests will have the best high-risk-coverage to time-required ratio? </li>
</ul>
</div>
Unknownnoreply@blogger.com2tag:blogger.com,1999:blog-6387540470950526449.post-26495568255475069742013-06-15T00:55:00.001+05:302013-07-06T15:27:24.087+05:30Difference Between Verification And Validation<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: justify;">
Difference Between Verification And Validation</h2>
<table style="text-align: justify;"><colgroup><col width="*"></col><col width="*"></col></colgroup>
<tbody>
<tr>
<th><div style="text-align: center;">
Verification</div>
</th>
<th><div style="text-align: center;">
Validation</div>
</th>
</tr>
<tr>
<td>Are we building the product right?</td>
<td>Are we building the right product?</td>
</tr>
<tr>
<td>Verification is to check whether software conforms to the specifications and is done by development team at various development phases.During development phase the SRS document ,Design Document and the code are reviewed to ensure that product is being developed using the process oriented approach.It is an in-house activity of the development organization. It is an Quality assurance activity which prevents the defects of the product.</td>
<td>Validation is to check whether the software meets the customer's expectation.This is done by testing the software for its functionality and other requirements as mentioned in Requirements Specification Documents.Validation is carried out with customer involvement.It is Quality control acitvity which detects the defect during testing of the product</td></tr>
</tbody></table>
</div>
Unknownnoreply@blogger.com4tag:blogger.com,1999:blog-6387540470950526449.post-69684630332941856212013-06-15T00:49:00.003+05:302013-07-06T15:26:02.120+05:30Difference Between Test Scenario And Test Case<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: left;">
Difference Between Test Scenario And Test Case</h2>
<table style="text-align: justify;"><colgroup><col width="*"></col><col width="*"></col></colgroup>
<tbody>
<tr>
<th><div style="text-align: center;">
<span style="font-family: inherit;">Test Scenario</span></div>
</th>
<th><div style="text-align: center;">
<span style="font-family: inherit;">Test Case</span></div>
</th>
</tr>
<tr>
<td><span style="font-family: inherit;">Test Scenario is ‘What to be tested’</span></td>
<td><span style="font-family: inherit;">Test Case is ‘How to be tested’</span></td>
</tr>
<tr>
<td><span style="font-family: inherit;">Test scenario is nothing but test procedure.</span></td>
<td><span style="font-family: inherit;">Test case consist of set of input values, execution precondition, expected Results and executed </span>post-condition<span style="font-family: inherit;"> developed to cover certain test Condition. </span></td>
</tr>
<tr>
<td><span style="font-family: inherit;">The scenarios are derived from use cases.</span></td>
<td><span style="font-family: inherit;">Test cases are derived (or written) from test scenario. </span></td>
</tr>
<tr>
<td><span style="font-family: inherit;">Test Scenario represents a series of actions that are associated together.</span></td>
<td><span style="font-family: inherit;">Test Case represents a single (low level) action by the user.</span></td>
</tr>
<tr>
<td><span style="font-family: inherit;">Scenario is thread of operations</span></td>
<td><span style="font-family: inherit;">Test cases are set of input and output given to the System.</span></td>
</tr>
</tbody>
</table>
<div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;">
<div style="text-align: justify;">
<span style="background-color: transparent; color: black; font-family: inherit; font-size: 15px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"><br /></span></div>
</div>
<div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;">
<div style="text-align: justify;">
<b style="font-family: inherit; font-size: 15px; line-height: 1; white-space: pre-wrap;"><u>For example:</u></b></div>
</div>
<div dir="ltr" style="line-height: 1; margin-bottom: 0pt; margin-top: 0pt;">
<div style="text-align: justify;">
</div>
<ul>
<li><span style="font-family: inherit; font-size: 15px; line-height: 1; white-space: pre-wrap;">Checking the functionality of Login button is Test scenario</span></li>
<li><span style="font-family: inherit; font-size: 15px; line-height: 1; white-space: pre-wrap;">Test Cases for this Test Scenario are:</span></li>
<ul>
<li><span style="font-family: inherit; font-size: 15px; line-height: 1; white-space: pre-wrap;">Click the button without entering user name and password.</span></li>
<li><span style="font-family: inherit; font-size: 15px; line-height: 1; white-space: pre-wrap;">Click the button only entering User name.</span></li>
<li><span style="font-family: inherit; font-size: 15px; line-height: 1; white-space: pre-wrap;">Click the button while entering wrong user name and wrong password and </span><span style="font-family: inherit; font-size: 15px; line-height: 1; white-space: pre-wrap;">etc...</span></li>
</ul>
</ul>
</div>
</div>
Unknownnoreply@blogger.com2tag:blogger.com,1999:blog-6387540470950526449.post-74684676981885190222013-06-14T04:34:00.000+05:302013-07-06T15:26:48.807+05:30Web Testing Interview Questions Answers<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: center;">
Web Testing Interview Questions Answers</h2>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjxny7gRVFTotVpwMslbi7b0yOujMQinJ2BONkPbfHSqhceAfiMz_MtRfa9czFd5PjolWAjx4hK3Vu-4cziSxi_TfDOKP90T4yRV_GdcpGACHkJ-LDHzuupaj4Fj6MT5ld2-oy6P7J35POQ/s1600/web-testing-interview-questions.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="web-testing-interview-questions" border="0" height="83" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjxny7gRVFTotVpwMslbi7b0yOujMQinJ2BONkPbfHSqhceAfiMz_MtRfa9czFd5PjolWAjx4hK3Vu-4cziSxi_TfDOKP90T4yRV_GdcpGACHkJ-LDHzuupaj4Fj6MT5ld2-oy6P7J35POQ/s400/web-testing-interview-questions.jpg" title="web-testing-interview-questions" width="400" /></a></div>
<div>
<div style="text-align: justify;">
<br /></div>
</div>
<h3 style="text-align: justify;">
What is Web application?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">It is Software application that is accessed over a network such as the Internet or an intranet through a web browser. Web application provides services (Free and Paid) apart from information. Ex: Online Banking System it provides Bank information, Branches & ATM Information, Loans information etc…And It provides balance enquiry, Fund transfer, Bill payments like services.</li>
</ul>
<h3 style="text-align: justify;">
What is Web browser?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Web browser is a software application used to locate, retrieve and also display content on the World Wide Web, including Web pages, images, videos and other files. Examples: Google Chrome, Mozilla Firefox, Internet Explorer, Opera, Safari.</li>
</ul>
<h3 style="text-align: justify;">
What is website?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Basically website is an information provider; it provides information globally using internet protocols.<a name='more'></a></li>
</ul>
<h3 style="text-align: justify;">
What is WWW?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">The term WWW refers to the World Wide Web or simply the Web. The World Wide Web consists of all the public Web sites connected to the Internet worldwide, including the client devices (such as computers and cell phones) that access Web content. The WWW is just one of many applications of the Internet and computer networks.</li>
</ul>
<h3 style="text-align: justify;">
What is Web portal?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Web portal is a business gateway, It organizes business operations. Ex: Online shopping portals, Job portals etc…</li>
</ul>
<h3 style="text-align: justify;">
What is Web server?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Web server handles Clint side and server side validations and helps to deliver Web content that can be accessed through the Internet protocols. Examples: Microsoft IIS (Internet Information Service) Apache Web server from Apache Java Web server Pramathi web server etc…</li>
</ul>
<h3 style="text-align: justify;">
How to perform Web Services Testing?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">A Web Service is a service accessed via Web. Web Service is a way to publish your application over web and enable other applications to access functions defined by your web service. Web services exposes an interface defined in Web Services Description Language (WSDL).</li>
</ul>
<h3 style="text-align: justify;">
How to test Web Forms manually and using QTP Tool?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Web forms have 2 types of validations;</li>
<ul>
<li style="text-align: justify;">a) Field level validations</li>
<li style="text-align: justify;">b) Field level validations</li>
</ul>
</ul>
<div style="text-align: justify;">
Using Black Box test design techniques we can test web forms manually</div>
<div style="text-align: justify;">
Using Conditional statements and built-in functions we can test web forms (Using QTP)</div>
<h3 style="text-align: justify;">
What are possible configurations that could affect the testing strategy of any web site?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Possible configurations that affect the testing strategy of any web site are hardware platform (PC, Mac), Browser software and version, Browser Plug-Ins, Browser settings options, Video resolution and Colour Depth, and text size.</li>
</ul>
<h3 style="text-align: justify;">
What are the advantages of web applications than GUI based applications?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Only server side installation, client side installation is not mandatory, so deployment and maintenance is easy.It can be accessible anywhere, anytime via a PC with an Internet connection.The user interface of web-based applications is easier to customize than it is in GUI applications. Content can also be customized for presentation on any device connected to the internet, including PDAs, mobile phones etc…Supports thousands of clients effectively Adding and removing clients is very easy.</li>
</ul>
<h3 style="text-align: justify;">
What are the different types of environments available in the Web?</h3>
<div style="text-align: justify;">
Intranet (Local Network)Internet (Wide area Network)Extranet (Private network over Internet)</div>
<h3 style="text-align: justify;">
We have different types of web applications available in the Industry?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">a) Websites Ex: http://www.aurobindo.com/, http://www.pennacement.com/ etc…</li>
<li style="text-align: justify;">b) Web portals Ex: http://www.ebay.in/, http://www.naukri.com/ etc…</li>
<li style="text-align: justify;">c) Web Applications Ex: www.icicibank.com/, http://www.sunlife.com/ etc…</li>
<li style="text-align: justify;">d) Email Service providers Ex: www.gmail.com, www.yahoo.com, www.rediffmail.com etc…</li>
<li style="text-align: justify;">e) Social Networks Ex: www.facebook.com, www.twitter.com, www.linkedin.com etc…</li>
<li style="text-align: justify;">f) Discussion Forums Etc… Ex: www.top100interviewquestions.com</li>
</ul>
<h3 style="text-align: justify;">
What are the important aspects in Web testing?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Functional Testing (includes links testing, navigation testing etc…),</li>
<li style="text-align: justify;">Security Testing,</li>
<li style="text-align: justify;">Database Testing (includes Data integrity, data manipulations, data retrievals etc..),</li>
<li style="text-align: justify;">Performance Testing (includes all types of performance like Load Testing, Stress Testing, Spike Testing, Endurance Testing and Data volume Testing),</li>
<li style="text-align: justify;">Usability Testing,</li>
<li style="text-align: justify;">Navigation testing,</li>
<li style="text-align: justify;">Configuration Testing,</li>
<li style="text-align: justify;">Compatibility Testing,</li>
<li style="text-align: justify;">Reliability Testing,</li>
<li style="text-align: justify;">Availability Testing,</li>
<li style="text-align: justify;">Scalability Testing Etc…</li>
</ul>
<h3 style="text-align: justify;">
What are the important web testing activities?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Forms validation</li>
<li style="text-align: justify;">Links validation</li>
<li style="text-align: justify;">Database testing</li>
<li style="text-align: justify;">Navigation testing</li>
<li style="text-align: justify;">Performance (Load, Stress and Endurance)</li>
<li style="text-align: justify;">Search operations validation Etc…</li>
</ul>
<h3 style="text-align: justify;">
What is application server?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Application Server also called an appserver, It is a program that handles all application operations between users and an organization’s back-end business applications or databases.</li>
</ul>
<h3 style="text-align: justify;">
What is Client side validation?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Validating client side forms, which is typically done by Java Script. Generally it checks weather the user is entering correct form of data or not? and entering all mandatory fields or not? Client site validation is 2 types One is Field level validation another is Form level validation.</li>
</ul>
<h3 style="text-align: justify;">
What is Cookies Testing?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">A “cookie” is a small piece of information that sent by a web server to store on a web browser so it can later be read back from that browser. This is useful for having the browser remember some specific information.</li>
</ul>
<h3 style="text-align: justify;">
What is database server?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Database server is used to refer to the back-end system of a database application using client/server architecture. The back-end, sometimes called a database server, performs tasks such as data design, storage, data manipulations, archiving, and other non-user specific tasks. Examples: Oracle, MS SQL Server, MySQL (Open source), IBM DB2 etc…</li>
</ul>
<h3 style="text-align: justify;">
What is difference between client server and Web Testing?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">The difference between client server and Web Testing: In client server application you have two different components to test. Application is loaded on server machine while the application exe on every client machine. You will test broadly in categories like, GUI on both sides, functionality, Load, client-server interaction, back-end. This environment is mostly used in Intranet networks. You are aware of number of clients and servers and their locations in the test scenario. Web application is a bit different and complex to test as tester don’t have that much control over the application. Application is loaded on the server whose location may or may not be known and no exe is installed on the client machine, you have to test it on different web browsers. Web applications are supposed to be tested on different browsers and OS platforms so broadly Web application is tested mainly for browser compatibility and operating system compatibility, error handling, static pages, back-end testing and load testing.</li>
</ul>
<h3 style="text-align: justify;">
What is extranet application?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">It is also a private application over internet, can be accessed by fixed machines only. It uses Wide area network and Internet Protocol technology to share information.</li>
</ul>
<h3 style="text-align: justify;">
What is HTML?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">HTML stands for Hyper Text Markup Language, it is for displaying web pages and other information. Basically it is data presenter in the web.</li>
</ul>
<h3 style="text-align: justify;">
What is HTTP?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Hyper Text Transfer Protocol, the data transfer protocol used on the World Wide Web.</li>
</ul>
<h3 style="text-align: justify;">
What is HTTPS?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">HTTPS stands for Hypertext Transfer Protocol Secure is a widely-used communications protocol for secure communication over a computer network.</li>
</ul>
<h3 style="text-align: justify;">
What is internet application?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Generally it is a public web application, uses Wide area network. It can be accessed from anywhere.</li>
</ul>
<h3 style="text-align: justify;">
What is intranet application?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">It is a private application, can be accessed within the Organization only. It uses Local /Private Network and Internet Protocol technology to share information.</li>
</ul>
<h3 style="text-align: justify;">
What is purpose of Java Script in the Web?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">It is for performing client side validations.</li>
</ul>
<h3 style="text-align: justify;">
What is Server side validation?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Validating, processing client requests and providing response from the Server.</li>
</ul>
<h3 style="text-align: justify;">
What is the difference among Intranet, Internet and Extranet web applications?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Intranet: It is a private network(Within the Organization) uses LAN/MAN Technologies</li>
<li style="text-align: justify;">Internet: It is a Public network uses WAN Technology</li>
<li style="text-align: justify;">Extranet: It also private network over Internet</li>
</ul>
<h3 style="text-align: justify;">
What is the difference between desktop application testing and web testing?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Desktop testing is standalone testing. Desktop need not worry about number of user etc. Web testing is related to client server. Web testing needs to have many testing’s like usability, GUI, and Load Testing.</li>
</ul>
<h3 style="text-align: justify;">
Which different test scenarios will you consider when you are testing a website?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">The first scenario to be tested is the GUI. The page layout and the design elements used on the website have to be uniform throughout the website. The next part to be tested is the different links provided inside the website. Along with the links, it will also have to be tested, whether internal navigation is smooth and also check if it is complex. The next important aspect to be checked is the response time of the website. This will also have to checked, when there is heavy load on the system.</li>
</ul>
<h3 style="text-align: justify;">
Explain the difference between authentication and authorization during web testing?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Authentication is the process with which the system identifies the user. The goal is to ensure that the user is indeed a user, who he claims to be. There are different types of authentications, which can be used like password based authentication, device based authentication, etc. On the other hand, authorization is the process after the authentication process. In this process the system will decide whether a particular task can be performed by the user, does he have the necessary permissions, etc</li>
</ul>
<h3 style="text-align: justify;">
Which are the different test case formats that are a part of web testing?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">The test case formats will vary depending on whether the website is a static website or a dynamic website. The static website will have the front end test cases, navigation test cases. On the other hand, if the website is a dynamic website, then the test cases will be broadly divided under front end test cases, back end test cases, field validations test cases, database test cases, security test cases, etc</li>
</ul>
<h3 style="text-align: justify;">
Which are the HTTP Response Objects?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Some of the HTTP Response Objects are write, flush, tell, etc. The subclasses of HTTP Response are HttpResponseRedirect, HttpResponsePermanentRedirect, HttpResponseBadRequest, HttpResponseNotFound, etc.</li>
</ul>
<h3 style="text-align: justify;">
What is a proxy server?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">A proxy server is a server, which behaves like an intermediary between the client and the main server. Therefore, the requests onto the main server are first sent to the proxy server from the client system, which are then forwarded to the main server. The response from the main server is sent to the client through the proxy server itself. The request and/or the response may be modified by the proxy server depending on the filtering rules of the server</li>
</ul>
<h3 style="text-align: justify;">
Is usability testing possible while testing a website?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Usability testing is indeed an important part of web testing. In usability testing, it is checked, whether the website is user-friendly. Is it possible for the user to move around easily within the webpage? Is there any sort of ambiguity on the webpage, which can hinder the user experience?</li>
</ul>
<h3 style="text-align: justify;">
While testing a website, which are the different configurations which will have to be considered these configurations may demand for change in strategy of the webpage.</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">The most important factor that needs consideration is the hardware platform, while some may use the Mac platform, some may use Linux, while others may use Microsoft platform. The next comes the browsers and their versions into the picture. Along with the browser versions, the different Plug-Ins also have to be taken into consideration. The resolution of the monitor also with color depth and text size are some of the other configurations.</li>
</ul>
<h3 style="text-align: justify;">
Which are the common browsers, where a web application should be tested?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">The browsers that are commonly used are Mozilla Firefox, Google Chrome, Internet Explorer and Opera. Therefore, a web application must be tested on these browsers as well.</li>
</ul>
<h3 style="text-align: justify;">
How are the static websites different than the dynamic websites?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Static websites only give out information to the user and the user does not have any sort of interaction with the website. On the other hand, dynamic websites are the ones, where the user communicates with the system and is asked for information. On providing the required information, he may be able to retrieve the information he is looking for.</li>
</ul>
<h3 style="text-align: justify;">
What are the common problems faced in web testing?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">The most common problem faced during web testing is the server problem. The server can either be down or it can be under maintenance. The next problem, which is often faced in web testing is database problem, where the connection to the database can be broken. In some cases, there can be hardware compatibility problems, when one is testing a web application.</li>
</ul>
<h3 style="text-align: justify;">
What is the purpose of VbScript in the Web?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">It can be used for client side validations as well as Server side validations.</li>
</ul>
<h3 style="text-align: justify;">
What is Web Services?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Web services are application components, communicate using open protocols and these can be used by other applications. XML is the basis for Web services SOAP (Simple Object Access Protocol), UDDI (Universal Description, Discovery and Integration) and WSDL (Web Services Description Language) are the Web services platform elements.</li>
</ul>
<h3 style="text-align: justify;">
What the latest web technologies do you know?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Latest web technologies are: The main three web tracks:</li>
<ul>
<li style="text-align: justify;">1. Microsoft ASP.Net Track + SQL Server database engine (IDE: Expression Web, Visual Studio).</li>
<li style="text-align: justify;">2. Oracle Java Track + Oracle database engine (IDE: NetBeans, Eclipse).</li>
<li style="text-align: justify;">3. PHP Track + MySQL database engine (IDE: Zend Studio, DreamWeaver). There are many new concepts and enhanced methodologies like Ajax, JQuery, JSON, and so on.</li>
</ul>
</ul>
<h3 style="text-align: justify;">
What types HTTP Response Codes do you know?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Types of HTTP Response Codes are:</li>
</ul>
<div style="text-align: justify;">
2xx – success,</div>
<div style="text-align: justify;">
3xx – Redirection,</div>
<div style="text-align: justify;">
4xx – Client Error,</div>
<div style="text-align: justify;">
5xx – Server Error</div>
<h3 style="text-align: justify;">
What types of web testing security problems do you know?</h3>
<ul style="text-align: left;">
<li style="text-align: justify;">Types of web testing security problems are: Denial of Service (DoS) attack, buffer overflow etc…</li>
</ul>
</div>
Unknownnoreply@blogger.com17tag:blogger.com,1999:blog-6387540470950526449.post-60791890195148579182013-06-11T00:30:00.000+05:302013-07-06T15:26:36.727+05:30Top 100 Software Testing Interview Questions<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: left;">
Top 100 Software Testing Interview Questions</h2>
<ol style="text-align: left;">
<li>What are the common problems with software automation?</li>
<li>What are the key challenges of software testing?</li>
<li>What is the role of QA in a project development?</li>
<li>Can you explain V model in manual testing?</li>
<li>Can u explain the structure of bug life cycle?</li>
<li>What is “bug leakage?” and what is “bug release?”</li>
<li>Can you explain water fall model in manual testing?</li>
<li>Can you explain me the levels in V model manual?<br /><a name='more'></a></li>
<li>What is the value of a testing group? How do you justify your work and budget?</li>
<li>Why does u save .vbs in library files in qtp winrunner?</li>
<li>What is open beta testing? And it did at which end? What is the difference b/w open beta testing and beta testing?</li>
<li>What’s the role of CMM Level in Testing?</li>
<li>What is the difference between scenario and test case?</li>
<li>What is the Test case Life Cycle?</li>
<li>What is extension for test script in Quick Test?</li>
<li>How to write test case with a minimum of 13 columns…….</li>
<li>How I can do GUI testing, what is its important contant, plz tell me all property of GUI testing?</li>
<li>Can u explain spiral binding model in manual testing developers looking to do= testing)</li>
<li>Why do u use object spy in qtp?</li>
<li>Why do need synchronization in qtp?</li>
<li>Who are prepared use cases?</li>
<li>Where do check points store in qtp?</li>
<li>When we do update mode in qtp?</li>
<li>What type of testing questions will be asked for 2+ yrs exp people in interview?</li>
<li>What part of the testing phase is the most important part for testing in the cycle?</li>
<li>What is visual source safe?</li>
<li>What is virtual object and when will we use?</li>
<li>What is virtual object and at what we will use virtual object in qtp?</li>
<li>What is virtual memory?</li>
<li>What is unit testing?</li>
<li>What is the model of spiral binding in manual testing? Can you explain spiral binding?</li>
<li>What is the difference between properties and methods in qtp?</li>
<li>What is the difference between smoke testing and sanitary testing?</li>
<li>What is the difference between test scenarios and test strategy?</li>
<li>What is the difference between build and release?</li>
<li>What is the difference between usability testing and GUI?</li>
<li>What is the difference between constant and parameter in qtp?</li>
<li>What is test strategy who will prepare that one? And what will be there in test strategy.</li>
<li>What is test metrics?</li>
<li>What is test development?</li>
<li>What is the definition for test life cycle?</li>
<li>What is the Test case Life Cycle?</li>
<li>What is test bed?</li>
<li>What is unit testing in manual?</li>
<li>What is a test plan who will prepare that one?</li>
<li>How do you develop a test plan and schedule? Describe bottom-up and top-down approaches?</li>
<li>What is system testing?</li>
<li>What is the difference in writing the test cases for Integration testing and system testing?</li>
<li>What are application entry and exit criteria?</li>
<li>What are SRS and BRS in manual testing?</li>
<li>What is Sanity Test, Adhoc Testing & Smoke Testing? When will use the Above Tests?</li>
<li>What is V model in manual testing?</li>
<li>What is V model can u explain?</li>
<li>What is a frame work at what situations we will use?</li>
<li>What is STLC how many phases are there can you explain them?</li>
<li>What is Review?</li>
<li>What is alpha testing and beta testing?</li>
<li>What is SRS and BRS document? Can you explain them briefly?</li>
<li>What is stub and driver in manual testing?</li>
<li>What is stress testing?</li>
<li>What is stand alone mode running in load runner?</li>
<li>What is reusable action in qtp?</li>
<li>What is regular expression and when we will use regular expression in qtp?</li>
<li>What is prototype model in manual testing?</li>
<li>What is port testing?</li>
<li>What is performance testing?</li>
<li>What is objective of actions in qtp?</li>
<li>What is mean by GUI testing? What is mean by client/Server? What is meant by web based application?</li>
<li>What is integration testing?</li>
<li>What is functional testing, system testing, data driven testing?</li>
<li>What is frame work in qtp?</li>
<li>What is fish model can you explain?</li>
<li>What is exact difference between Debugging & Testing?</li>
<li>What is determination?</li>
<li>What is debugging?</li>
<li>What is compatibility testing?</li>
<li>What is BUG Life cycle?</li>
<li>What is Black Box Testing?</li>
<li>What are the roles of glass-box and black-box testing tools?</li>
<li>What is FSO can you explain?</li>
<li>What are the processes followed in your company for automation?</li>
<li>What do you mean by Pilot Testing?</li>
<li>What is AUT?</li>
<li>What are the objectives of Low-level recording? What is Elapsed Time? When we use Update mode?</li>
<li>What are the difference between per text mode and shared mode in qtp?</li>
<li>What are the objectives of Utility objects?</li>
<li>What are the objectives of debugging?</li>
<li>Share a particular project where you have been able to learn enough skills to help with testing?</li>
<li>What are GET TO, SETTO, and GET RO properties in QTP.</li>
<li>The role of both QA & QC?</li>
<li>How to test the Microsoft Word 2003. What all the major areas to be tested, please explain.</li>
<li>How to write a test case and bugreport? Plz explain with an example.</li>
<li>How to do regression testing, and can give one or two examples on that in the same application?</li>
<li>How to arrive Test case? And how to write Test case in Email id? When we go for winrunner and why we go for?</li>
<li>Explain me the phases of STLC and explain each one briefly?</li>
<li>Explain about Microsoft Six Rules Standard for User Interface testing?</li>
<li>Difference between bug, error and defect?</li>
<li>How many modes of recording are there?</li>
<li>Give exact and appropriate definition of testing.</li>
<li>How will you review the test case and how many types are there?</li>
</ol>
<br /></div>
Unknownnoreply@blogger.com10tag:blogger.com,1999:blog-6387540470950526449.post-9602263481999772682013-06-08T02:09:00.001+05:302013-07-06T15:25:42.268+05:30Compare Desktop testing, Client-Server testing and Web testing<div dir="ltr" style="text-align: left;" trbidi="on">
<div style="text-align: justify;">
We have three testing types</div>
<ul style="text-align: left;">
<li style="text-align: justify;">Desktop application testing,</li>
<li style="text-align: justify;">Client server application testing and</li>
<li style="text-align: justify;">Web application testing.</li>
</ul>
<div style="text-align: justify;">
Each one differs in the environment in which they are tested and you will lose control over the environment in which application you are testing, while you move from desktop to web applications.</div>
<h2 style="text-align: justify;">
DESKTOP APPLICATION:</h2>
<div style="text-align: justify;">
It runs on personal computers and work stations, so when you test the desktop application you are focusing on a specific environment. You will test complete application broadly in categories like GUI, functionality, Load, and back-end i.e DB.</div>
<h2 style="text-align: justify;">
CLIENT / SERVER TESTING:</h2>
<div style="text-align: justify;">
In client server application you have two different components to test. Application is loaded on server machine while the application exe on every client machine. You will test broadly in categories like, GUI on both sides, functionality, Load, client-server interaction, back-end.</div>
<div style="text-align: justify;">
<br />
<a name='more'></a><br /></div>
<div style="text-align: justify;">
This type of testing usually done for 2 tier applications (usually developed for LAN) Here we will be having front-end and back-end.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
The application launched on front-end will be having forms and reports which will be monitoring and manipulating data E.g: applications developed in VB, VC++, Core Java, C, C++, D2K, Power Builder etc., The back-end for these applications would be MS Access, SQL Server, Oracle, Sybase, MySQL, Quad-base.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
The tests performed on these types of applications would be</div>
<div style="text-align: justify;">
</div>
<ul>
<li>User interface testing</li>
<li>Manual support testing</li>
<li>Functionality testing</li>
<li>Compatibility testing & configuration testing</li>
<li>Intersystem testing</li>
</ul>
<h2 style="text-align: justify;">
WEB TESTING:</h2>
<div style="text-align: justify;">
This is done for 3 tier applications (developed for Internet / intranet / xtranet) Here we will be having Browser, web server and DB server. Web application is a bit different and complex to test as tester don’t have that much control over the application. Application is loaded on the server whose location may or may not be known and no exe is installed on the client machine, you have to test it on different web browsers. Web applications are supposed to be tested on different browsers and OS platforms so broadly Web application is tested mainly for browser compatibility and operating system compatibility, error handling, static pages, back-end testing and load testing.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
The applications accessible in browser would be developed in HTML, DHTML, XML, JavaScript etc. (We can monitor through these applications)</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Applications for the web server would be developed in Java, ASP, JSP, VBScript, JavaScript, Perl, Cold Fusion, PHP etc. (All the manipulations are done on the web server with the help of these programs developed)</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
The DB server would be having oracle, sql server, sybase, MySQL etc. (All data is stored in the database available on the DB server)</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
The tests performed on these types of applications would be:</div>
<div style="text-align: justify;">
</div>
<ul>
<li>User interface testing</li>
<li>Functionality testing</li>
<li>Security testing</li>
<li>Browser compatibility testing</li>
<li>Load / stress testing</li>
<li>Interoperability testing/intersystem testing</li>
<li>Storage and data volume testing</li>
</ul>
<h2 style="text-align: left;">
Difference between Desktop, Client-Server and Web Applications :</h2>
<table><colgroup><col width="*"></col><col width="*"></col><col width="*"></col></colgroup>
<tbody>
<tr>
<th>Desktop applications</th>
<th>Client/Server applications</th>
<th>Web applications</th>
</tr>
<tr>
<td>Application runs in single memory (Front end and Back end in one place)</td>
<td>Application runs in two or more machines</td>
<td>Application runs in two or more machines</td>
</tr>
<tr>
<td>N/A</td>
<td>Application is a menu-driven</td>
<td>URL-driven</td>
</tr>
<tr>
<td>N/A</td>
<td>Connected mode (connection exists always until logout)</td>
<td>Disconnected mode (state less)</td>
</tr>
<tr>
<td>Single user only</td>
<td>Limited number of users</td>
<td>Unlimited number of users</td>
</tr>
<tr>
<td>N/A</td>
<td>Less number of network issues when compared to web app.</td>
<td>Many issues like hardware compatibility, browser compatibility, version compatibility, security issues, performance issues etc.</td>
</tr>
</tbody>
</table>
<div style="text-align: justify;">
<br />
As per difference in both the applications come where, how to access the resources. In client server once connection is made it will be in state on connected, whereas in case of web testing http protocol is stateless, then there comes logic of cookies, which is not in client server.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
For client server application users are well known, whereas for web application any user can login and access the content, he/she will use it as per his intentions.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
So, there are always issues of security and compatibility for web application we need to be aware of</div>
</div>
Unknownnoreply@blogger.com6tag:blogger.com,1999:blog-6387540470950526449.post-20429877879810492462013-06-08T02:09:00.000+05:302013-07-06T15:25:35.492+05:30Difference between Web testing and Client-Server testing<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: left;">
<span style="font-family: inherit;">Difference between Web testing and Client-Server testing :</span></h2>
<table style="text-align: justify;"><colgroup><col></col><col></col></colgroup>
<tbody>
<tr>
<th><div style="text-align: center;">
<span style="font-family: inherit;">CLIENT / SERVER TESTING</span></div>
</th>
<th><div style="text-align: center;">
<span style="font-family: inherit;">WEB TESTING</span></div>
</th>
</tr>
<tr>
<td><span style="font-family: inherit;">This type of testing usually done for 2 tier applications (usually developed for LAN)</span><br />
<span style="font-family: inherit;">Here we will be having frontend and backend.</span><br />
<span style="font-family: inherit;"><br /></span>
<span style="font-family: inherit;">The application launched on frontend will be having forms and reports which will be monitoring and manipulating data</span></td>
<td><span style="font-family: inherit;"><br /></span>
<span style="font-family: inherit;">This is done for 3 tier applications (developed for Internet / intranet / xtranet)</span><br />
<span style="font-family: inherit;"><br /></span>
<span style="font-family: inherit;">Here we will be having Browser, web server and DB server. </span><br />
<span style="font-family: inherit;"><br /></span>
<span style="font-family: inherit;">The applications accessable in browser would be developed in HTML, DHTML, XML, JavaScript etc.,</span><br />
<span style="font-family: inherit;">(we can monitor thru these applications)</span></td>
</tr>
<tr>
<td><span style="font-family: inherit;">Applications developed in VB,VC++,Core Java,C,C++,D2K,PowerBuilder etc.,</span><br />
<span style="font-family: inherit;"><br /></span></td>
<td><span style="font-family: inherit;">Applications for the webserver would be developed in Adv Java, ASP, JSP, VBScript, JavaScript, Perl, ColdFusion, PHP etc.,</span><br />
<span style="font-family: inherit;">(all the manipulations are done on the web server with the help of these programs developed)</span><br />
<span style="font-family: inherit;"><br /></span></td>
</tr>
<tr>
<td><span style="font-family: inherit;">The backend for these applications would be MS Access, SQL Server, oracle, sybase, mysql, quadbase</span><br />
<span style="font-family: inherit;"><br /></span></td>
<td><span style="font-family: inherit;">The DBserver would be having oracle, sql server, sybase, mysql etc.,</span><br />
<span style="font-family: inherit;">(all data is stored in the database available on the DB server)</span></td>
</tr>
<tr>
<td><span style="font-family: inherit;">The tests performed on these type of applications would be</span><br />
<span style="font-family: inherit;">- user interface testing</span><br />
<span style="font-family: inherit;">- manual support testing</span><br />
<span style="font-family: inherit;">- Functionality testing</span><br />
<span style="font-family: inherit;">- compatability testing & configuration testing</span><br />
<span style="font-family: inherit;">- intersystems testing</span><br />
<span style="font-family: inherit;"><br /></span></td>
<td><span style="font-family: inherit;">The tests performed on these type of applications would be</span><br />
<span style="font-family: inherit;">- user interface testing</span><br />
<span style="font-family: inherit;">- Functionality testing</span><br />
<span style="font-family: inherit;">- security testing</span><br />
<span style="font-family: inherit;">- browser compatability testing</span><br />
<span style="font-family: inherit;">- load / stress testing</span><br />
<span style="font-family: inherit;">- interoperability testing/intersystems testing</span><br />
<span style="font-family: inherit;">- storage and data volume testing</span></td></tr>
</tbody></table>
<div style="text-align: justify;">
<br /></div>
</div>
Unknownnoreply@blogger.com2tag:blogger.com,1999:blog-6387540470950526449.post-87196666798408087242013-06-07T03:37:00.000+05:302013-07-06T15:26:26.916+05:30Software testing Interview Questions – Based on Testing Levels<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: center;">
Software testing Interview Questions – Based on Testing Levels</h2>
<ul style="text-align: left;">
<li style="text-align: justify;"> What is Acceptance Testing?</li>
<li style="text-align: justify;">What is Alfa Testing?</li>
<li style="text-align: justify;">What is Beta Testing?</li>
<li style="text-align: justify;">What is Big-bang or System Approach?</li>
<li style="text-align: justify;">What is Bottom-up Integration?</li>
<li style="text-align: justify;">What is Certification Testing?<a name='more'></a></li>
<li style="text-align: justify;">What is Component Integration Testing?</li>
<li style="text-align: justify;">What is STLC?</li>
<li style="text-align: justify;">What is Static Testing?</li>
<li style="text-align: justify;">What is System Integration Testing?</li>
<li style="text-align: justify;">What is System Testing?</li>
<li style="text-align: justify;">What is Dynamic Testing?</li>
<li style="text-align: justify;">What is End to End Testing?</li>
<li style="text-align: justify;">What is Functional and System Testing?</li>
<li style="text-align: justify;">What is Program Testing?</li>
<li style="text-align: justify;">What is Test Level?</li>
<li style="text-align: justify;">What is Top-down Integration?</li>
<li style="text-align: justify;">What is Traceability Matrix?</li>
<li style="text-align: justify;">What is Integration Testing?</li>
<li style="text-align: justify;">What is Operational Acceptance Testing?</li>
<li style="text-align: justify;">What is the role of test lead in Test Planning stage?</li>
<li style="text-align: justify;">What type of Test design techniques can be applied in System Testing?</li>
<li style="text-align: justify;">What type of Test design techniques can be applied in Unit or Component Testing?</li>
<li style="text-align: justify;">Who is the author of Test Plan?</li>
<li style="text-align: justify;">What is Unit or Component Testing?</li>
<li style="text-align: justify;">Explain about the System Testing process?</li>
<li style="text-align: justify;">What are the Test Types that can be applied in System Testing?</li>
<li style="text-align: justify;">What are the Test Types that can be applied in Unit Testing?</li>
<li style="text-align: justify;">What are the differed types of documents that can be created during testing?</li>
<li style="text-align: justify;">What are the different approaches for Components Integration?</li>
<li style="text-align: justify;">What are the different stages in Software Test Process?</li>
<li style="text-align: justify;">What is role of Test Lead in Test Closure stage?</li>
<li style="text-align: justify;">What is role of team members in Test Design stage?</li>
<li style="text-align: justify;">What is role of team members in Test planning stage?</li>
<li style="text-align: justify;">What is the role of test lead in Test Design stage?</li>
</ul>
<div style="text-align: justify;">
<br /></div>
</div>
Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-6387540470950526449.post-34068004005459458952013-05-31T03:34:00.000+05:302013-07-06T15:26:18.045+05:30Software testing Interview Questions – Based on Testing Types<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: center;">
Software testing Interview Questions – Based on Testing Types</h2>
<ul style="text-align: left;">
<li style="text-align: justify;">What are the prerequisites for Test Execution?</li>
<li style="text-align: justify;">What are the roles of Test Lead in Test Execution stage?</li>
<li style="text-align: justify;">What are the roles of Testers in Test Execution stage?</li>
<li style="text-align: justify;">What is Accessibility Testing?</li>
<li style="text-align: justify;">What is Ad-hoc Testing?</li>
<li style="text-align: justify;">What is Agile testing?<a name='more'></a></li>
<li style="text-align: justify;">What is Automated Testing?</li>
<li style="text-align: justify;">What is Basic path Testing?</li>
<li style="text-align: justify;">What is Boundary Testing?</li>
<li style="text-align: justify;">What is Branch Testing?</li>
<li style="text-align: justify;">What is Breadth Testing?</li>
<li style="text-align: justify;">What is Compatibility Testing?</li>
<li style="text-align: justify;">What is Comprehensive Testing?</li>
<li style="text-align: justify;">What is Comprehensive Testing?</li>
<li style="text-align: justify;">What is Concurrency Testing?</li>
<li style="text-align: justify;">What is Configuration Testing?</li>
<li style="text-align: justify;">What is Conformance Testing?</li>
<li style="text-align: justify;">What is Context Driven testing?</li>
<li style="text-align: justify;">What is Decision Testing?</li>
<li style="text-align: justify;">What is Dependency Testing?</li>
<li style="text-align: justify;">What is Depth Testing?</li>
<li style="text-align: justify;">What is Endurance Testing?</li>
<li style="text-align: justify;">What is Exhaustive Testing?</li>
<li style="text-align: justify;">What is Final Regression?</li>
<li style="text-align: justify;">What is Functional Testing?</li>
<li style="text-align: justify;">What is Functionality Testing?</li>
<li style="text-align: justify;">What is Installation Testing?</li>
<li style="text-align: justify;">What is Internalization Testing?</li>
<li style="text-align: justify;">What is Load Testing?</li>
<li style="text-align: justify;">What is Localization Testing?</li>
<li style="text-align: justify;">What is Monkey Testing?</li>
<li style="text-align: justify;">What is Non-Functional Testing?</li>
<li style="text-align: justify;">What is Performance Testing?</li>
<li style="text-align: justify;">What is Random Testing?</li>
<li style="text-align: justify;">What is Re Testing?</li>
<li style="text-align: justify;">What is Recovery Testing?</li>
<li style="text-align: justify;">What is Regression Testing?</li>
<li style="text-align: justify;">What is Regression Testing?</li>
<li style="text-align: justify;">What is Reliability Testing?</li>
<li style="text-align: justify;">What is Sanity Testing?</li>
<li style="text-align: justify;">What is Sanity Testing?</li>
<li style="text-align: justify;">What is Security Testing?</li>
<li style="text-align: justify;">What is Spike Testing?</li>
<li style="text-align: justify;">What is Statement Testing?</li>
<li style="text-align: justify;">What is Stress Testing?</li>
<li style="text-align: justify;">What is Test Batch?</li>
<li style="text-align: justify;">What is Test Type?</li>
<li style="text-align: justify;">What is Usability Testing?</li>
</ul>
</div>
Unknownnoreply@blogger.com6tag:blogger.com,1999:blog-6387540470950526449.post-73051044598985575002013-05-28T00:23:00.000+05:302013-07-06T15:26:12.127+05:30WinRunner Automation Testing Interview Questions<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: left;">
WinRunner Automation Testing Interview Questions</h2>
<ol style="text-align: left;">
<li>How do you handle an Exception in WinRunner?</li>
<li>What’s your comfort level in using WinRunner?</li>
<li>Running tests from the command line?</li>
<li>Can you test DB using WinRunner?</li>
<li>When do you go for Context Sensitive and Analog recordings? What’s the difference between them?</li>
<li>When do you use Break Points?</li>
<li>When do you use Verify/Debug/Update Modes?</li>
<li>How do you invoke an application using TSL?<br /><a name='more'></a></li>
<li>How do you link a Data Table in your script?</li>
<li>Advantages of WinRunner over other market tools silk, robot etc.?</li>
<li>Defined Functions available in WinRunner?</li>
<li>Difference between WinRunner and Test Director?</li>
<li>Does WinRunner help you in web testing?</li>
<li>Explain WinRunner Testing Modes?</li>
<li>Does load testing possible using WinRunner?</li>
<li>Explain data parameterization in WinRunner.</li>
<li>How do you define WinRunner on your own?</li>
<li>Explain the project tree in Test Director.</li>
<li>Have you completed the CPS exam? Which one?</li>
<li>How TSL looks like?</li>
<li>How do you check GUI objects?</li>
<li>How do you check a bitmap?</li>
<li>How do you define an Exception for complete application or for a particular function?</li>
<li>What are all the different platforms that WinRunner can be used?</li>
<li>What are all the different types of recordings available in WinRunner?</li>
<li>How do you forcibly capture an Object using WinRunner (when WinRunner not able identify it)?</li>
<li>Any knowledge of Test Director?</li>
<li>What are all the types of applications WinRunner can use?</li>
<li>What are data driven tests & How Do you create it in WinRunner?</li>
<li>How do you read text from an application?</li>
<li>How do you run tests on a new version of WinRunner?</li>
<li>What is User Define Functions? What are all the different types of User</li>
<li>What is a batch test? How do you program a batch test?</li>
<li>What is injector in load runner?</li>
<li>What is meant by Check points? Types of Check points? In what situation will you use it?</li>
<li>How do you set a Query to get/fetch data from the DB?</li>
<li>How does Winrunner identify GUI Objects?</li>
<li>How will you synchronize tests using WinRunner? When should you synchronize? Synchronize settings?</li>
<li>Name a couple of standard web function found in the function generator? And explain their purpose.</li>
<li>Questions on TSL: How to generate Functions?</li>
<li>Besides Record and Replay what else can be done using WinRunner?</li>
<li>How do you load GUI Map Editor?</li>
<li>What are all the default codes WinRunner will generates when you start an application?</li>
<li>What are all the different DB that WinRunner can support?</li>
<li>How do you manage test data, test result?</li>
<li>How do you program tests with TSL?</li>
<li>Types of Exception available in WinRunner?</li>
<li>What are all the Limitations & Advantages of WinRunner?</li>
<li>What are different types of running a test?</li>
<li>What are the other codes you can write/call with in TSL? 56. What are all the different languages can be called using TSL in between the scripts?</li>
<li>What are the two GUI Map modes available in WinRunner?</li>
<li>What databases can Test Director reside on?</li>
<li>What happens when user interface changes?</li>
<li>What is Function? Types of Functions?</li>
<li>What is Module? What’s Compiled Module?</li>
<li>What is TSL? What 4GL is it similar too?</li>
<li>What is Toggle Break Points? How it differ from Break points?</li>
<li>What is meant by Function Generator? (F7).</li>
<li>What is meant by GUI Spy?</li>
<li>What is meant by Synchronization? How do you implement it in WinRunner?</li>
<li>What is the use of rapid test script wizard?</li>
<li>What’s Step and Step into?</li>
<li>What’s the File Format used in Data Table?</li>
<li>What’s the WinRunner version number you used for your applications?</li>
<li>What’s the purpose of the wrun.ini file?</li>
<li>What’s the role of GUI Map Editor? (Its connects logical name in the script to the physical attributes of the object in the GUI Map Editor).</li>
<li>What’s the types application you working on using WinRunner?</li>
<li>What’s the use of GUI Map Editor?</li>
<li>Where do you use Private/Public function in your script?</li>
<li>Where you find that you can’t use WinRunner for automation?</li>
<li>WinRunner is suitable for which type of applications?</li>
<li>Winrunner GUI map modes?</li>
<li>Write a short compiled module which selects random numbers; and what function is used to call your customized compiled module?</li>
</ol>
</div>
Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-6387540470950526449.post-17551443965842858472013-05-24T00:14:00.000+05:302013-07-06T15:25:21.506+05:30Advantages and Dis-advantages of V-model<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: left;">
<span style="text-align: justify;">Advantages of V-model (SDLC)</span></h2>
<div style="text-align: justify;">
These are the advantages V-Model offers in front of other systems development models:</div>
<div style="text-align: justify;">
<br /></div>
<ul style="text-align: justify;">
<li>The users of the V-Model participate in the development and maintenance of The V-Model. A change control board publicly maintains the V-Model. The change control board meets anywhere from every day to weekly and processes all change requests received during system development and test.</li>
<li>The V-Model provides concrete assistance on how to implement an activity and its work steps, defining explicitly the events needed to complete a work step: each activity schema contains instructions, recommendations and detailed explanations of the activity.</li>
</ul>
<div style="text-align: justify;">
<a name='more'></a><br /></div>
<div style="text-align: justify;">
<h2>
Limitations or Dis-advantages of V-model (SDLC)</h2>
</div>
<div style="text-align: justify;">
The following aspects are not covered by the V-Model, they must be regulated in addition, or the V-Model must be adapted accordingly:</div>
<div style="text-align: justify;">
<br /></div>
<ul style="text-align: justify;">
<li>The placing of contracts for services is not regulated.</li>
<li>The organization and execution of operation, maintenance, repair and disposal of the system are not covered by the V-Model. However, planning and preparation of a concept for these tasks are regulated in the V-Model.</li>
<li>The V-Model addresses software development within a project rather than a whole organization.</li>
</ul>
<div style="text-align: justify;">
<blockquote class="tr_bq">
Check about <a href="http://www.jobsnewstoday.com/2013/04/advantages-disadvantages-of-waterfall-model.html" target="_blank">Advantages and Dis-advantages of Waterfall Model</a> and <a href="http://www.jobsnewstoday.com/2013/04/v-model-sdlc.html" target="_blank">V-model</a> and<br />
<a href="http://www.jobsnewstoday.com/2013/04/what-is-waterfall-model.html" target="_blank">Waterfall model</a></blockquote>
</div>
</div>
Unknownnoreply@blogger.com6tag:blogger.com,1999:blog-6387540470950526449.post-25356656507929310472013-05-24T00:00:00.000+05:302013-07-06T15:25:14.262+05:30All (100) Types of Software Testing<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: center;">
All (100) Types of Software Testing</h2>
<div style="text-align: justify;">
Below is an exhaustive list of “types of software testing” and a brief description about each type of software testing, like load testing, stress testing, unit testing, system testing, acceptance testing, certification testing, performance testing, user acceptance testing, penetration testing, automated testing, beta testing, compatibility testing, security testing, benchmark testing, functional testing, negative testing, destructive testing, integration testing, regression testing, alpha testing, end-to-end testing, path testing, smoke testing, black box testing, stability testing, usability testing etc., and many more, about 100 software testing types with descriptions are listed below.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
Why there are so many types of software testing ?</h3>
<div style="text-align: justify;">
Quality of software is assessed in terms of 6 Quality factors (Functionality, Reliability, Efficiency, Usability, Maintainability and Portability). Each of below listed type of software testing is designed to validate software for one or more of the mentioned quality factors. More types of software testing have evolved to keep up with the pace with rapid increase in complexity of the software design, frameworks & Programming languages, increased number of users with popularity of internet, advent of new platforms and technologies. With increase in number of software testing types to be performed, need for software testing tools has increased as well.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
1.<span class="Apple-tab-span" style="white-space: pre;"> </span>Ad-hoc testing :</h3>
<div style="text-align: justify;">
This is a informal type of software testing that is performed by software testers, business analyst, developers or any stake holder without referring to test cases or documentation. Person performing ad-hoc testing usually has a good understanding of software requirements and tries to break the software and find defects with the experience and knowledge they have about the domain, requirements and functionality of the software. Ad hoc testing is intended to find defects that were not found by existing test cases.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
2.<span class="Apple-tab-span" style="white-space: pre;"> </span>Acceptance testing:</h3>
<div style="text-align: justify;">
This is a formal type of software testing that is performed by end customer to check if the software confirms to their business needs and to the requirements provided earlier. Acceptance tests are usually documented; however end customers may not document test cases for smaller version or releases.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
3.<span class="Apple-tab-span" style="white-space: pre;"> </span>Accessibility testing:</h3>
<div style="text-align: justify;">
This is a formal type of software testing that helps to determine whether the software can be used by people with disability. Disability can be blind, deaf, color blindness, learning disability etc. There are also companies and consultants that provide website accessibility audits.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
4.<span class="Apple-tab-span" style="white-space: pre;"> </span>Aging testing:</h3>
<div style="text-align: justify;">
This is a type of performance testing that is carried out by running software for longer duration like weeks or months and check performance of software to see if the software performance degrades or shows any signs of degradation after running for a longer period of time. Aging Test is also known as Soak testing and also known as longevity testing.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
5.<span class="Apple-tab-span" style="white-space: pre;"> </span>Alpha Testing:</h3>
<div style="text-align: justify;">
This is a formal type of testing that is performed by end customers at development site. Alpha testing is conducted before taking the software to Beta testing.</div>
<div style="text-align: justify;">
<br />
<a name='more'></a><br /></div>
<h3 style="text-align: left;">
6.<span class="Apple-tab-span" style="white-space: pre;"> </span>Agile Testing:</h3>
<div style="text-align: justify;">
This is a type of software testing that accommodates agile software development approach. Agile development treats testing as an integral part of software development and to be done along with coding. Agile testing allows incremental and iterative coding and testing.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
7.<span class="Apple-tab-span" style="white-space: pre;"> </span>API Testing:</h3>
<div style="text-align: justify;">
API testing is a type of testing that is similar to unit testing. Each of the Software APIs are tested as per API specification. API testing is mostly done by testing team unless APIs to be tested or complex and needs extensive coding. API testing requires understanding both API functionality and possessing good coding skills.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
8.<span class="Apple-tab-span" style="white-space: pre;"> </span>Automated testing:</h3>
<div style="text-align: justify;">
This is a testing approach that makes use of testing tools and/or programming to run the test cases using software or custom developed test utilities. Most of the automated tools provided capture and playback facility, however there are tools that require writing extensive scripting or programming to automate test cases.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
9.<span class="Apple-tab-span" style="white-space: pre;"> </span> All Pairs testing:</h3>
<div style="text-align: justify;">
Also known as Pair wise testing, is a black box testing approach and a testing method where in for each input is tested in pairs of inputs, which helps to test software works as expected with all possible input combinations.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
10.<span class="Apple-tab-span" style="white-space: pre;"> </span>Beta Testing:</h3>
<div style="text-align: justify;">
This is a formal type of software testing that is carried out by end customers before releasing or handing over software to end users. Successful completion of Beta testing means customer acceptance of the software.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
11.<span class="Apple-tab-span" style="white-space: pre;"> </span>Black Box testing:</h3>
<div style="text-align: justify;">
Black box testing is a software testing method where in testers are not required to know coding or internal structure of the software. Black box testing method relies on testing software with various inputs and validating results against expected output.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
12.<span class="Apple-tab-span" style="white-space: pre;"> </span>Backward Compatibility Testing:</h3>
<div style="text-align: justify;">
Type of software testing performed to check newer version of the software can work successfully installed over previous version of the software and newer version of the software works as fine with table structure, data structures, files that were created by previous version of the software.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
13.<span class="Apple-tab-span" style="white-space: pre;"> </span>Boundary Value Testing (BVT):</h3>
<div style="text-align: justify;">
Boundary Value Testing is a testing technique that is based on concept “error aggregates at boundaries”. In this testing technique, testing is done extensively to check for defects at boundary conditions. If a field accepts value 1 to 100 then testing is done for values 0, 1, 2, 99, 100 and 101.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
14.<span class="Apple-tab-span" style="white-space: pre;"> </span>Big Bang Integration testing:</h3>
<div style="text-align: justify;">
This is one of the integration testing approaches, in Big Bang integration testing all or all most all of the modules are developed and then coupled together.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
15.<span class="Apple-tab-span" style="white-space: pre;"> </span>Bottom up Integration testing:</h3>
<div style="text-align: justify;">
Bottom up integration testing is an integration testing approach where in testing starts with smaller pieces or sub systems of the software till all the way up covering entire software system. Bottom up integration testing begins with smaller portion of the software and eventually scale up in terms of size, complexity and completeness.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
16.<span class="Apple-tab-span" style="white-space: pre;"> </span>Branch Testing:</h3>
<div style="text-align: justify;">
Is a white box testing method for designing test cases to test code for every branching condition. Branch testing method is applied during unit testing.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
17.<span class="Apple-tab-span" style="white-space: pre;"> </span>Basis path testing:</h3>
<div style="text-align: justify;">
Is a white box testing method for designing test cases to test code for every execution path of code at least once. Basis path testing method is applied during unit testing.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
18.<span class="Apple-tab-span" style="white-space: pre;"> </span>Browser compatibility Testing (BCT) : </h3>
<div style="text-align: justify;">
Its one of the sub types of testing of compatibility testing performed by testing team. Browser compatibility testing is performed for web applications with combination of different browsers and operating systems.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
19.<span class="Apple-tab-span" style="white-space: pre;"> </span>Benchmark testing:</h3>
<div style="text-align: justify;">
This is one of the types of testing performed by testing team, objective of benchmark testing is to measure performance of different versions of the software with predefined configuration (hardware and Operating system)configuration.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
20.<span class="Apple-tab-span" style="white-space: pre;"> </span>Binary portability testing: </h3>
<div style="text-align: justify;">
Binary portability testing is one of the types of comp ability testing which tests compatibility of binary or executable files from one hardware and/or operating system to other for e.g. win 2000 to windows xp etc.,</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
21.<span class="Apple-tab-span" style="white-space: pre;"> </span>Compatibility testing: </h3>
<div style="text-align: justify;">
Compatibility testing is one of the test types performed by testing team. Compatibility testing checks if the software can be run on different hardware, operating system, bandwidth, databases, web servers, application servers, hardware peripherals, emulators, different configuration, processor, different browsers and different versions of the browsers etc.,</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
22.<span class="Apple-tab-span" style="white-space: pre;"> </span>Certification testing: </h3>
<div style="text-align: justify;">
Certification testing is also related to Compatibility testing, however product will be certified as fit to use. Certification is applicable for hardware, Operating systems or Browser. e.g. hardware/laptops are certified for Windows 7 etc.,</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
23.<span class="Apple-tab-span" style="white-space: pre;"> </span>Configuration Testing: </h3>
<div style="text-align: justify;">
Configuration testing is a type of testing which is used for performance testing as well as for performance tuning by finding optimal configuration settings that can make software perform at its best for hardware or for a given operating system.</div>
<h3 style="text-align: left;">
<br />24.<span class="Apple-tab-span" style="white-space: pre;"> </span>Component Testing: </h3>
<div style="text-align: justify;">
is a type of software testing performed by developers. Component testing is carried out after completing unit testing. Component testing involves testing a group of units as code together as a whole rather than testing individual functions, methods.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
25.<span class="Apple-tab-span" style="white-space: pre;"> </span>Compliance Testing: </h3>
<div style="text-align: justify;">
is a type of software testing performed by external agencies, external standards body and can be done by testers as well. Objective of compliance testing is to test software meets the required standards, government laws, company policies etc.,</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
26.<span class="Apple-tab-span" style="white-space: pre;"> </span>Concurrency Testing: </h3>
<div style="text-align: justify;">
is type of software testing performed by performance test engineers, objective of concurrency testing is to check if application performs as expected when multiple users use the software, logins, features and database etc.,</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
27.<span class="Apple-tab-span" style="white-space: pre;"> </span>Comparison Testing:</h3>
<div style="text-align: justify;">
is a type of software testing performed to compare features, pros and cons of the product with competitor products or different versions of the product. This type of testing is usually done by Business analysts or marketing analysts.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
28.<span class="Apple-tab-span" style="white-space: pre;"> </span>Conformance Testing: </h3>
<div style="text-align: justify;">
is a type of software testing performed by external agencies or standards body. Conformance testing is done to endorse a product that it meets the requirements it was supposed to fulfill. e.g.: Mobile devices to restrict to a limit of electromagnetic radiation emission.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
29.<span class="Apple-tab-span" style="white-space: pre;"> </span>Conversion Testing: </h3>
<div style="text-align: justify;">
is a type of software testing performed by testers to check programs or software used for converting data from existing systems to new or replacement systems. e.g.: Existing Insurance software developed in java is being replace by SAP implementation, in this case existing data has to be converted, and migrated to SAP.</div>
<h3 style="text-align: left;">
<br />30.<span class="Apple-tab-span" style="white-space: pre;"> </span>Code-driven Testing: </h3>
<div style="text-align: justify;">
is related to types of testing that makes uses of frameworks like Junit, XUnit, Nunit used for Unit testing.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
31.<span class="Apple-tab-span" style="white-space: pre;"> </span>Condition Coverage Testing: </h3>
<div style="text-align: justify;">
Condition coverage testing is a testing technique used during unit testing, where in developer tests for all the condition statements like if, if else, case etc., in the code being unit tested.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
32.<span class="Apple-tab-span" style="white-space: pre;"> </span>Dynamic Testing: </h3>
<div style="text-align: justify;">
Testing can be performed as Static Testing and Dynamic testing, Dynamic testing is a testing approach where-in testing can be done only by executing code or software are classified as Dynamic Testing. Unit testing, Functional testing, regression testing, performance testing etc.,</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
33.<span class="Apple-tab-span" style="white-space: pre;"> </span>Documentation testing: </h3>
<div style="text-align: justify;">
is a type of Static testing in which project documents are checked for thoroughness and completeness. Documentation testing can range from doing spell, grammar check, reading the document from end user perspective, reading the documenting thoroughly understanding and looking for any ambiguous statements, checking documents that are technical in nature like installation documents for its simplicity and completeness. Documentation will also include EULA (End user license agreements), user guides, Admin guides, installation guides etc.</div>
<h3 style="text-align: left;">
<br />34.<span class="Apple-tab-span" style="white-space: pre;"> </span>Decision Coverage Testing: </h3>
<div style="text-align: justify;">
Is a testing technique that is used in Unit testing, objective of decision coverage testing is to expertise and validate each and every decisions made in the code e.g. if, if else, case statements.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
35.<span class="Apple-tab-span" style="white-space: pre;"> </span>Destructive Testing: </h3>
<div style="text-align: justify;">
Destructive testing is a type of testing which is performed by testing team, Destructive testing is intended to find failure points of a software, be it by inputting incorrect data, inputting corrupt data, incorrect format, by volume or by number requests etc.,</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
36.<span class="Apple-tab-span" style="white-space: pre;"> </span>Domain Testing: </h3>
<div style="text-align: justify;">
Domain testing is a software testing technique, Objective of domain testing is to select test cases of critical functionality of the software and execute them. Domain testing does not intend to run all the existing test cases.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
37.<span class="Apple-tab-span" style="white-space: pre;"> </span>Dependency Testing: </h3>
<div style="text-align: justify;">
Is type of testing which can be applied to components, web services, software services, software, APIs, intent of the dependency testing it to check the configuration, input and output sent by base application to dependent services or softwares are as per specification.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
38.<span class="Apple-tab-span" style="white-space: pre;"> </span>End-to-end Testing: </h3>
<div style="text-align: justify;">
End to end testing is performed by testing team, focus of end to end testing is to test end to end flows e.g. right from order creation till reporting or order creation till item return etc and checking ., End to end testing is usually focused mimicking real life scenarios and usage. End to end testing involves testing information flow across applications.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
39.<span class="Apple-tab-span" style="white-space: pre;"> </span>Exploratory Testing: </h3>
<div style="text-align: justify;">
Exploratory testing is an informal type of testing conducted to learn the software at the same time looking for errors or application behavior that seems non-obvious. Exploratory testing is usually done by testers but can be done by other stake holders as well like Business Analysts, developers, end users etc. who are interested in learning functions of the software and at the same time looking for errors or behavior is seems non-obvious.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
40.<span class="Apple-tab-span" style="white-space: pre;"> </span>Endurance Testing: </h3>
<div style="text-align: justify;">
Endurance testing is also known as soak testing, longevity testing. Endurance testing is usually performed by performance testing team. Endurance testing is done to check if software can withstand expected load on continuous basis for reasonable longer duration of time, say about a week or a month. During Endurance testing, performance issues or memory leaks that can be discovered and this is the intent of the endurance testing.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
41.<span class="Apple-tab-span" style="white-space: pre;"> </span>Equivalence Partitioning: </h3>
<div style="text-align: justify;">
Equivalence partitioning is also known as Equivalence Class Partitioning is a software testing technique and not a type of testing by itself. Equivalence partitioning technique is used in black box and grey box testing types. Equivalence partitioning classifies test data into Equivalence classes as positive Equivalence classes and negative Equivalence classes, such classification ensures both positive and negative conditions are tested.</div>
<h3 style="text-align: left;">
<br />42.<span class="Apple-tab-span" style="white-space: pre;"> </span>Error-Handling Testing: </h3>
<div style="text-align: justify;">
Is a type of testing that focuses on error handling capabilities of software, this type of testing that focuses on response of the software and message it displays to uses incase of expected and un-expected errors.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
43.<span class="Apple-tab-span" style="white-space: pre;"> </span>Functional Testing: </h3>
<div style="text-align: justify;">
Functional testing is a formal type of testing performed by testers. Functional testing focuses on testing software against design document, Use cases and requirements document. Functional testing is a black box type of testing and does not require internal working of the software unlike white box testing.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
44.<span class="Apple-tab-span" style="white-space: pre;"> </span>Fault injection Testing: </h3>
<div style="text-align: justify;">
Fault injection Testing is a type of testing that done by testing team with help of development team. Faults or errors are induced in the application and existing tests are executed, in case the introduced errors are caught, that means existing tests are good and robust else additional tests have to be included. Fault injection testing is very important incase of defense, aerospace, medical or any critical software that can lead to financial or loss of life.</div>
<div style="text-align: justify;">
<br /></div>
<h3>
45.<span class="Apple-tab-span" style="white-space: pre;"> </span>failover testing: </h3>
<div style="text-align: justify;">
is a type of software testing which focuses on testing functionality or features that enable software to recover from some of the anticipated failures like web server failure, hardware or network failure, or web services not available or not responding etc.,</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
46.<span class="Apple-tab-span" style="white-space: pre;"> </span>Forward Compatibility Testing: </h3>
<div style="text-align: justify;">
is a type of software testing that is done to check if the software works as expected when software is downgraded from higher version to lower version for e.g. Presume you installed new version of Internet explorer 9.0 and due to some reason you are not comfortable or you find that new version I.E 9.0 is not working as expected, then you would downgrade to I.E. 8.0 and as a end user you will expect that I.E 8.0 works as earlier with all the favorites and browser add-ons intact. Software development companies provide forward compatibility testing in mind when there are going in for a major release and incase due to any issue (software, hardware or configuration) user should still have an option to go back to previous version of the software.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
47.<span class="Apple-tab-span" style="white-space: pre;"> </span>Fuzz Testing: </h3>
<div style="text-align: justify;">
Fuzz testing or fuzzing is a software testing technique that involves testing with unexpected or random inputs. Software is monitored for failures or error messages that are presented due to the input errors.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
48.<span class="Apple-tab-span" style="white-space: pre;"> </span>GUI (Graphical User Interface) testing: </h3>
<div style="text-align: justify;">
is aimed at testing the software GUI (Graphical User Interface) of the software meets the requirements as mentioned in the GUI mockups and Detailed designed documents. For e.g. checking the length and capacity of the input fields provided on the form, type of input field provided, e.g. some of the form fields can be displayed as dropdown box or a set of radio buttons. So GUI testing ensures GUI elements of the software are as per approved GUI mockups, detailed design documents and functional requirements. Most of the functional test automation tools work on GUI capture and playback capabilities. This makes script recording faster at the same time increases the effort on script maintenance.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
49.<span class="Apple-tab-span" style="white-space: pre;"> </span>Glass box Testing: </h3>
<div style="text-align: justify;">
Glass box testing is another name for White box testing. Glass box testing is a testing method that involves testing individual statements, functions etc., Unit testing is one of the Glass box testing methods.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
50.<span class="Apple-tab-span" style="white-space: pre;"> </span>Globalization Testing: </h3>
<div style="text-align: justify;">
Globalization testing is a type of testing which detects problems with in application design related to usage of the software with different languages, different character sets. Software used should not crash and should not be able to display information correctly. Globalization testing is applicable for software that is used by people across different geographies and different language.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
51.<span class="Apple-tab-span" style="white-space: pre;"> </span>Gorilla Testing: </h3>
<div style="text-align: justify;">
is a type of software testing done by software testing team, has a scary name though ?. Objective of Gorilla Testing is to exercise one or few functionality thoroughly or exhaustively by having multiple people test the same functionality.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
52.<span class="Apple-tab-span" style="white-space: pre;"> </span>Hybrid Integration Testing: </h3>
<div style="text-align: justify;">
Also known as sand witch testing is a combination of both bottom up and top down integration testing techniques. By combining both of these once can find more defects at the same time provide better integration test coverage.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
53.<span class="Apple-tab-span" style="white-space: pre;"> </span>Happy path testing: </h3>
<div style="text-align: justify;">
Also known as Golden path testing, this type of testing focuses on selective execution of tests that do not exercise the software for negative or error conditions.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
54.<span class="Apple-tab-span" style="white-space: pre;"> </span>Integration Testing: </h3>
<div style="text-align: justify;">
Integration testing also known as I&T in short, in one of the important types of software testing. Once the individual units or components are tested by developers as working then testing team will run tests that will test the connectivity among these units/component or multiple units/components. There are different approaches for Integration testing namely, Top-down integration testing, Bottom-up integration testing and a combination of these two known as Sand witch testing.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
55.<span class="Apple-tab-span" style="white-space: pre;"> </span>Interface Testing: </h3>
<div style="text-align: justify;">
Software provides support for one or more interfaces like “Graphical user interface”, “Command Line Interface” or “Application programming interface” to interact with its users or other software. Interfaces serves as medium for software to accept input from user and provide result. Approach for interface testing depends on the type of the interface being testing like GUI or API or CLI.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
56.<span class="Apple-tab-span" style="white-space: pre;"> </span>Internationalization Testing: </h3>
<div style="text-align: justify;">
Internationalization testing is a type of testing that is performed by software testing team to check the extent to which software can support Internationalization i.e., usage of different languages, different character sets, double byte characters etc., For e.g.: Gmail, is a web application that is used by people all over work with different languages, single by or multi byte character sets.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
57.<span class="Apple-tab-span" style="white-space: pre;"> </span>I18n Testing: </h3>
<div style="text-align: justify;">
I18n refers to Internationalization Testing, in the word “Internationalization”, between letters “I” and “n” there are about 18 letters, hence the name i18n.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
58.<span class="Apple-tab-span" style="white-space: pre;"> </span>Installation/un-installation Testing: </h3>
<div style="text-align: justify;">
Installation/un-installation Testing is a type of testing performed by testing team to find defects related to installation and un-installation of software. This type of testing is very important for packaged software applications (off the shelf software applications) where-in end users are expected to install the software. This testing would involve executing software installer in different modes like “express” or “custom” modes and on different types of environments like virtual operating systems and on different operating systems. Installation/un-installation Testing may also require updating software configuration files.</div>
<div style="text-align: justify;">
<br /></div>
<h3>
59.<span class="Apple-tab-span" style="white-space: pre;"> </span>Keyword-driven Testing: </h3>
<div style="text-align: justify;">
Keyword driver testing is more of a automated software testing approach than a type of testing itself. Keyword driven testing is known as action driven testing or table driven testing.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
60.<span class="Apple-tab-span" style="white-space: pre;"> </span>Load Testing: </h3>
<div style="text-align: justify;">
Load testing is a type of non-functional testing; load testing is done to check the behavior of the software under normal and over peak load conditions. Load testing is usually performed using automated testing tools. Load testing intends to find bottlenecks or issues that prevent software from performing as intended at its peak workloads.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
61.<span class="Apple-tab-span" style="white-space: pre;"> </span>Localization Testing: </h3>
<div style="text-align: justify;">
Localization testing a type of software testing performed by software testers, in this type of testing, software is expected to adapt to a particular locale, it should support a particular locale/language in terms of display, accepting input in that particular locale, display, font, date time, currency etc., related to a particular locale. For e.g. many web applications allow choice of locale like English, French, German or Japanese. So once locale is defined or set in the configuration of software, software is expected to work as expected with a set language/locale.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
62.<span class="Apple-tab-span" style="white-space: pre;"> </span>Loop Testing: </h3>
<div style="text-align: justify;">
Loop testing is a type of white box testing technique, it is one of the most commonly used white box testing technique while performing unit testing.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
63.<span class="Apple-tab-span" style="white-space: pre;"> </span>Monkey testing: </h3>
<div style="text-align: justify;">
Monkey testing is a type of testing that can be performed by software testing team or new users of the software. Objective of monkey testing is to use the software without any specific tests in mind. Monkey test tries to break the software by entering incorrect dates like 31-Feb-2012 or long strings of text or numbers or special characters etc.,</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
64.<span class="Apple-tab-span" style="white-space: pre;"> </span>Negative Testing:</h3>
<div style="text-align: justify;">
is a type of software testing approach, which calls out the “attitude to break”, these are functional and non-functional tests that are intended to break the software by entering incorrect data like incorrect date, time or string or upload binary file when text files supposed to be upload or enter huge text string for input fields etc.,</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
65.<span class="Apple-tab-span" style="white-space: pre;"> </span>Non functional testing: </h3>
<div style="text-align: justify;">
Software are built to fulfill functional and non-functional requirements, non-functional requirements like performance, usability, localization etc., There are many types of testing like compatibility testing, compliance testing, localization testing, usability testing, volume testing etc., that are carried out for checking non-functional requirements.</div>
<h3 style="text-align: left;">
<br />66.<span class="Apple-tab-span" style="white-space: pre;"> </span>ORT (Operational readiness testing): </h3>
<div style="text-align: justify;">
Operational readiness testing also known as pre go live testing is usually performed by software testers. As the name suggests, Operational readiness testing intends to validate the production environment after new version of the software is deployed in production environment. Software testers test the existing and new functionality to certify that the software is ready to be used by end users.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
67.<span class="Apple-tab-span" style="white-space: pre;"> </span>Orthogonal array Testing: </h3>
<div style="text-align: justify;">
is a black box testing technique. Orthogonal array Testing is statistical and systematic way of Software testing. Orthogonal array Testing technique helps to minimize the number of test cases and maximize test coverage by grouping set of test conditions. Orthogonal testing is effective in case of GUI testing, Configuration testing where there are multiple input parameters and testing one parameter at a time would lead to large number of test cases.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
68.<span class="Apple-tab-span" style="white-space: pre;"> </span>Pair Testing: </h3>
<div style="text-align: justify;">
is a software testing technique that can be done by software testers, developers or Business analysts (BA). As the name suggests, two people are paired together, one to test and other to monitor and record test results. Pair testing can also be performed in combination of tester-developer, tester-business analyst or developer-business analyst combination. Combining testers and developers in pair testing helps to detect defects faster, identify root cause, fix and test the fix.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
69.<span class="Apple-tab-span" style="white-space: pre;"> </span>Parallel Testing: </h3>
<div style="text-align: justify;">
is a software testing technique, where in you test two or more versions of the software “the current version” and “previous version or versions” of the software together to see the differences of existing functionality.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
70.<span class="Apple-tab-span" style="white-space: pre;"> </span>Path Testing: </h3>
<div style="text-align: justify;">
is a type of software testing technique that is used as part of white box testing approach. Objective of path testing is to exercise and test each of the branch statements. These testing techniques are applied by developers while performing Unit testing.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
71.<span class="Apple-tab-span" style="white-space: pre;"> </span>Performance Testing: </h3>
<div style="text-align: justify;">
is a type of software testing and part of performance engineering that is performed to check some of the quality attributes of software like Stability, reliability, availability. Performance testing is carried out by performance engineering team. Unlike Functional testing, Performance testing is done to check non-functional requirements. Performance testing checks how well software works in anticipated and peak workloads. There are different variations or sub types of performance like load testing, stress testing, volume testing, soak testing and configuration testing.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
72.<span class="Apple-tab-span" style="white-space: pre;"> </span>Penetration Testing: </h3>
<div style="text-align: justify;">
is a type of security testing, also known as pentest in short. Penetration testing is done to tests how secure software and its environments (Hardware, Operating system and network) are when subject to attack by an external or internal intruder. Intruder can be a human/hacker or malicious programs. Pentest uses methods to forcibly intrude (by brute force attack) or by using a weakness (vulnerability) to gain access to a software or data or hardware with an intent to expose ways to steal, manipulate or corrupt data, software files or configuration. Penetration Testing is a way of ethical hacking, an experienced Penetration tester will use the same methods and tools that a hacker would use but the intention of Penetration tester is to identify vulnerability and get them fixed before a real hacker or malicious program exploits it.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
73.<span class="Apple-tab-span" style="white-space: pre;"> </span>Ramp Testing: </h3>
<div style="text-align: justify;">
is a type of testing conducted to check the response of the software with constant increase in workload on the software. Ramp testing enables tests the ability of the software to sustain gradual increase in work load.</div>
<h3 style="text-align: left;">
<br />74.<span class="Apple-tab-span" style="white-space: pre;"> </span>Regression Testing: </h3>
<div style="text-align: justify;">
is a type of software testing that is carried out by software testers as functional regression tests and developers as Unit regression tests. Objective of regression tests are to find defects that got introduced to defect fix(es) or introduction of new feature(s). Regression tests are ideal candidate for automation.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
75.<span class="Apple-tab-span" style="white-space: pre;"> </span>Retesting: </h3>
<div style="text-align: justify;">
is a type of retesting that is carried out by software testers as a part of defect fix verification. For e.g. a tester is verifying a defect fix and let us say that there are 3 test cases failed due to this defect. Once tester verifies defect fix as resolved, tester will retest or test the same functionality again by executing the test cases that were failed earlier.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
76.<span class="Apple-tab-span" style="white-space: pre;"> </span>Resilience testing: </h3>
<div style="text-align: justify;">
is a type of testing carried by performance engineering team to assess how stable the software is when it is subject to incorrect data, large workloads and more volume of data to be processes.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
77.<span class="Apple-tab-span" style="white-space: pre;"> </span>Recovery Testing: </h3>
<div style="text-align: justify;">
is a type of testing performed by software testers. Recovery testing aims at checking how soon and how efficiently software can recover from software crashes, Operating system crashers, and hardware failures. Recovery testing is not the same as fail rover testing or reliability testing.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
78.<span class="Apple-tab-span" style="white-space: pre;"> </span>Risk based Testing: </h3>
<div style="text-align: justify;">
is a type of software testing and an different approach towards testing a software. In Risk based testing, requirements and functionality of software to be tested are prioritized as Critical, High, Medium and low. In this approach, all critical and High priority tests are tested and them followed by Medium. Low priority or low risk functionality are tested at the end or may not based on the time available for testing.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
79.<span class="Apple-tab-span" style="white-space: pre;"> </span>Smoke testing: </h3>
<div style="text-align: justify;">
is a type of testing that is carried out by software testers to check if the new build provided by development team is stable enough i.e., major functionality is working as expected in order to carry out further or detailed testing. Smoke testing is intended to find “show stopper” defects that can prevent testers from testing the application in detail. Smoke testing carried out for a build is also known as build verification test.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
80.<span class="Apple-tab-span" style="white-space: pre;"> </span>Security Testing: </h3>
<div style="text-align: justify;">
is a type of software testing carried out by specialized team of software testers. Objective of security testing is to secure the software is to external or internal threats from humans and malicious programs. Security testing basically checks, how good is software’s authorization mechanism, how strong is authentication, how software maintains confidentiality of the data, how does the software maintain integrity of the data, what is the availability of the software in an event of an attack on the software by hackers and malicious programs is for Security testing requires good knowledge of application, technology, networking, security testing tools. With increasing number of web applications necessarily of security testing has increased to a greater extent.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
81.<span class="Apple-tab-span" style="white-space: pre;"> </span>Sanity Testing: </h3>
<div style="text-align: justify;">
is a type of testing that is carried out mostly by testers and in some projects by developers as well. Sanity testing is a quick evaluation of the software, environment, network, external systems are up & running, software environment as a whole is stable enough to proceed with extensive testing. Sanity tests are narrow and most of the time sanity tests are not documented.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
82.<span class="Apple-tab-span" style="white-space: pre;"> </span>Scalability Testing: </h3>
<div style="text-align: justify;">
is a non functional test intended to test one of the software quality attributes i.e. “Scalability”. Scalability test is not focused on just one or few functionality of the software instead performance of software as a whole. Scalability testing is usually done by performance engineering team. Objective of scalability testing is to test the ability of the software to scale up with increased users, increased transactions, increase in database size etc., It is not necessary that software’s performance increases with increase in hardware configuration, scalability tests helps to find out how much more workload the software can support with expanding user base, transactions, data storage etc.,</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
83.<span class="Apple-tab-span" style="white-space: pre;"> </span>Stability Testing: </h3>
<div style="text-align: justify;">
is a non functional test intended to test one of the software quality attributes i.e. “Stability”. Stability testing focuses on testing how stable software is when it is subject to loads at acceptable levels, peak loads, loads generated in spikes, with more volumes of data to be processed. Scalability testing will involve performing different types of performance tests like load testing, stress testing, spike testing, soak testing, spike testing etc.,</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
84.<span class="Apple-tab-span" style="white-space: pre;"> </span>Structural testing: </h3>
<div style="text-align: justify;">
is an alias for White box testing. Refer to white box testing for more details.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
85.<span class="Apple-tab-span" style="white-space: pre;"> </span>Static Testing: </h3>
<div style="text-align: justify;">
is a form of testing where in approaches like reviews, walkthroughs are employed to evaluate the correctness of the deliverable. In static testing software code is not executed instead it is reviewed for syntax, commenting, naming convention, size of the functions and methods etc. Static testing usually has check lists against which deliverables are evaluated. Static testing can be applied for requirements, designs, test cases by using approaches like reviews or walkthroughs.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
86.<span class="Apple-tab-span" style="white-space: pre;"> </span>Stress Testing: </h3>
<div style="text-align: justify;">
is a type of performance testing, in which software is subjected to peak loads and even to a break point to observe how the software would behave at breakpoint. Stress testing also tests the behavior of the software with insufficient resources like CPU, Memory, Network bandwidth, Disk space etc. Stress testing enables to check some of the quality attributes like robustness and reliability.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
87.<span class="Apple-tab-span" style="white-space: pre;"> </span>System Testing: </h3>
<div style="text-align: justify;">
this includes multiple software testing types that will enable to validate the software as a whole (software, hardware and network) against the requirements for which it was built. Different types of tests (GUI testing, Functional testing, Regression testing, Smoke testing, load testing, stress testing, security testing, stress testing, ad-hoc testing etc.,) are carried out to complete system testing.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
88.<span class="Apple-tab-span" style="white-space: pre;"> </span>Soak Testing: </h3>
<div style="text-align: justify;">
is a type of performance testing, where in software is subjected to load over a significant duration of time, soak testing may go on for few days or even for few weeks. Soak testing is a type of testing that is conducted to find errors that result in degeneration of software performance with continued usage. Soak testing is extensively done for electronic devices, which are expected to run continuously for days or months or years without restarting or rebooting. With growing web applications soak testing has gained significant importance as web application availability is critical for sustaining and success of business.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
89.<span class="Apple-tab-span" style="white-space: pre;"> </span>Spike Testing: </h3>
<div style="text-align: justify;">
is a type of performance testing performed by performance engineering team. Objective of spike testing is to check how software responds to workloads that are sent in very short span of time and which are not constant over period of time.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
90.<span class="Apple-tab-span" style="white-space: pre;"> </span>System Integration Testing: </h3>
<div style="text-align: justify;">
known as SIT (in short) is a type of testing conducted by software testing team. As the name suggests, focus of System integration testing is to test for errors related to integration among different applications, services, third party vendor applications etc., As part of SIT, end-to-end scenarios are tested that would require software to interact (send or receive data) with other upstream or downstream applications, services, third party application calls etc.,</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
91.<span class="Apple-tab-span" style="white-space: pre;"> </span>Transparent box testing: </h3>
<div style="text-align: justify;">
is an alias for White box testing. Refer to White box Testingfor more details.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
92.<span class="Apple-tab-span" style="white-space: pre;"> </span>Top down Integration testing: </h3>
<div style="text-align: justify;">
is one of the integration testing approaches. Top down integration testing is an incremental testing approach for integration testing where in testing of top level modules are done first before moving on to testing of branch modules. Top down integration testing helps to find design issues in the beginning of the Integration test stage.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
93.<span class="Apple-tab-span" style="white-space: pre;"> </span>Upgrade testing: </h3>
<div style="text-align: justify;">
is a type of testing that is carried out by software testers. Upgrade testing is more often carried out after an hardware upgrade or operating system upgrade or any other supporting software like JVM or Web server or application server. For e.g. if JRE is upgraded from 1.0 to 2.3.3 then the subset of the functional tests have to be executed to ensure application features are not broken due to JRE upgrade.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
94.<span class="Apple-tab-span" style="white-space: pre;"> </span>Unit testing:</h3>
<div style="text-align: justify;">
is a type of testing that is performed by software developers. Unit testing follows white box testing approach where developer will test units of source code like statements, branches, functions, methods OR class, interface in OOP (object oriented programming). Unit testing usually involves in developing stubs and drivers. Unit tests are ideal candidates for automation. Automated tests can run as Unit regression tests on new builds or new versions of the software. There are many useful unit testing frames works like Junit, Nunit etc., available that can make unit testing more effective.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
95.<span class="Apple-tab-span" style="white-space: pre;"> </span>Upward compatibility Testing:</h3>
<div style="text-align: justify;">
Upward compatibility testing is another name for forward compatibility Testing.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
96.<span class="Apple-tab-span" style="white-space: pre;"> </span>Usability testing:</h3>
<div style="text-align: justify;">
is a type of software testing that is performed to understand how user friendly the software is. Objective of usability testing is to allow end users to use the software, observe their behavior, their emotional response (whether users liked using software or were they stressed using it? etc.,) and collect their feedback on how the software can be made more useable or user friendly and incorporate the changes that make the software easier to use.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
97.<span class="Apple-tab-span" style="white-space: pre;"> </span>User Acceptance testing (UAT ):</h3>
<div style="text-align: justify;">
User Acceptance testing is a must for any project; it is performed by clients/end users of the software. User Acceptance testing allows SMEs (Subject matter experts) from client to test the software with their actual business or real-world scenarios and to check if the software meets their business requirements.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
98.<span class="Apple-tab-span" style="white-space: pre;"> </span>Volume testing:</h3>
<div style="text-align: justify;">
is a non-functional type of testing carried out by performance engineering team. Volume testing is one of the types of performance testing. Volume testing is carried out to find the response of the software with different sizes of the data being received or to be processed by the software. For e.g. If you were to be testing Microsoft word, volume testing would be to see if word can open, save and work on files of different sizes (10 to 100 MB).</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
99.<span class="Apple-tab-span" style="white-space: pre;"> </span>Vulnerability Testing:</h3>
<div style="text-align: justify;">
involves identifying, exposing the software, hardware or network Vulnerabilities that can be exploited by hackers and other malicious programs likes viruses or worms. Vulnerability Testing is key to software security and availability. With increase number of hackers and malicious programs, Vulnerability Testing is critical for success of a Business.</div>
<div style="text-align: justify;">
<br /></div>
<h3 style="text-align: left;">
100.<span class="Apple-tab-span" style="white-space: pre;"> </span>White box Testing:</h3>
<div style="text-align: justify;">
White box testing is also known as clear box testing, transparent box testing and glass box testing. White box testing is a software testing approach, which intends to test software with knowledge of internal working of the software. White box testing approach is used in Unit testing which is usually performed by software developers. White box testing intends to execute code and test statements, branches, path, decisions and data flow within the program being tested. White box testing and Black box testing complement each other as each of the testing approaches have potential to un-cover specific category of errors.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b><i>Thanks for reading. In-case any type of software testing missed out in the above list, you are welcome to add the same in comment section of this post!</i></b></div>
</div>
Unknownnoreply@blogger.com13tag:blogger.com,1999:blog-6387540470950526449.post-30429242904353740582013-05-23T00:00:00.000+05:302013-07-06T15:24:08.441+05:30Software Test Documents - Test Plan, Test Scenario, Test Case, Traceability Matrix<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: center;">
<u>Explain about Software Test Documents (a<span style="text-align: justify;">rtifacts</span>)</u></h2>
<div style="text-align: justify;">
Testing documentation involves the documentation of artifacts which should be developed before or during the testing of Software.<br />
<br /></div>
<div style="text-align: justify;">
Documentation for Software testing helps in estimating the testing effort required, test coverage, requirement tracking/tracing etc. This section includes the description of some commonly used documented artifacts related to Software testing such as:</div>
<h4 style="text-align: left;">
<ul style="text-align: left;">
<li style="text-align: justify;"><b>Test Plan</b></li>
</ul>
<ul style="text-align: left;">
<li style="text-align: justify;"><b>Test Scenario</b></li>
</ul>
<ul style="text-align: left;">
<li style="text-align: justify;"><b>Test Case</b></li>
</ul>
<ul style="text-align: left;">
<li style="text-align: justify;"><b>Traceability Matrix</b></li>
</ul>
<div style="text-align: justify;">
<a name='more'></a><br /></div>
</h4>
<h2 style="text-align: left;">
Define Test Plan</h2>
<div style="text-align: justify;">
A test plan outlines the strategy that will be used to test an application, the resources that will be used, the test environment in which testing will be performed, the limitations of the testing and the schedule of testing activities. Typically the Quality Assurance Team Lead will be responsible for writing a Test Plan.</div>
<blockquote class="tr_bq">
<b>A test plan will include the following:</b> </blockquote>
<blockquote class="tr_bq">
Test Plan id<br />
Introduction<br />
Test items<br />
Features to be tested<br />
Features not to be tested<br />
Test techniques<br />
Testing tasks<br />
Suspension criteria<br />
Features pass or fail criteria<br />
Test environment (Entry criteria, Exit criteria)<br />
Test deliverables<br />
Staff and training needs<br />
Responsibilities<br />
Schedule</blockquote>
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="clear: left; margin-bottom: 1em; margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjgU27idl_xtsFV3qT8PyMJe410kKIJdBa_eDHrjk-n4s-GG3xVsJh31rhuH7HLpsweiU78ABUTZuOFKL2FVof_4MoHePAZhSDSplvN7fKDszdGqgxSarw3Jvw9Va4AeZOSGfVPevNmFNSA/s1600/testplan-template.jpeg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img alt="testplan-template" border="0" height="258" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjgU27idl_xtsFV3qT8PyMJe410kKIJdBa_eDHrjk-n4s-GG3xVsJh31rhuH7HLpsweiU78ABUTZuOFKL2FVof_4MoHePAZhSDSplvN7fKDszdGqgxSarw3Jvw9Va4AeZOSGfVPevNmFNSA/s320/testplan-template.jpeg" title="testplan-template" width="320" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;"><b>Click on the image for Zoom view</b></td></tr>
</tbody></table>
<br />
<h2 style="text-align: left;">
Define Test Scenario</h2>
<div style="text-align: justify;">
A one line statement that tells what area in the application will be tested. Test Scenarios are used to ensure that all process flows are tested from end to end. A particular area of an application can have as little as one test scenario to a few hundred scenarios depending on the magnitude and complexity of the application.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
The term test scenario and test cases are used interchangeably however the main difference being that test scenarios has several steps however test cases have a single step. When viewed from this perspective test scenarios are test cases, but they include several test cases and the sequence that they should be executed. Apart from this, each test is dependent on the output from the previous test.</div>
<h2 style="text-align: left;">
Define Test Case</h2>
<div style="text-align: justify;">
Test cases involve the set of steps, conditions and inputs which can be used while performing the testing tasks. The main intent of this activity is to ensure whether the Software Passes or Fails in terms of its functionality and other aspects. There are many types of test cases like: functional, negative, error, logical test cases, physical test cases, UI test cases etc.</div>
<div style="text-align: justify;">
<br /></div>
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgqPtJVkzvbm14zkeCZEJlNc3krjxs0ETuLQ94mCIVwZr4u1OkEZyYwq5sWgjMSxUoaVBvdH2sM_h41VbAbex_1BLacu-sLg9q5AO_FYhE7jdw_x1lErdJhCFd8wclYS_KP8DF9rOJoUCV5/s1600/testcase_template.gif" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img alt="testcase_template" border="0" height="232" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgqPtJVkzvbm14zkeCZEJlNc3krjxs0ETuLQ94mCIVwZr4u1OkEZyYwq5sWgjMSxUoaVBvdH2sM_h41VbAbex_1BLacu-sLg9q5AO_FYhE7jdw_x1lErdJhCFd8wclYS_KP8DF9rOJoUCV5/s400/testcase_template.gif" title="testcase_template" width="400" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;"><b>Click on the image for Zoom view</b></td></tr>
</tbody></table>
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
<div style="text-align: justify;">
Furthermore test cases are written to keep track of testing coverage of Software. Generally, there is no formal template which is used during the test case writing. However, following are the main components which are always available and included in every test case:</div>
<blockquote class="tr_bq">
<b>Test case ID.<br />Product Module.<br />Product version.<br />Revision history.<br />Purpose<br />Assumptions<br />Pre-Conditions.<br />Steps.<br />Expected Outcome.<br />Actual Outcome.</b><br />
<b>Post Conditions.</b></blockquote>
<div style="text-align: justify;">
Many Test cases can be derived from a single test scenario. In addition to this, some time it happened that multiple test cases are written for single Software which is collectively known as test suites.</div>
<h2 style="text-align: left;">
Define Traceability Matrix</h2>
<div style="text-align: justify;">
Traceability Matrix (also known as Requirement Traceability Matrix - RTM) is a table which is used to trace the requirements during the Software development life Cycle. It can be used for forward tracing (i.e. from Requirements to Design or Coding) or backward (i.e. from Coding to Requirements). There are many user defined templates for RTM.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Each requirement in the RTM document is linked with its associated test case, so that testing can be done as per the mentioned requirements. Furthermore, Bug ID is also include and linked with its associated requirements and test case.</div>
<blockquote class="tr_bq">
<b>The main goals for this matrix are:</b><br />
Make sure Software is developed as per the mentioned requirements.<br />
Helps in finding the root cause of any bug.<br />
Helps in tracing the developed documents during different phases of SDLC.</blockquote>
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhkdNRaeQppr-fUEA5-FX1xVT7sK_rKdL4HFb6BD_ljix0745J37kZ2cvXGVMTlCFt_q3RJb1qvyD1zkECXbHxVzFxg55GvYA9WTbii8_hkuVQBdO108rPCehT3lY1BCCrn0oz5eE6hLNo7/s1600/sample_traceability-template.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img alt="sample_traceability-template" border="0" height="212" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhkdNRaeQppr-fUEA5-FX1xVT7sK_rKdL4HFb6BD_ljix0745J37kZ2cvXGVMTlCFt_q3RJb1qvyD1zkECXbHxVzFxg55GvYA9WTbii8_hkuVQBdO108rPCehT3lY1BCCrn0oz5eE6hLNo7/s400/sample_traceability-template.png" title="sample_traceability-template" width="400" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;"><b>Click on the image for Zoom view</b></td></tr>
</tbody></table>
<br />
<br />
<b><i>These are about Software Test Documents. </i></b></div>
Unknownnoreply@blogger.com16