<%@ Page Title="Basics of Software Testing" Language="C#" MasterPageFile="~/STMNAV.
master"
AutoEventWireup="true" CodeBehind="[Link]"
Inherits="Desamma.SoftwareTestingManual1" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">
<div class="childpage">
<meta name="description" content="Tutorial explains Basics of Software Testing" />
<meta name="keywords" content="Goal of software testing,Testing" />
<meta name="classification" content="Tutorials,Software Testing,online articles" />
<h1>Basics of Software Testing</h1>
<h2>Why Test?</h2>
Let's assume that web application which is e-commerce web site which sells xyz products.<br />
Case 1 Customer logon to website and select the product and goes payment module due to some issue
page didn’t got loaded. So the Customer logout and leaves the website. <br />
Case 2. Customer logon to website and select the product and does payment and order placed
successfully. But it has not updated in Database. Then it is again headache of user to track that
order.<br />
Let's assume that same web application if it has been tested. if above two case has been test that loss
may not be happen. That is why the application should undergo test before it goes to live or hands of
customer. <br />
<h2>Definition Software Testing</h2>
The Process of evaluating each and every functionality of entire system, application or software is
functioning according to the expectations defined by the Requirement/specification document.<br />
The goal of software Testing is to:<br />
-Demonstrate the faults are not present<br />
-Finding Errors<br />
-Try to prove that software does not work.<br />
-Ensure that all the functionality has been implemented<br />
-Ensure the customer will be able to get his work done.<br />
Software testing must be applied systematically.<br />
Testing Involves<br />
-Operation of a system or application.<br />
-under controlled Conditions.<br />
-Evaluating the results.
</div>
</asp:Content>
<%@ Page Title="Software Development Life cycle" Language="C#"
MasterPageFile="~/[Link]" AutoEventWireup="true"
CodeBehind="[Link]"
Inherits="Desamma.Sotwaretesting_Manual.SoftwareTestingManual2" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">
<div class="childpage">
<meta name="description" content="Tutorial explains (STLC)Software Testing Life Cycle" />
<meta name="keywords" content="STLC,Software Testing Life Cycle,Analysis Phase,Design
Phase,Implementation Phase,Testing Phase,Deployment Phase,Production Phase,Testing" />
<meta name="classification" content="Tutorials,Software Testing Life Cycle,online articles" />
<h1>Software Development Life cycle</h1>
<h2>Analysis Phase:</h2>
In this phase ,based on the Customer Requirement Document Project Manager, Senior test Engineer,
Analysts refers all the requirement Documents and analyses and prepare High level requirement
Document and scope, resource and schedule will be decided.
<h2>Design Phase:</h2>
In this Phase based on the requirement, Team leads, Senior Software Engineer will prepare A technical
Documents which is called (HLD)high level Design,(LLD) Low level design documents these documents
is also called as Blue print of the project.
<h2>Implementation Phase:</h2>
In this phase based on these (HLD)high level Design,(LLD) Low level design documents actual
execution of the project starts. Development of source code happens by the developers.
<h2>Testing Phase: </h2>
In this phase testers starts testing those Source Code developed by the developed. They will execute
all the test cases which has been designed based on the requirement Documents. Once Tester found
defects in code. Code would be sent back to the developer to fix it up. Once code got fixed tester tests
the code again approves that code is valid.
<h2>Deployment Phase:</h2>
In this phase the source code need to be deployed depending on the test results. Here the customer
gets the product.
<h2>Production Phase:</h2>
In this phase the maintenance of product were provided for the customer. Based the request from the
customer any change request according to the that change request code would be done. And
regression test would be performed for the code changes.
</div>
</asp:Content>
<%@ Page Title="Software Testing Life Cycle" Language="C#" MasterPageFile="~/[Link]"
AutoEventWireup="true" CodeBehind="[Link]"
Inherits="Desamma.Softwaretesting_Manual.SoftwareTestingmanual3" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">
<div class="childpage">
<meta name="description" content="Tutorial explains (STLC)Software Testing Life Cycle" />
<meta name="keywords" content="STLC,Software Testing Life Cycle,Analysis Phase,Design
Phase,Implementation Phase,Testing Phase,Deployment Phase,Production Phase,Testing" />
<meta name="classification" content="Tutorials,Software Testing Life Cycle,online articles" />
<h1>Software Testing Life Cycle</h1>
<h2>Analysis: </h2>
In this Phase Senior Test engineers (LEADs)with prepare the test plan which consists of scope,
schedules, Test strategy, and resource allocation. Test Engineers has to analyze the requirement
documents and understand each and every functionality. To make sure that any single requirement left.
Finally they prepare high level test cases(Use cases) covering all the requirements.
<h2>Design:</h2>
In this phase Based on the high level test cases(Use Cases).Test Engineers starts creating the test
cases against the requirement document. This Test cases are detailed test cases which would be tested
once the system is ready for testing. All this test cases would be reviewed internally by exchanging it.
Then this test cases would be review by test leads. Again the same test cases would be reviewed by
Business people based on their feedback these test cases would be modified and keep it ready for
testing in Quality Center.
<h2>Execution:</h2>
In this Phase once the system is ready for testing, Test engineers starts executing all the test cases
which is in Quality Center designed in earlier phases. Once if they found issue or defect, they will raise
the ticket for the defect in Quality Center and assign it to respective developer. All the defects which
has been raised by Test Engineer will be tracked in Quality center once the defect got fixed by the
developer again tester will test it.
<h2>Report(Signoff):</h2>
Here In this Phase Senior Test engineers (Leads) based on the test cases designed and test need to be
executed will track it and generate a graphs in Quality center. The defect metrics also would be created
and every they will make it as document and would be sent it as report. Once the test cases execution
comes to 100%. And all the defects in quality center got fixed and closed. Then further step would be
signoff.
</div>
</asp:Content>
<%@ Page Title="Verification And Validation" Language="C#" MasterPageFile="~/[Link]"
AutoEventWireup="true" CodeBehind="[Link]"
Inherits="Desamma.Softwaretesting_Manual.SoftwareTestingmanual4" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">
<div class="childpage">
<meta name="description" content="Tutorial explains Verification & Validation" />
<meta name="keywords" content="Verification,Validation,Testing" />
<meta name="classification" content="Tutorials,Verification,Validation,online articles" />
<h1>Verification And Validation</h1>
<p>
<h2> Verification:</h2> Before and during Software development, reviewing or analyzing the
application or system that are we building the project right?<br />
Verification shows conformance with specification.<br />
Verification Is the Static Process where reviews, walkthrough happens <br />
<br />
For example : Review of High Level Test Cases and detailed Test cases with leads or business people.
<h2>Validation:</h2> After the majority of software development work has been done. To perform
system test that are we building the right product.
Validation shows that the program meets m meets the customer the customer’s needs.<br />
Validation Is the Dynamic Process where real Executions runs.<br />
<br />
For example : Execution of test cases.
</p>
</div>
</asp:Content>
<%@ Page Title="Black and White Box Testing Coverage or techniques" Language="C#"
MasterPageFile="~/[Link]" AutoEventWireup="true"
CodeBehind="[Link]"
Inherits="Desamma.Softwaretesting_Manual.SoftwareTestingmanual6" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">
<div class="childpage">
<meta name="description" content="Tutorial explains Black and White box Testing Coverages Or
Techniques" />
<meta name="keywords" content="Equivalence Partitioning,Boundary value Analysis,Blackbox
testing Coverages,White box testing Coverages,Method Coverage,Statement Coverage,Branch
Coverage,Condition Coverage" />
<meta name="classification" content="Tutorials,Black and White box Testing Coverages Or
Techniques,online Free articles" />
<h1>Black and White Box Testing Coverage or techniques</h1>
<h2>Black Box testing Coverages</h2>
<h3>Equivalence Partitioning</h3>
<p>Equivalence Partitioning is the process of taking all possible test data and placing them into
classes. One test value is picked from each class while testing.
</p>
<h3>Boundary value Analysis</h3>
<p>Boundary Value Analysis is a next part of equivalence partitioning for designing test cases
where test data are selected at the edges of the equivalence classes.
</p>
<p>To understand this better(EP)and (BVA) , let's consider that if we have application for
voting<br />
Here age of person is will divide it 3 different classes
Age group of negative values such as -2,-20,-
18 Invalid
data<br />
Age group of lesser then boundary values such as 0,10,15,17
Invalid data<br />
Age group of valid values such as 18,21,35,45.. Valid
data <br />
we divided all the possible test data into three Different classes such that we can pick each values from
each group while testing.<br />
whereas for Boundary value Analysis We will pick the values at boundaries such as<br />
17,18,19 ,<br />
Here 17 is invalid data and 18 and 19 are valid data…<br />
</p>
<h2>White Box Testing Coverage's</h2>
<h3>Method Coverage </h3>
Method coverage is a measure of the percentage of methods that have been executed by test cases.
<h3>Statement Coverage</h3>
Statement coverage is a measure of the percentage of statements that have been executed by test
cases.
<h3>Branch Coverage</h3>
Branch coverage is a measure of the percentage of the decision points (Boolean expressions)
of the program have been evaluated as both true and false in test cases.
<h3>Condition Coverage</h3>
Condition coverage is a measure of percentage of Boolean sub-expressions of the program that have
been evaluated as both true or false outcome [applies to compound predicate] in test cases.
</div>
</asp:Content>
<%@ Page Title="Defect Analysis in Software Testing" Language="C#"
MasterPageFile="~/[Link]" AutoEventWireup="true"
CodeBehind="[Link]"
Inherits="Desamma.Softwaretesting_Manual.SoftwareTestingmanual7" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">
<div class="childpage">
<meta name="description" content="Tutorial explains the Defect analysis and Defect Life Cycle
in Software Testing " />
<meta name="keywords" content="Defect Life Cycle,Defect Report,Defect Severity,Defect
ID,software testing" />
<meta name="classification" content="Tutorials,Defect Life cycle,Defect Analysis,online free
articles" />
<h1>Defect Analysis in Software Testing</h1>
<h2>Defect Life Cycle</h2>
Defect Life Cycle is the Cycle that covers all the stages of the defect. ones the tester raises the
defect until he closes it.<br />
--> Once tester found the defect he raises It and assign it to developer and owner of defect is
developer. status would be open state.<br />
-->The developer Fixes the issue and assign it back to Tester for validation and owner of defect is
Tester .status should be changed Fixed.<br />
-->Now the tester validates the code change.<br />
if the issue got resolved tester will close the Defect. Status should be changed to close.<br />
Else if the issue(Defect) persists tester again reopens it and assign it back to Developer and owner of
defect is developer. Status should be changed to Reopen.<br />
Now the developer checks it and fixes it and assign it back to tester for validation. Owner of the defect
is Tester. status should be changed to Fixed.<br />
Tester validates the code change and closes the Defect. Status of defect is Close.<br />
<h2>Defect Severity</h2>
Severity of the defect can be stated as degree of impact on the build or operation of application or
system.<br />
Defect Severity is Classified by its level <br />
Urgent: If the Defect has been raised by severity as Urgent then the defect should be fixed as soon as
possible. Because It has more dependents. <br />
High: If the defect has been raised by severity as High then the defect impact on the system is high<br
/>
Medium :If the defect has been raised by severity as Medium then the defect impact on the system is
Medium<br />
Low :If the defect has been raised by severity as Low then the defect impact on the system is
Low<br />
<h2>Defect Report</h2>
Defect Report It is report which generated for each and every defect with following values In Quality
Center of Quality Unit.<br />
<table style="width: 100%">
<tr>
<td style="width: 152px">Defect Fields</td>
<td>Description</td>
</tr>
<tr>
<td style="width: 152px">Defect ID</td>
<td>Unique ID that is generated for each and every Defects</td>
</tr>
<tr>
<td style="width: 152px">Product</td>
<td>Name of the Product.</td>
</tr>
<tr>
<td style="width: 152px">Project</td>
<td>Name of the Project.</td>
</tr>
<tr>
<td style="width: 152px">Description</td>
<td>Giving some description for defect to make understand the defect g for
developer.</td>
</tr>
<tr>
<td style="width: 152px">Steps to Reproduce</td>
<td>The followed steps to replicate the defect</td>
</tr>
<tr>
<td style="width: 152px">Actual Result</td>
<td>The result obtained when all the steps.</td>
</tr>
<tr>
<td style="width: 152px">Expected Result</td>
<td>Which it should result if the defect doesn't occur.</td>
</tr>
<tr>
<td style="width: 152px">Found in Project Phase</td>
<td>Which phase the Defect has been identified i.e. Analysis Phase or Design Phase Or
Testing Phase</td>
</tr>
<tr>
<td style="width: 152px">Submitter</td>
<td>Defect who is raising it…(Test Engineer)</td>
</tr>
<tr>
<td style="width: 152px">Owner</td>
<td>Defect to who need to be assigned (Developer at initial state)</td>
</tr>
<tr>
<td style="width: 152px">State</td>
<td>The status of the Defect whether it is in Open State or Fixed or Validated.</td>
</tr>
<tr>
<td style="width: 152px">Sub State</td>
<td>Once the Defect got fixed then this sub state should be</td>
</tr>
<tr>
<td style="width: 152px">Detected In Release.</td>
<td>On Which release the Defect has been Fixed</td>
</tr>
<tr>
<td style="width: 152px">Comments</td>
<td>Comment sections for developer or tester to give explanation on Issue(Defect)</td>
</tr>
<tr>
<td style="width: 152px">Submit Date</td>
<td>The date submitter submit the defect to the developer.</td>
</tr>
<tr>
<td style="width: 152px">Attachments</td>
<td>An Screenshots, Text files or PDF files…etc… for references</td>
</tr>
</table>
</div>
</asp:Content>
<%@ Page Title="Levels of software testing" Language="C#" MasterPageFile="~/[Link]"
AutoEventWireup="true" CodeBehind="[Link]"
Inherits="Desamma.Softwaretesting_Manual.SoftwareTestingmanual8" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">
<div class="childpage">
<meta name="description" content="Free Tutorial explains The Levels of Software Testing and
the Definitions of Unit Testing,Integration Testing,System Testing,Acceptance Testing. " />
<meta name="keywords" content="Level of Software Testing,Unit Testing,Integration Testing,System
Testing,Acceptance Testing,Definitions" />
<meta name="classification" content="Free Tutorials,Level of SoftWare Testing,online free
articles" />
<H1>
Levels of software testing</H1>
<h3>Unit Testing:</h3>
Unit Testing is level of Software Testing to test single module, build or unit
<h3>Integration Testing:</h3>
Integration Testing Definition : Integration testing is a systematic technic to uncover errors associated
with interfacing (build the program structure as per the design) modules or units
<h3>System Testing:</h3>
Testing the system in artificial conditions to ensure that it should perform as excepted and as required
<h3>Acceptance Testing: </h3>
Formal testing with respect to user needs, requirements, and business
processes conducted to determine whether or not a system satisfies the acceptance criteria
and to enable the user, customers or other authorized entity to determine whether or not to
accept the system.
</div>
</asp:Content>
<%@ Page Title="Unit Testin In Software Testing" Language="C#" MasterPageFile="~/[Link]"
AutoEventWireup="true" CodeBehind="[Link]"
Inherits="Desamma.Softwaretesting_Manual.SoftwareTestingmanual9" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">
<div class="childpage">
<h1>Unit Testing Definition.</h1>
Unit Testing is level of Software Testing to test single module, build or unit <br />
Unit Testing is white box Testing method performed by the Developers.
Unit Testing make more confidence of the developer.<br />
Whereas identify the bug in system it is easy in unit testing. Such unit 1 or unit 2 or unit 3<br />
There is no need of creating test cases for Unit testing for developer.<br />
<h4>For example</h4>
Unit Testing is performed for each and every module such as if we have functionality like login for web
application.
we will test by its code wise such as function that which compares values from text box to
database values.
Such a way each and every step is tested against the requirement.<br />
<meta name="description" content="Tutorial explains the Defect analysis and Defect Life Cycle in
Software Testing " />
<meta name="keywords" content="Defect Life Cycle,Defect Report,Defect Severity,Defect
ID,software testing" />
<meta name="classification" content="Tutorials,Defect Life cycle,Defect Analysis,online free
articles" />
</div>
</asp:Content>
<%@ Page Title="Integration Testing" Language="C#" MasterPageFile="~/[Link]"
AutoEventWireup="true" CodeBehind="[Link]"
Inherits="Desamma.Softwaretesting_Manual.SoftwareTestingmanual10" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">
<div class="childpage">
<meta name="description" content="Tutorial explains the integration testing level,what is
integration testing? why Integration testing?" />
<meta name="keywords" content="Integration testing,what is Integration Testing" />
<meta name="classification" content="Tutorials,Integration Testing,online articles" />
<h1>Integration Testing</h1>
<h3> What is integration testing?</h3>
Integration Testing Definition : Integration testing is a systematic technic to uncover errors associated
with interfacing (build the program structure as per the design) modules or units
<h3>Why to perform integration testing? </ <h3>Security Testing </h3>
h3>
Once the build, Module or unit is ready, we will perform unit test against that build same way if its two
or three builds we will perform unit test for each and every build or module separately but all this
builds assembled as single unit. The path in between all this builds has not been tested if the defect
arises in those path. Then the system has bugs. So in order to find those defects we will perform
integration testing.
<h3>When to perform integration testing?</h3>
Once two builds, module or units were joined or integrated as single unit then this integration testing
should be performed to the interface path of system.
<h3>For example </h3>
let us assume one web application which has 5 pages each and every page has been tested and
functioning fine. but links between page were not working then application will face an issue. To avoid
such issues Integration level of testing is done for an application.<br />
<div class="fb-like"
data-href="[Link]
data-layout="box_count" data-action="like" data-show-faces="true" data-share="true"></div>
</div>
</asp:Content>
<%@ Page Title="System Testing In Software Testing" Language="C#"
MasterPageFile="~/[Link]" AutoEventWireup="true"
CodeBehind="[Link]"
Inherits="Desamma.Softwaretesting_Manual.SoftwareTestingmanual11" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">
<div class="childpage">
<meta name="description" content="Tutorial explains the System testing level,what is System
testing? why System testing?" />
<meta name="keywords" content="System testing,what is System Testing" />
<meta name="classification" content="Free Tutorials,System Testing,online articles" />
<h1>System Testing In Software Testing</h1>
<article> System Testing: Testing the system in artificial conditions to ensure that it should
perform as excepted and as required. Once each and every module is ready unit test is performed.
Once all the units or modules are integrated then integration is performed for the interfaces and hubs.
<h3>When to perform System Test</h3>
But overall testing that we perform on the system against requirement is called as System testing.
System testing is performed once the system is ready for testing. i.e. after integration testing
Performed before doing Acceptance Testing.
<h3>Definition by ISTQB</h3>
system testing: The process of testing an integrated system to verify that it meets specified
requirements.
</article>
</div>
</asp:Content>
<%@ Page Title="Software Testing Documents Test Plan,Test Case,Test Script." Language="C#"
MasterPageFile="~/[Link]" AutoEventWireup="true"
CodeBehind="[Link]"
Inherits="Desamma.Softwaretesting_Manual.SoftwareTestingmanual20" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">
<div class="childpage">
<meta name="description" content="Tutorial explains different documents used in Software
testing like Test Plan,Test Case,Test script" />
<meta name="keywords" content="Software Testing Documents,Testplan,Test Case,Test script" />
<meta name="classification" content="Tutorials,software Testing Documnets,Test Plan,Test
Cases,TestScript,online Free articles" />
<h1>Software Testing Documents</h1>
<h3> Test Plan: </h3>
Test plan is a Document which contains Objectives, Scope and the approach for testing . This document
says how many people ,equipment dedicated or allocated to testing. Which tools to be used. Test entry
and exit criteria
It contains reporting ,Communication processes, Schedules and milestones.
<h3>Test Plan Types</h3>
Test Plan Types can classified master Test Plan or Testing level Test Plan
Master Test Plan: A test plan that typically addresses multiple test levels.
Testing Level Specific Test Plans: Plans for each level of testing.
Unit Level test Plan, Integration Test Plan and so on… different types of Test plans…
<h3>Test Case: </h3>
Test Case is test item that tester creates it against the requirement document to cover each and every
business scenarios. It consists of following fields.
<br />
<br />
<table style="width: 100%">
<tr>
<td style="width: 173px">Test Case ID </td>
<td>Unique ID created for each and every Test case.</td>
</tr>
<tr>
<td style="width: 173px">Date Of Creation</td>
<td>The Date of Test creation</td>
</tr>
<tr>
<td style="width: 173px">Test Name</td>
<td>Name for the Test case</td>
</tr>
<tr>
<td style="width: 173px">Test Description</td>
<td>Description for test case additional information.</td>
</tr>
<tr>
<td style="width: 173px">Step name</td>
<td><span style="mso-spacerun:yes"> </span>Test Case's Step
numbers</td>
</tr>
<tr>
<td style="width: 173px">Description</td>
<td>Description that explain what user has to do.</td>
</tr>
<tr>
<td style="width: 173px">Expected Results</td>
<td>How does system should respond as per the requirement document.</td>
</tr>
<tr>
<td style="width: 173px">Product</td>
<td>The name of the product.</td>
</tr>
<tr>
<td style="width: 173px">Test Data</td>
<td>The data that used for testing</td>
</tr>
<tr>
<td style="width: 173px">Comments</td>
<td><span style="mso-spacerun:yes"> A</span>dditional information that
communicated between developer and tester</td>
</tr>
<tr>
<td style="width: 173px">Designer</td>
<td>Test case creator name.</td>
</tr>
</table>
<br />
<h3>Test Script Definition,</h3>
<br /> Explanation,
Example:<br />
A Test Script is a set of instructions written using a scripting/programming language that is performed
on a system under test to verify that the system performs as expected. Test scripts are used in
automated testing.
<br />
Some scripting languages used in automated testing are:<br />
JavaScript<br />
Perl<br />
Python<br />
Ruby<br />
Unix Shell Script<br />
VBScript<br />
</div>
</asp:Content>
<%@ Page Title="Testing Tools for Automation" Language="C#" MasterPageFile="~/[Link]"
AutoEventWireup="true" CodeBehind="[Link]"
Inherits="Desamma.Softwaretesting_Manual.SoftwareTestingmanual21" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">
<div class="childpage">
<meta name="description" content="Tutorial explains Testing Tools for Automation,What Is
Manual Testing?,What is Automation Testing?,When to Automate?,What to automate?" />
<meta name="keywords" content="Testing Tools for Automation,What Is Manual Testing?,What is
Automation Testing?,When to Automate?,What to automate?" />
<meta name="classification" content="Tutorials,Types of software Testing,online articles" />
<h1>Testing Tools for Automation</h1>
<asp:PlaceHolder ID="PlaceHolder1" runat="server"></asp:PlaceHolder>
<h2>Difference between Manual and Automation Testing</h2>
<h3>What Is Manual Testing?</h3>
The Process of evaluating each and every functionality of entire system, application or software is
functioning according to the expectations defined by the Requirement/specification document.
<h3>What is Automation Testing?</h3>
The process of creating set of instruction as script for business critical scenarios though which more
number of users go through and making the script to run as manual user.
<h3>Why to Automate Testing?</h3>
Once we have new release or any new bug fixes we can automate our test cases.<br />
To minimize the manual effort while doing regression testing.<br />
To Avoid human errors while doing testing manually.<br />
<h3>When to Automate?</h3>
Once the system testing is Done. Then it is best to automate the application why because system
would be stable at that point.
Picking up business critical scenarios for Performance test. Picking functional flow of application to
create Regression Suites.<br />
<h3>What to automate?</h3>
Business Critical Scenarios for Performance Test.<br />
Functionalities which we frequently perform regression test.<br />
<br />
<h3>Mostly used tools In Market for Automation.</h3>
HP Quick Test Professional<br />
Selenium<br />
IBM Rational Functional Tester<br />
SilkTest<br />
Test Complete<br />
Testing Anywhere<br />
Win Runner<br />
HP LoadRunner<br />
J Meter<br />
Visual Studio Test Professional<br />
WATIR<br />
<div class="socialnetwork"> madhu</div>
</div>
</asp:Content>
<%@ Page Title="Types of Software testing" Language="C#" MasterPageFile="~/[Link]"
AutoEventWireup="true" CodeBehind="[Link]"
Inherits="Desamma.Softwaretesting_Manual.SoftwareTestingmanual13" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">
<div class="childpage">
<meta name="description" content="Tutorial explains Types of Software testing,ISTQB Definition
of Smoke Testing,Functional Testing,Usability Testing,Security Testing,Performance Testing,Regression
Testing" />
<meta name="keywords" content="Types of Software testing,Smoke Testing,Functional
Testing,Usability Testing,Security Testing,Performance Testing,Regression Testing" />
<meta name="classification" content="Tutorials,Types of software Testing,online articles" />
<h1>Types of Software Testing</h1>
<h3> Smoke Testing</h3>
smoke test: A subset of all defined/planned test cases that cover the main functionality of a component
or system, to ascertaining that the most crucial functions of a program work, but not bothering with
finer details. A daily build and smoke test is among industry best practices. See also intake test.
<h3>Functional Testing</h3>
functional testing: Testing based on an analysis of the specification of the functionality of a component
or system. See also black box testing.<br />
functionality: The capability of the software product to provide functions which meet stated and implied
needs when the software is used under specified conditions.
<br />
functionality testing: The process of testing to determine the functionality of a software product.
<h3>Usability Testing</h3>
usability testing: Testing to determine the extent to which the software product is
ATA understood, easy to learn, easy to operate and attractive to the users under specified
conditions. [After ISO 9126] <br />
use case: A sequence of transactions in a dialogue between an actor and a component or
system with a tangible result, where an actor can be a user or anything that can exchange
information with the system.
<h3>Security Testing </h3>
security testing: Testing to determine the security of the software product. See also functionality
testing.
<h3>Performance Testing:</h3>
performance testing: The process of testing to determine the performance of a software
ATT product. See also efficiency testing.<br />
performance testing tool: A tool to support performance testing that usually has two main
ATT facilities: load generation and test transaction measurement. Load generation can simulate
either multiple users or high volumes of input data. During execution, response time
measurements are taken from selected transactions and these are logged. Performance
testing tools normally provide reports based on test logs and graphs of load against
Response times.
<h3>Regression Testing</h3>
regression testing: Testing of a previously tested program following modification to ensure that defects
have not been introduced or
uncovered in unchanged areas of the software, as a result of the changes made. It is performed
when the software
or its environment is changed.
</div>
</asp:Content>