Software testing is the process of evaluation of a software item to detect differences between given input and expected output. Software Testing is the process of assuring that product which is manufactured by developer is meeting the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed. The purposes of testing are: Quality assurance, Verification and Validation, To find the bugs before the product is released to customer. To improve the quality of the product To evaluate that the product is according to requirements By, Mr. Surendra Rawat, QA Tester at www.gusani.com

1. www.Gusani.com
Prepared By: Surendra Rawat
SOFTWARE TESTING

2. Call Us :(UK) +44020 3289 2499
(USA) +1 (315) 642 4399
(India) +91 (079) 4019 1848
INTRODUCTION OF TESTING
 What is Testing: Software testing is the process of evaluation of a software item to detect
differences between given input and expected output.
 Software Testing is the process of assuring that product which is manufactured by developer
is meeting the user requirement. The motive to perform testing is to find the bugs and make
sure that they get fixed.
 The purposes of testing are:
 Quality assurance, Verification and Validation,
 To find the bugs before the product is released to customer.
 To improve the quality of the product
 To evaluate that the product is according to requirements

3. Call Us :(UK) +44020 3289 2499
(USA) +1 (315) 642 4399
(India) +91 (079) 4019 1848
WHO AND WHEN TO START TESTING
 Who does testing: Following professionals are involved in testing of a system
within their respective capacities:
 Software Tester
 Software Developer
 Project Lead/Manager
 End User
 When to Start Testing?
 Testing is done in different forms at every phase of SDLC like during Requirement
gathering phase, the analysis and verifications of requirements are also
considered testing.

4. Call Us :(UK) +44020 3289 2499
(USA) +1 (315) 642 4399
(India) +91 (079) 4019 1848
TYPE OF TESTING
 Manual testing: This type includes the testing of the Software manually i.e.
without using any automated tool or any script.
 A manual tester would typically perform the following steps for manual
testing:
 Understand the functionality of program
 Prepare a test environment.
 Execute test case(s) manually
 Verify the actual result
 Record the result as Pass or Fail
 Make a report of the Pass and Fail test cases
 Publish the report

5. Call Us :(UK) +44020 3289 2499
(USA) +1 (315) 642 4399
(India) +91 (079) 4019 1848
Pros - Cons
 Advantage:-
 Manual testing can be use in both small and big project.
 We can easily reduce and add our test case according to project movement.
 Easy to learn for new people who enters in manual testing.
 Manual testing is more reliable then automated (in many cases automated not cover all cases) .
 Disadvantage:-
 GUI object size difference and color combination etc is not easy to find out in manual testing.
 Actual load and performance is not possible to cover in manual testing for large number of users.

6. Call Us :(UK) +44020 3289 2499
(USA) +1 (315) 642 4399
(India) +91 (079) 4019 1848
Automation testing
 Automation testing: Automation testing which is also known as Test Automation.
In this testing, the tester writes scripts and uses another software to test the
software. There are many Tools are use in automation Testing.
 Software testing tools:
 HP Quick Test Professional
 Selenium
 Testing Anywhere
 WinRunner
 LaodRunner

7. Call Us :(UK) +44020 3289 2499
(USA) +1 (315) 642 4399
(India) +91 (079) 4019 1848
Pros - Cons
 Advantage
 Easy to cover up all cases in a limited time period.
 You can perform different types of testing’s like load testing, performance testing using
tool.
 Automated testing can be performed on different operating systems.
 Disadvantage
 Purchase a tools and Maintenance.
 Automation testing is more expensive work as comparing with manual testing.
 Language wise there are many tools to test various type of software, means all tools will
not support to all software which are developed in different languages.

8. Call Us :(UK) +44020 3289 2499
(USA) +1 (315) 642 4399
(India) +91 (079) 4019 1848
SDLC AND STLC
 Software Development Life Cycle:
There are six type of SDLC.
 Requirement phase
 Design phase
 Coding (programming)
 Testing
 Release (Production)
 Maintenance (Support)
 Software Testing Life Cycle: There
