The document discusses the roles and differences between developers and testers in software development, emphasizing the importance of a proactive testing approach to ensure software quality and usability. It outlines the software testing life cycle, various testing methodologies, and provides insight into the bug life cycle, including identification, tracking, and resolution processes. Additionally, it lists common testing tools, both open-source and commercial, used for functional and performance testing.

1. ABC of Testing

2. Before Beginning
Developers Vs Testers - Common Mindset
–
–
Development is a highly skillful, tedious job
A developer is an expert who always will have more skill
set as compared to a tester
–
A Tester has to have developmental skill set to find the
errors in the application.
A Tester is a proactive person and needs to think ahead of
developer.
Reality
–

3. What is Software Testing
Testing is to –
 Ensure that the software product
works according to the Specifications.
 Identify the defects in the software
Product.
 Check if the Software is user friendly
and easy to operate.
 Suggest improvements in the existing
working product.


4. Need for Testing of the
Software product
A Software Application is a developed
product & not manufactured Product
 There is no standardised mechanical
process of development for an
application
 The Testing ensures the

◦ Precision of Application Functionality
◦ Requirements given are fulfilled

5. Ensuring Precision
Common Error-Prone Areas
 Athematic Calculations on data
 Data Validations
 Data Editing and processing
 Data Comparing and merging
 Data searches that gives incorrect or
incomplete output results
 Defining data relationship
 Coding errors
 Incorrect logic destabilizing existing
business process

6. SDLC And Software Testing
Initiation
Requirement
Analysis
Planning
Development
Testing
Defect
Tracking
Designing
Deployment
Maintenance

7. Software Testing Life Cycle

The Test Process is the formal
process designed for the Testing of
the software

The Test Team along with the
development team achieves the goal
of delivering a perfect software system

8. Test Process
Requirement Analysis
Test Execution
Defect Tracking
Report Bugs
Regression Testing
Test Panning
Bugs Fixed
Test Scenario/Use
Case Design
Integration Testing
Design of Test Cases
System Testing
Creation of Test Data
Setup Configuration
Performance Testing
QA Sign Off
QA of
Documentation

9. Functional Testing
 Usability Testing:
 Performance Testing:
 Unit Testing:
 Integration Testing:
 System Testing:
 User Acceptance Testing:
 User Interface Testing:
 Boundary value Analysis:

Database Testing:
 Compatibility Testing:
 Security Testing:
 Scalability Testing:
 Localization Testing:
 Configuration Testing:
 Deployment Testing:
 Documentation Testing:
 Non functional Testing:

Types of Testing

10. Types of Testing
Black Box Testing
White Box Testing
The Tester does not look into the Code of the Software
Program under Test
The Tester reads and understands the code under Test.
The expertise of Tester required is basic Testing skills
The Tester should understand basic Testing as well as
writing Test programs.
Testing is primarily based in entering input data into the Testing is based on actual writing a Test Program to
Software Program mostly through User Interface and
input data and read out put data through Application
observing the Output.
Programming interfaces or function pointers.
Automation is limited to automate entering data into and In addition to Automating the entering and reading
reading the output from the User Interface.
input data it includes automates testing code functions,
decision making algorithms and interfaces. Also checks
the Test Coverage of the Software Program
Usually Database Testing is not involved in this. Tester
might not be aware of the Database or other storage.
This involves Database Testing and the Tester needs to
understand the basic RDBMS

11. What is BUG?

Any flaw/fault in the software product
which is a Defect is called a Bug in
the Software terminology.

12. A BUG Life Cycle
A Bug is identified by the Tester.
The Tester enters it in the defect tracking System. Bug Status: NEW
The Test Lead reviews the Bug.
The Test Lead assigns it to the Developer. Bug Status: Assigned
The Developer corrects the code.
The Developer changes the status and assigns it to the Tester for
verification. Bug Status: Fixed
The Tester executes the related tests to find out if the issue is fixed in
the code.
The Tester changes the status and
assigns the Bug to the developer for
fixing the issue.
YES
Bug Status: Reopened
Defect is
Present?
NO
The Tester retest the feature ensures
that no defect exists and changes the
status of the Bug.
Bug Status: Verified
At the End of the SDLC the Tester marks for
all Bugs that are verified
Bug Status: Closed

13. Common tools for Testing

Open Source Tools
◦
Test Management tools
◦
TET (Test Environment Toolkit)
◦
TETware
◦
Test Manager
◦
RTH

Functional Testing Tools
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
Selenium
Soapui
Watir
HTTP::Recorder
WatiN
Canoo WebTest
Webcorder
Solex
Imprimatur
SAMIE
Swete
ITP
WET
WebInject

14. Load Testing Tools
Jmeter
FunkLoad
Proprietary/Commercial
tools
 Test Management tools

◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
HP Quality Center/ALM
QA Complete
T-Plan Professional
Automated Test Designer (ATD)
Testuff
SMARTS
QAS.TCS (Test Case Studio)
PractiTest
Test Manager Adaptors
SpiraTest
TestLog
ApTest Manager
DevTest

15. 
Functional Testing Tools
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
QuickTest Pro
Rational Robot
Sahi
SoapTest
Badboy
Test Complete
QA Wizard
Netvantage Functional Tester
PesterCat
AppsWatch
Squish
actiWATE
liSA
vTest
Internet Macros
Ranorex

Load Testing Tools
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
HP LoadRunner
LoadStorm
NeoLoad
Loadtracer
WebLOAD Professional
Forecast
ANTS – Advanced .NET Testing
System
vPerformer
Webserver Stress Tool
preVue-ASCII
Load Impact

16. Thank You