Professional Documents
Culture Documents
Project:
Project is some thing that is developed based on the particular customers
requirements and used by that customer only ( E.g.: Marriage laddu)
Product:
It is some thing that is developed based on the companies specification and used
by the multiple customers (e.g.: Thirupathi laddu)
Quality:
Latest definition for quality: - quality is defined as not only the justification of
requirements but also the presence of value (User friendliness)
Testing:
1
Page 2
Testing is processes, in which the defects are identified, isolated, subjected for
rectification & ensure that the product is defect free. In order to produce the quality
product in the end and hence customer satisfaction.
2. Analysis phase
3. Design phase
4. Coding Phase
5. Testing Phase
(a) Tasks: Interaction with the customer and gathering the requirements.
Once the requirement document has come to the company the engagement
manager will check whether the customer gives any extra requirements or confused
requirements. In case of extra requirements he deals the excess cost of the project. In case
of confused requirements he is the responsible for prototype demonstration and gathering
the clear requirements.
2
Page 3
Proof: The proof document of this phase is Requirements Document. This is called
with different names in different companies.
5. BD (Business Document)
Some companies may maintain the over all business flow information in one document
and the detailed functional requirement information in the other document
Templates: It is a pre defined format, which contains the predefined fields, and used
for preparing a document in an easy, comfort and perfect manner.
Prototype: -Defined as a roughly & Rapidly developed model which is used for
demonstrating to the client, In order to gather the clear requirements and to win the
confidence of a customer.
(a) Tasks:
1.Feasibilty Study
2.Tentative planning
3. Technology Selection
4. Requirement Analysis
(b) Roles: System Analyst, Project Manager, and Team Manager.
Process
2. Tentative Planning: In this section the resource planning and the time planning
(scheduling) is done temporarily.
3. Technology Selection: - The list of all the technologies that are required to
accomplish this project. Successfully will be analyzed and listed out in this
section.
4. Requirement Analysis: - The list of all the requirements that are required to
accomplish this project. Successfully will be analyzed and listed out here in this
section.
3
Page 4
SRC- System requirement specification
Roles: High-level designing is done by the chief Architect & Low level
designing is done by the Technical Lead
Process: The Chief architect will be drawing some diagrams using unified modeling
language in order to divide the whole project in to modules.
The Technical lead will also draw some diagrams in order to divide the modules
in to sub modules.
The technical lead will also develop the PSEUDO code in order to make
developers comfortable while de3veloping the actual code.
Process: Developers will develop the actual code by using the technical design
document as well as following the coding standards like Proper indentation, color
coding, proper commenting and etc..,
V. Testing Phase:
Process:
4
Page 5
1. First of all the test engineers will collect the requirements
document and try to understand all the requirements
2. While understanding it at all they get any doubts they will list
out all of them in a review report.
4. Once the clarifications are given and after understanding all the
requirements clearly, they will take the test case template and
writes the test cases.
5. Once the first build is released then they will execute the test
cases
6. If at all any defects are found. They will list out all of them in a
defect profile template then
8. Once the next build is released then they re-execute the test
cases.
9. If at all any defects are found they will update the profile
document and sent it to the development department and will
be waiting fro the next build to be released .
Test Case: (def) Test case is an idea of a test engineer based on the customer’s
requirements in order to test a particular feature or a function.
Delivery:
(a) Task: - Installing the application in the client’s environment
Maintenance:
After delivering the soft wate while using if at all any problem occurs
then that problem becomes a task, based on that problem corresponding rolws will be
appointed, the roles will defined the process and solve that problem.
Some clients may request for the continuous maintenance in such situations a
group of people from the software company will be continuously working on the clients
place and taking care of the soft ware.
************************^^^^^^^^^^^^^^^^^^^************************
1. Un-conventional testing
2. Conventional testing
(a) Black-Box Testing: If one performs testing only on the functional part of an
application with out having any structural knowledge then tat method of testing is
known as Black-Box testing, usually the test engineers perform it.
(c) Grey-Box Testing: If one performs testing on both the functional part as well
as the structural part of an application then that method of testing as known as
gray box testing using the test engineers who have structural knowledge will
perform gray- box testing.
Levels of Testing:
There are five levels of testing
The developers may follow one of the following approaches while integrating the
modules.
7
Page 8
1.Top-down approach
4.Bigbang approach
1.Top-down approach: - In this approach one will develop the parent modules first
and then integrate them with the related child modules
2.Bottom-up approach: - In this approach one will develop the child modules first and
integrate them to the parent modules
4.Big bang approach:-In this approach one will wait till all the modules are ready and
finally they will integrate all the modules at a time
STUB: - While integrating the modules in top down approach if at all any mandatory
module is missing then that module is replace with a temporary program known as STUB
a. Presentation layer
b. Business layer
a. Presentation Logic: The logic that is used for viewing application is known as
presentation logic
b. Business Logic: - The logic that is used for performing the operations on the
application is known as business logic.
c. Data Base Logic: - The logic that is used for sharing and retrieving the data is
known as database logic.
One-Tier Architecture
PL
PL+BL DBL
9
Page 10
PL+BL
PL+BL
Clients Server
c. Web environment: - In his type of environment three tiers will be there. One is for
client’s the middle one is for application server and the other one is for database
servers. Presentation layer will be present at clients, Business layer will be present in
the application server, and database layer will be present at the database servers.
This type of environment is suitable for the applications that are used all over the
world by limited number users
Three-tier Architecture:
PL
DBL
BL
PL
DBL
PL
Web server: -
It is software, which provides web services to the clients.
E.g.: - Internet Information service (IIS).
Example for Application servers: Tom pact, Web logic, web sphere etc..,
d. Distributed environment: -
It is similar to the web environment but the number of application servers
are increased and represented in individual tiers in order to distribute the
business logic so that the logic will be distributed.
N-tier Architecture:
W
PL DBL
BL BL BL
10
Page 11
PL
PL
PL
******************^^^^^^^^^^^^^^^^^^^^^^^********************************
Advantages:
It is a simple model
Project monitoring & maintenance is very easy
Drawbacks:
Con not accept the new requirements in the middle of the project
H/Wprototype H/Wprototype
Prototype
S/WPrototepe H/Wprototype
REQ.are
Advantages: - BRS DOC
Refined
Base
Whenever the customer is not clearLined
with the requirements this is the best
suitable model for gathering the clear requirements.
Drawbacks: -
It is not a complete model
Prototype has to be built on companies cost
User may limit his requirements by sticking to the prototype.
Initial Req
User accept
Application validation 12 is Base lined
Appl
Y
Page 13
Advantages: -
Whenever the customer is evolving the requirements this is the best
Suitable model.
Drawbacks: -
Cannot define the dead lines
Project monitoring & maintenance is very difficult
No Transparency (No clear)
Spiral Model: -
Defining the objectives/WA/Constraints
Implementation
Advantages: -
This is the best suitable for developing the highly risk based project
(scientific projects)
Drawbacks: -
Risk analysis and estimation is not an easy task
It is a costly model
It is a time consuming model
Advantages: -
This is the best suitable for developing the highly risk based project(scientific projects)
Drawbacks: -
o Time consuming Model
o Costly model
Verification: -
It is a process of checking conducted on each and every role of the organization in order to check
whether they are working according to the guidelines or not right from the starting of the process
till the ending of the process
Validation: -
It is a process of checking conducted on the developed product in order to check whether it is
working according to the requirements or not.
(D) V-Model: -
Verification
Validation
BRS Preparing proj plan
Initial& design SRS Preparing Test plan
Phase Req.Phase testing
Port Testing
S/W efficiency
DRE=A/A+B
14
Page 15
Delivery & Maintenance Test S/W changer
Advantages; -
AS verification and validation as well as test management process is done the out come
will be a quality product.
Drawbacks: -
o Time consuming mode
o Costly model
2.Regression Testing: -
15
Page 16
It is a type of testing in which one will perform testing on the already tested
functionalities again and again.
It is usually done in two scenarios.
1. Whenever the testers has raised the defects, rectified by the developers and next build
is released to the testing department then the test engineer’s will test the defect
functionality as well as the related functionality once again.
2. When ever some new features are incorporated by the developers, next build is
released to the testing department then the test engineers will once again test the
related functionalities of the new features in order to confirm that they are working
same as previous.
Note: - Testing the new functionalities for the first time is known as new testing but not
Regression Testing.
3.Re-Testing: -
It is a type of testing in which one will test the same functionality again and again with
different sets of values in order to come to a conclusion whether it is working or not.
Advantage: - If at all any defects are found then there is a chance of rectifying them
immediately.
5. -Testing (Beta): -
It is a type of user acceptance testing done in the clients place either by the end-users or
by the third party testing experts before actual implementation.
Drawback: If at all any defects are found then there is no chance of rectifying them immediately.
6. Static Testing: -
It is a type of testing in which one will perform testing on the application or application
related factors with out performing any action.
Eg:- Documentary testing, GUI testing, Code reviews and etc.,
7. Dynamic Testing: -
It is a type of testing in which one will perform in the application or its related factors by
doing some actions
Eg: - Functionality testing.
16
Page 17
8.Installation Testing: -
It is a type of testing in which one will install the application in to the environment by
following the guide lines provided in the installation document and if the installation is
successful then he will come a conclusion that the given guide lines are correct other wise he will
come to a conclusion that the given guidelines are not correct.
9.Compatibility Testing: -
It is a type of testing in which one may have to deploy the application in to the multiple
number of environments prepared with different combinations of environmental components in
order to check whether the application is compatible with all that environments. This type of
testing is usually done to products.
11.Usability Testing: -
It is a type of testing in which one will check whether the application is user friendly or
not and it can be comfortably used by the end user or not.
14.Port Testing:-
It is a type of testing in which one will deploy the application in to the clients
environment and check whether it is compatible with that environment or not.
15.Reliability Testing: -
It is a type of testing I which one will perform testing on the application continuously for
long period of time in order to check the stability of the application
16.Security Testing: -
Its is a type of testing in which one will concentrate on the following areas of the
application
a. Authentication Testing
b. Direct URL Testing (Uniform Resource Location)
c. Fire Wall Leakage Testing.
17
Page 18
It is a type of testing in which one will enter different combinations of usernames and
passwords and try to access the home page in order to check whether only the authorized persons
are accessing the application or not.
It is a type of testing in which one will enter the URL of an unauthorized page directly in
the browser and try to access that page in order to check whether it is been accessed or not.
It is a type of testing in which one will enter as one level of user and try to access the
other level of unauthorized pages in order to check whether the firewalls are working properly or
not.
They are…
Test Planning
Test Development
Test Execution
Result Analysis
18
Page 19
Bug Tracking
Reporting
Plan: -
It is a strategic document, which describes how to perform a task in an effective, efficient
and optimized way.
Test Plan: -
It is a strategic document, which describes how to perform testing on an application in an
effective, efficient and optimized way.
Optimization: -
Optimization is a process of utilizing the available input resources to their max and
getting maximum possible out put.
1.0 Introduction
1.1 Objective
1.2 Reference Document
19
Page 20
3.4 Configuration management
3.5 Test metrics
3.6 Terminology
3.7 Automation Plan
3.8 List of automated tools
8.0 Scheduling
11.0 Assumptions
1.0 Introduction: -
1.1 Objective: -
The Purpose of the document is clearly described here in this section
20
Page 21
The list of all the features that are to be tested in this phase will be clearly
mentioned here in this section.
Test strategy is defined as an organizational level term, which is used for testing
all the projects in the organization.
Test Plan: -
It is defined as a project level term, which is used for testing a particular project in
the organization.
Note: - Test strategy is common for all the projects but the test plan is
specific for a particular project
3.6 Terminology: -
21
Page 22
The list of all the terms and the meaning that are used in that company will be
listed out here in this section
The list of all the documents that are to be prepared during the testing phase will
be listed out here in this section.
Eg: Test case, defects profile document.
8.0 Scheduling: -
The starting dates and the ending data of the each and every tasks is clearly
planned here in this section.
The list of all the potential risks and the corresponding solution plans will be
listed out here in this section.
Example:
Risks:
i. Unable to deliver the soft ware with in dead lines.
ii. Employees may leave the organization in the middle of the project
iii. Customer may impose the dead lines.
iv. Unable to test all the features with in the time.
v. Lack of expertisation
11.0 Assumptions: -
The list of all the assumptions that are to be assumed by the test engineer will be
listed out here in this section.
LLI (Low-level
Information) USE CASES
Screen Shots
Use Cases:
23
Page 24
Use case is a description of functionality of certain features of an application in
terms of actors, actions& responses
i. Screen shot
ii. Functional requirements
iii. Special requirement/Business rules/Validation
iv. Template
i. Screen Shot: -
User name
Password
Connect to
a. Initially whenever the login screen is Invoked Login, clear buttons must be
disabled.
b. Cancels Button must be always enable.
c. Up on entering user name and password the login button must be enabled.
d. Up on entering some information in to any of the fields the clear button must
be enabled
e. The Tabbing order must be user name, Password, Connect to, Login, clear,
cancel.
iv. Use Case Template:
Name Of The Use Case :
Brief Description of Use Case :
Actor’s Involved :
24
Page 25
Special Requirements :
Pre Condition :
Post-Conditions :
Flow of Events :
1.Explicit Requirements: -
The Requirements that are directly given by the customer are known as
explicit requirement.
2.Implicit Requirement: -
The requirements that are analyzed by the business analyst feeling that
they will add the value (user friendliness) to the application are known as implicit
requirements.
Initially whenever the login screen is Invoked Login, clear buttons must be
disabled.
Cancels Button must be always enable.
Up on entering user name and password the login button must be enabled.
Up on entering some information in to any of the fields the clear button
must be enabled
The Tabbing order must be user name, Password, Connect to, Login, clear,
cancel.
Initially whenever the login screen is invoked the cursor must be available in the
user name field
Upon entering in valid username, valid password and clicking on log in button an
error message should be displayed “Invalid username Please try again”
25
Page 26
Upon entering valid username, In valid password and clicking on login button an
error message should be displayed “Invalid Password Please Try again”
Upon entering Invalid username, Invalid password and clicking on login button
an error message should be displayed “Invalid user name and password Please try
again”
Post-Conditions: Either home page or admin page for the valid user and error
message for the invalid users
1. Main Flow
2.Alternative Flow
3.Exceptional Flow
1.Main Flow:
Action Response
1.Actor invokes the application. 1.Login Screen is displayed with the following fields
Username, Password, Connect to, Login, Clear& cancel.
Action Response
Actor Clicks on the cancel button. Login screen is close
27
Page 28
Identify the functionality of the use case with respect to the total functionality
Authentication
Identify the functional points and prepare the functional point document.
Functional Point: -
The point where an user can perform some action is known as functional
point.
Testing Process: -
FRS FPD MTCD DTCD DPD
28
Page 29
8 22 5 5
47
1 1
2 1
3 1
4 2
5 2
6 2
7 2
8 2
DID TCID
1 28
2 32
3 65
4 96
5 48
6 52
There are Two types of test cases if we see broadly they are:
1. GUI Test Cases
2. Functional Test Cases
29
Page 30
(a) Positive Test Cases,
(b) Negative Test Cases.
(a)Test Objective: -
The main purpose of the document is described here in this section
(b) Test Scenarios: -
The list of all the scenarios that are to be tested will be listed out here in
this section.
(c)Test Procedure: -
DEF: It is a functional level term, which describes how to perform testing
on the functionalities of the application.
30
Page 31
The plan for testing the functionalities is briefly described here in
this section
(e)Test Cases: -
TC
ID TYPE Description Expected Value Actual Value Result Severity Priority Reference
Check for the availability of All the objects must be All the objects
all the objects as per the available as per the are available as
Login Obj Tab login obj tab per the login obj
1 GUI tab Pass
All the objects must be
consistent with each All the objects
Check for the constancy of other are consistent
2 GUI all the objects with each other Pass
Check for the spellings of
all the objects as per the All the objects must be All the objects
spelled properly as per
Login obj TabLogin Obj are spelled
the login obj tab
3 GUI Tab.xls properly Pass
Initially login, clear must
Check for the enable be disabled and cancel Login, clear and
property of login, clear and button must be enabled cancel buttons
4 GUI cancel buttons are enabled Fail
31
Page 32
Initially the cursor must
be positioned in the Initially the cursor
Check for the initial user name field is present in the
5 GUI position of the cursor username field Pass
Enter some information in
to user name and
Login button must be
password field and check
enabled
for the enabled property of Login button is
6 Positive login button enabled Pass
Enter some info in to any
of the fields and check for Clear button must be
the enabled property of enabled Clear button is
7 Positive clear button enabled Pass
Corresponding page Corresponding
Enter user name, must be displayed as pages are
Password as per the VIT per the VIT displayed as per
8 Positive and click on login button valid in puts table Pass
Corresponding
Corresponding page
pages are
must be displayed as
Enter username, displayed as per
per the VIT With the
Password as per the VIT the VIT with the
mentioned data base
and select a data base mentioned data
connection
9 Positive option and click on login base connection Pass
All the fields are
All the fields must be
cleared but the
cleared and the Cursor
Enter some information in cursor is not
should be placed in the
to any of the fields and placed in the
user name fields
10 Positive clear button user name field. Fail
32
Page 33
1 User name Text Box
4 Login Button
5 Clear Button
6 Cancel Button
1 Suresh1 qtp Invalid User name Plz try again Admin Fail
Invalid User name Plz try
2 Raja2 rani Invalid User name Plz try again again Pass
Invalid password Plz try
3 Chiru DADA Invalid password Plz try again again Pass
Invalid password Plz try
4 Praveen TOPI Invalid password Plz try again again Pass
Invalid user name & Invalid user name &
5 NTR1 illu4 password Plz try again password Plz try again Pass
Invalid user name & Invalid user name &
6 Admin5 Admin6 password Plz try again password Plz try again Pass
33
Page 34
In this phase the test engineer will compare the expected values with the actual values
and if both are matched they will document the result as pass other wise they will
document the result as fail.
Bug Tracking is a process in which the defects are identified, Isolated and managed
Defect –ID: -
Defect Description: -
What exactly the defect is clearly described here in this section.
Submitter: -
The name of the test engineer who has submitted the defect will be mentioned here in this
section.
Date Submission: -
The date on which the defect is submitted is mentioned here in this section.
Version No: -
Corresponding Version number is mentioned here in this section.
34
Page 35
Build No: -
Corresponding build number is mentioned here in this section.
Assigned To: -
The development lead will fill the developers name for whom the defect is assigned.
1.Enter some
information in to any
Upon Clicking on of the fields
clear button all the 2.Click on clear
fields are cleared button
but the cursor is not 3.Observe that the
placed in the user cursor is not placed
name field in the username
fields after clearing
all the fields
2 Sri Balaji 11-Feb-08 1.0.0 1
1.Enter Suresh1 in
to the user name
Upon entering
field 2.Enter
Suresh1 as
qtp in to the
username and qtp
password field
as password and
3.Click on login
clicking on login
button
button admin page
4.Observe admin
is displayed instead
page is displayed
of error message
instead of error
message.
3 Sri Balaji 11-Feb-08 1.0.0 1
35
Page 36
1.Enter some
information in to
Up on entering the username field
information only in 2.Check for the
to the user name enabled property of
field login button is login button.
enabled instead of 3.Observe that login
being disabled button is enabled
instead of being
disabled.
4 Sri Balaji 14-Feb-08 1.0.0 1
1.Enter some
information in tho
Upon entering the password field
information only in 2.Check for the
to the password enabled property of
field login button is login button
enabled instead 3.Observe that login
being disabled button to enable
instead of being
disabled
5 Sri Balaji 11-Feb-08 1.0.0 1
Defect- Id: -
The list of defect numbers are mentioned here in this section
Defect Description: -
What exactly the defect is clearly described here in this section
Submitter: -
The name of the test engineer who has submitted the defect will be
mentioned here in this section.
Date Of Submission: -
The date on which the defect is submitted is mentioned here in this section.
Version No: -
Corresponding Version number is mentioned here in this section.
Build No: -
Corresponding build number is mentioned here in this section.
Assigned To: -
The development lead will fill the developers name for whomthe defect is
assigned.
36
Page 37
Severity: -
How serious the defect is defined in terms of severity, Severity is classified
in to four types:
1.Fatal (Sev1) or S1 or 1
2.Major (Sev2) or S2 or 2
3.Minor (Sev3) or S3 or 3
4.Suggestion (Sev4) or S4 or 4
1.Fatal:
If at all the problems are related to the navigational blocks or unavailability of
functionality then such type of defects are treated to be fatal defect.
Val1
Main Menu Val2
Result UN
AVAILABL
ADD E
Next
Next Next
2.Major: -
If at all the problems are related to the working of major functionalities then
such types of defects are treated to be major defects.
Val1 10
Val2 20
Result -10
ADD
3.Minor: -
If at all the problems are related to the Look & Feel of the application then
such type of defects are treated to be minor defects
Val1
Val2
Result
37
BAD
Page 38
4.Suggestions: -
If at all the problems are related to the value of the application then such type
defects are treated to be suggestions.
Some Invalid
+Ve integer Box alphabets Entry
Plz Try
again
Priority: -
Priority defines the sequence in which the sequence in which defects has to be
rectified. It is classified in to four types
1.Critical (Pri1) or P1 or 1
2.High (Pri2) or P2 or 2
3.Medium (Pri3) or P3 or 3
4.Low (Pri4) or P4 or 4
Usually the Fatal defects are given critical priority, Major defects are
given High priority, Minor defects are given Medium Priority and suggestions are given
Low Priority, But depending up on the situations the priority will be changing.
I - Case:
Low severity-High Priority Case: -
Up on customer visit to the company all the look and feel defects are given
highest priority.
II - Case:
High severity –Low Priority Case: -
When ever 80% of the application is released to testing department as 20%
is missing the test engineers will treat them as Fatal defect but the development lead will
give least priority for those defects as features are under development.
38
Page 39
Testers
REQ error
As per
No design
Is it OP
DEV Rectific
Reall EN
ation
y
Defe
ct
M1
Build #1 Fixed for
verification
Is
defect
is Build #2
RE
TESTING
really
If
ope verifie
Defect
Clos
STOP TESTING
Nen ed 39
d
Page 40
Yes
No
Yes
No
Status: -
New: - When ever the defect is found for the first time the test engineer will set the status
as New.
Open: -When ever the developer accepts the raised defect then he will set the status as
open.
Fixed for verification Or Fixed for rectified: - When ever the developer rectifies the
raised defect then he will change the status to fixed.
Re open and Closed: -When ever the defects are rectified, next build is released to the
testing dept then the test engineers will check whether the defects are rectified properly or
not. If the defect is rectified properly then the test engineer will set the status as “Closed”.
If the defect is not rectified properly then the test engineer will set the status as “Re
open”.
Hold: - When ever the developer is confused to accept or reject the defect then he will
set the status of the defect as hold.
40
Page 41
Testers Error or Testers Mistake Or Rejected: - When ever the developer is confirmed it is
not at all a defect hen he will set the status of the defect as “ Rejected”.
As Per Design: - When ever the test engineer is not aware of new requirements and if he
raises defects related to the new features then the developer will set the status “ As Per
Design”.
Note: This is a rare case not usually Occurs
41