are seven type of STLC.
 Requirement Study
 Test Planning
 Writing Test Cases
 Review the Test Cases
 Executing the Test Cases
 Bug logging
 Close or Reopen bugs

9. Call Us :(UK) +44020 3289 2499
(USA) +1 (315) 642 4399
(India) +91 (079) 4019 1848
BASIC TYPE OF TESTING
 Black Box Testing: The technique of testing without having any knowledge of the interior
workings of the application is Black Box testing. The tester is oblivious to the system
architecture and does not have access to the source code. It is also called behavioral,
functional and close box testing.
 White Box Testing: White box testing is require understanding of internal logic and structure
of the code. White box testing is also called glassbox testing or open box, structural,clearbox
testing.
 Different types of software testing:
 Unit testing
 Shakeout testing
 Smoke testing(Ad-hoc testing)

10. Call Us :(UK) +44020 3289 2499
(USA) +1 (315) 642 4399
(India) +91 (079) 4019 1848
…continue
 Functional testing
 Integration testing
 Regression testing
 System testing
 Load testing
 Stress testing
 Performance testing
 User acceptance testing
 Black box testing
 White box testing
 Alpha testing
 Beta testing

11. Call Us :(UK) +44020 3289 2499
(USA) +1 (315) 642 4399
(India) +91 (079) 4019 1848
SAMPLE OF TEST CASE AND BUG LIFE CYCLE
Sample of Test case:
Bug Life Cycle: There are six phases of Bug Life cycle.
a. New
b. Assigned
c. Resolved
d. Verified
e. Closed
f. Reopen
Test Case
ID
Test Case
Description
Input
Data
Expected
Result
Test
Result
Remarks

12. Call Us :(UK) +44020 3289 2499
(USA) +1 (315) 642 4399
(India) +91 (079) 4019 1848
SAMPLE OF BUG CASE
Sample of Bug Case:
Bug Name: Application crash on clicking the SAVE button.
Bug ID: (It will be automatically created by the BUG Tracking tool once you save this bug)
Area Path: USERS menu > New Users
Severity: High (High/medium/Low)
Priority: High (High/medium/Low)
Assigned to: Developer-X
Reported By: Your Name
Reported On: Date
Reason : Defect
Environment: Windows 2003/SQL Server 2005

13. Call Us :(UK) +44020 3289 2499
(USA) +1 (315) 642 4399
(India) +91 (079) 4019 1848
…continue
 Severity: Describes the bug in terms of functionality.
 Priority: Describes the bug in terms of customer.
 Ex.
 High Priority and Low Severity: Company logo is not properly displayed on their website.
 High Priority and High Severity: Suppose you are doing online shopping and filled payment
information, but After submitting the form, you get a message like "Order has been cancelled."
 Low Priority and High Severity: If we have a typical scenario in which the application get crashed, but
that scenario exists rarely.
 Low Priority and Low Severity: There is a mistake like "You have registered success" instead of
successfully, success is written.

14. Call Us :(UK) +44020 3289 2499
(USA) +1 (315) 642 4399
(India) +91 (079) 4019 1848
WATER FALL MODEL
 Water Fall Model:
 History: The first formal description of the waterfall model is often cited as a 1970
article by Winston W. Royce
 Features:
 A Water Fall Model is easy to flow.
 It can be implemented for any size of project.
 Every stage has to be done separately at the right time so you cannot jump stages.
 Testing is done at every stage.

15. Call Us :(UK) +44020 3289 2499
(USA) +1 (315) 642 4399
(India) +91 (079) 4019 1848
Waterfall Model

16. Thank you…!
Call Us :(UK) +44020 3289 2499
(USA) +1 (315) 642 4399
(India) +91 (079) 4019 1848

17. Gusani
E-mail : sales@Gusani.com / Skype: Gusaniinfotech
Call (UK) : +44 020 3289 2499
Call (USA) : +1 (315) 642 4399
Call (India) : +91 (079) 4019 1848
www.Gusani.com
Let’s get started with your projects…!