MANUAL TESTING

What is Testing?
Testing is process of evaluating the project/product
Testing is act of checking if a product performs as expected
Test is kind of specific part of s/w eng. to check the robustness of s/w for various invalid
and valid inputs and checking of the output according to the requirement specification
and functional specification.
Testing: Verification and Validation of an Application.

What is Test Plan?

test plan is a road map for successful complete testing
Test Plan:
When to test?
What to test?
Who is going to test?
How is he going to test?
etc.
Write paper which plans in better quality the process of testing. Scope, People
needed, Approach, Criteria (pass/fail/suspension/resumption), Environment needs,
Deliverables test, Incidental, Risk (contingencies), Schedule (Time/Date),
Responsibilities, Short term Objectives (Objectives), Long term Objectives (Aim)

What is Test Case?

Test case is a action that validate the product success or failure
Test case contains
1) Test case ID
2) Test case Description/Purpose
3) Test case Procedure
4) Test Data
5) Expected Result
6) Actual Result
7) Test Log (Result)
8) Reason
9) If need Note

Differentiate Between Error, Defect, Bug, and Fault?

 Error: Occurred in programming side. Developers should identified and rectified the
errors (Logical error, Syntax error)
Defect: Occurred in testing side. Testers identify the mistakes/wrong in the
application. (Testing Term)
Bug: Developers also accepts testers defect, its called Bug (Testing Term)
Fault: Customer/Client are identified the mistakes in the application after delivering
the project/product.

What is Defect?
The name defect is testing term. Testers identify the mistakes in the application.
Expected Result != Actual Result

What is Quality?
User Friendly
Expected Result = Actual Result
Full fill the users requirement and satisfaction.

Differentiate between Project and Product based Testing?

product Testing is nothing but after preparing the
application we will contact to the clients. If client need
any changes then we will change it according to
requirements.
Example : Microsoft (Vista)
project based means client only give all the
customer requirements. According their requirements we will
test the application.
Example : TCS

Software Development Life Cycle (SDLC)

Its contain
Plan
Analysis
Design
Implementation
Operation and Support (Maintenance)

Software Testing Life Cycle (STLC)

Test plan preparation

Test case preparation
Test case execution
Test log
Defect tracking
Report writing

Test case Preparation

Actual Result are meet to customer expectation.

Contains
1)
2)
3)
4)
5)

Test case ID
Test case Description
Test case Procedure
Test case Data
Expected Result

Testcase Execution

Actual Result
What we actually got in the application.

Test Log

Pass or Fail
Expected Result = Actual Result ------- Pass
Expected Result 1= Actual Result ------ Fail

Testcase Sample:

testcas
e id

test case
procedure

test
case
desc

test steps

step

expecte
d

Defect Tracking

Contains
1) Test case ID
2) Defect ID
3) Defect Description
4) Defect Status
5) Priority
6) Severity

3) Defect Status (Bug Life Cycle)

Contains
A. Unconfirmed
B. New
C. Assigned
D. Open
E. In progress
F. Resolved
a) Fixed
b) Wont Fixed
c) Duplicate
d) Incomplete
e) Cannot Reproduce
G. Reopen
H. Closed

A. Unconfirmed

test
statu
s
(P/F)
actual

Notes
(if
need)

It means Testers identify a defect but not confirm whether its a defect or not (Like Look
and Feel)
B. New
Means testers confirm the defect in the application.
C. Assigned
Assign a person (Developer) to rectify the defect.
D. Open
The issue is open and ready for the assignee to start work on it.
E. In progress
This issue is being actively worked on at the moment by the assignee.
F. Resolved
Resolve the bug by developers (also testers side)
a) Fixed
Rectify the issues what the testers raise
b) Wont Fix
The problem described is an issue which will never be fixed.
c) Duplicate
The problem is a duplicate of an existing issue.
d) Incomplete
The problem is not completely described.
e) Cannot Reproduce
All attempts at reproducing this issue failed, or not enough information was available
to reproduce the issue. Reading the code produces no clues as to why this behavior
would occur. If more information appears later, please reopen the issue.
G. Reopened
This issue was once resolved, but the resolution was deemed incorrect. From here
issues are either marked assigned or resolved.
H. Closed
The issue is considered finished, the resolution is correct. Issues which are closed
can be reopened.

Manual Testing Life Cycle

Developer develop (Build) the application and send it to testers. Testers test the application, if
there is any defect occur they prepare a test report and send it to developers and the
developers are to open and rectify the defect, and resend it to tester.. This process continues up
to the product/project are defect free or quality.

Testing Phase
Task
Testing.
Roles

Test Engineer.

Process

First of all the Test Engineer will receive the requirement documents and review it for
under studying the requirements.

If at all they get any doubts while understanding the requirements they will prepare
the Review Report (RR) with all the list of doubts.

Once the clarifications are given and after understanding the requirements clearly
they will take the test case template and write the test cases.

Once the build is released they will execute the test cases.

After executions if at all find any defects then they will list out them in a defect profile
document.

Then they will send defect profile to the developers and wait for the next build.

Once the next build is released they will once again execute the test cases

If they find any defects they will follow the above procedure again and again till the
product is defect free.

Once they feel product is defect free they will stop the process.

Proof

The proof of this phase is Quality Product.

Test case
Test case is an idea of a Test Engineer based on the requirement to test a
particular feature.

TESTING METHODOLOGY (OR) TESTING TECHNIQUES

There are 3 methods are there

Black Box Testing.
White Box Testing.
Gray Box Testing
1) Black Box Testing
It is a method of testing in which one will perform testing only on the functional part of an
application without having any structural knowledge. Usually test engineers perform it.
2) White box Testing (Or) Glass box Testing (Or) Clear box Testing
It is a method of testing in which one will perform testing on the structural part of an
application. Usually developers are white box testers perform it.
3) Gray box Testing
It is a method of testing in which one will perform testing on both the functional part as
well as the structural part of an application.

LEVELS OF TESTING
There are 5 levels of testing.

1) Unit level testing

2) Module level testing
3) Integration level testing
4) System level testing
5) User acceptance level testing
1) Unit level testing
If one performs testing on a unit then that level of testing is known as unit level testing. It
is white box testing usually developers perform it.
Unit: - It is defined as a smallest part of an application.
2) Module level testing
If one perform testing on a module that is known as module level testing. It is black box
testing usually test engineers perform it.

3) Integration level testing

Once the modules are developing the developers will develop some interfaces and
integrate the module with the help of those interfaces while integration they will check
whether the interfaces are working fine or not. It is a white box testing and usually
developers or white box testers perform it.
4) System level testing

Once the application is deployed into the environment then if one performs testing on the
system it is known as system level testing it is a black box testing and usually done by
the test engineers.

5) User acceptance testing.

The same system testing done in the presents of the user is known as user acceptance
testing. It s a black box testing usually done by the Test engineers.

Testing Types
Ad hoc testing
Testing carried out using no recognised test case design technique.
Boundary value testing
A testing technique using input values at, just below, and just above, the defined limits of an
input domain; and with input values causing outputs to be at, just below, and just above, the
defined limits of an output domain.

Regression testing
Retesting of a previously tested program following modification to ensure that faults have not
been introduced or uncovered as a result of the changes made.
Stress testing
Testing in which a system is subjected to unrealistically harsh inputs or load with inadequate
resources with the intention of breaking it.