Manual Testing with Examples

1. Example For Quality
Enter Text
here:
abc
ok
Please enter valid
data

2. Enter Text
here:
abc123
OK
Please enter valid
data
Summary for above two Examples
The Application should be prepared according to client’s
requirements and it should be User-Friendliness.

3. Project taken by the Organization
in a procedural way...
BOA
Requirements
TCS
Infosys
IBM
Tech
Mahindra
DSS
RFP
Client

4. Contents of RFP
Full form of RFP : Request for Proposal Document
Contents :
1) Introduction
2) Cost
3) Experience
4) Resources
5) Approach
6) Methodologies ....etc

5. Selected
BOA DSS
The Official People of both the companies will meet to
finalize the agreement. For finalizing they will sign on
Documents.
SLA Service level Agreement
SOW Statement of work

6. SDLC Phases
1) Initial or Requirement phase
2) Analysis Phase
3) Design Phase
4) Coding Phase
5) Testing Phase
6) Release & Maintenance

7. Where exactly Testing will be started
1) UnConventional Testing
2) Conventional Testing
Unconventional Testing : The person will test the application whether
this application is going according to company standards are not. Here
the person is QA(Quality Analyst)
Conventional Testing : The person will test the application whether this
application is according to clients requirements or not. Here the person
is Software Test Engineer.

8. Testing Methodologies : There are two types of testing methodologies.
1) Black Box Testing
2) White Box Testing
There is one more which is derived from above two methodologies.
i.e Gray Box Testing.
Black Box Testing : The people who performs testing only on the
functional part of the application is called as Black Box test Engineers.

9. White Box Testing : The people who test the structural part of the
application i.e Coding part is known as White Box Testing.
> Usually developers are White Box Test Engineers.
Gray Box testing : The people who test the Functional and Structural
part of the application is known as Gray Box Testing.

10. Levels of Testing
Different Levels of Testing are :
1) Unit Level Testing
2) Module level Testing
3) Integration level Testing
4) System level Testing
5) User acceptance Testing
Unit Level Testing :
 Unit is defined as a Smallest part of the program in an
application.

11.  These will be performed by developers where they will test each
and every unit of an application(i.e coding) and combination of
units.
Different ways of unit testing are :
1) Structural Testing
2) Conditional Testing
3) Branch Testing

12. Module Level Testing :
 Combining more than one functionality to perform a major
task of related feature to test is known as Module Level
Testing
 These will be performed by Software Test Engineers.
City
GOA
HYD
Others
Select
Location here
: OK

13. Example 2
City
GOA
HYD
Others
Select
Location here
: OK
Enter Location name : PUNE
OK

14. Select
Location here
:
City
GOA
HYD
PUNE
Others
OK

15. 3) Integration Level Testing :
Combining all the modules of a project by using
different approaches. The approaches are :
1) Top-Down Approach
2) Bottom- Up Approach
3) Hybrid Approach
4) Big bang Integration
1) Top-Down Approach :
Combining the modules from top(i.e parent) level to
bottom(i.e Child) level is known as Top-down Approach.

16. A
B C
D E F G
From top to
Bottom
Parent
Module
Stub
Stub : In Top-Down approach if any original module is replaced
With dummy module that module we will call it as Stub.

17. Bottom-Up Approach : Combining the modules from child level to
parent level is known as Bottom-up approach.
A
B C
Parent
Module
D E F G
Driver
From Bottom
to Top
Child Module

18. Hybrid Approach : Combination of both the approaches is known as
Hybrid approach.
Big Bang Integration : Combining all the modules at a time after
Preparing the modules is known as Big bang Integration.
System Level Testing : Testing each and every functionality of the
application where we will perform all the types of testing is known
as system level testing.

19. Software Development Models
Water Fall Model or Linear Sequential Model
Initial
Analysis
Design
Coding
Testing
R & M
Phases
Cost
Cost of a bug phase
by phase

20. Initial
Analysis
Design
When ever Requirements are added
In the middle again the process
Should start from first.
Coding
Testing
R & M

21. ENVIRONMENT
Present
Layer
Validations Appropriate data
Database
Layer
Request Request
Applicati-on
Layer
Response Response
Displaying data
There are 4 types of architectures :
1) 1-Tier Architecture
2) 2-Tier Architecture
3) 3-Tier Architecture
4) n-Tier Architecture

22. Environment in the Organization for a project
Dev Environment Test Environment Production Environment
D1 D2
D3
T1 T2
T3
P1
Build 1 released
Build 1(Defects)

23. Dev Environment Test Environment Production Environment
D1 D2
D3
T1 T2
T3
P1
Build 1000 released
Build 1000 (No Bugs found)
Deploying Build
1000

24. Types of Testing
1) Build Verification Testing
or
Build Acceptance Testing
or
Sanity Testing
Conditions for accepting the Build :
1) Build Installation.
2) Navigating through pages.
3) Features Availability.
4) Required connections are properly established or not.
If all these conditions are satisfied then we will continue with
Normal testing.

25. Sanity Testing : After releasing the build the testing will be performed on
some major functionalities to accept the build is known as Sanity Testing.
Smoke Testing : Before releasing the build the developers will test the
application that is known as Smoke testing.
2) Regression Testing : It is a type of testing in which one will perform
testing on the already tested functionality again with there dependencies.
Usually we do it in two scenarios.
 Whenever we raise the defects to the development department, once the
next build is released we will test the defect functionality as well as the
related functionality again and again.
 Whenever some new features added (incorporated) to application, When
next build is released to the testing department then all the related
features of the new features will be tested once again.

26. Example for Regression Testing
Calculator
V1 1
V2 2
Res 3
ADD
SUB
MUL

27. V1 1
V2 2
Res 30
ADD
SUB
MUL
Clicking on SUB
V1 1
V2 2
Res 300
ADD
SUB
MUL
Clicking on MUL

28. Retesting :
Username : abc
Password : abc
OK Cancel
Username : abcd
Password : abcd
OK Cancel

29. Definition : Testing the application again and again with different
set of values is known as Retesting.
Alpha Testing : It is a type of user acceptance testing conducted in
the software company by our test engineers in front of client
to make him accept.
Example : Project or Product
Beta Testing : It is a type of testing conducted by the End users or
third party experts or clients before releasing to Client is known as
beta Testing.
Example : Product

30. Static Testing :
Usernane :
Passward :
Cancel
Login
Definition : Without performing any actions on the application while
testing is known as Static Testing

31. Dynamic Testing : Here we will perform some actions on the application
to test the functionality whether it is according to client requirement.
Example : Functionality Testing
Installation Testing :-It is a type of testing in which one will install the
application into the environment by following the guidelines provided in
the deployment document. In-order to come to a conclusion whether
those guidelines are perfectly suitable for installing the application or not.
Compatibility Testing:-
It is a type of testing in which one will install the application into the
number of environments prepared with different combinations in-order
to confirm whether the application is suitable with all those environments
or not. Usually the type of testing is compulsory for products rather than
projects.
EX:- Testing the application with different browsers(Netscape Navigator,
Mozilla Firefox, Internet explorer).