Why Did You Choose This Course?: Project

Page 1
Why did you choose this Course?
1.
2.
3.
4.
Scope of getting job is very high.

No need to depend up on any technologies.
Testing remains forever
I want to be consistent through out my life
Why
explicitly the s/w companies are

recruited the test engineers?
1. One person cannot efficiently perform two tasks at a time
2. Sentimental attachment.
Who
can do the course?
Any graduate can do this course at this point of time
What exactly we require to get a job?

1.
2.
3.
4.
Stuf
Communication skills
Confidence
Dynamism
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:
Classical definition for quality: - Quality is defined as justification of all the

requirements of customer in a product.
NOTE: Quality is not defined in the product; it is defined in the customers mind
Defect: - Defect is defined as deviation from the requirements

Latest definition for quality: - quality is defined as not only the justification of
requirements but also the presence of value (User friendliness)
Testing:
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.
bandaru7778@gmail.com
Page 2
Software Development Life Cycle (SDLC):SDLC contains six phases they are
1. Initial phase or requirements phase.
2. Analysis phase
3. Design phase
4. Coding Phase
5. Testing Phase
6. Delivery & Maintenance Phase.
I. Initial Phase or Requirements Phase :

(a) Tasks: Interaction with the customer and gathering the requirements.
(b) Roles: Business Analyst (B.A), Engagement Manager (E.M)
Process: First of all the business analyst will take an appointment from the
customer, collects the templates from the company, meets the customer on appointed
day, gathers the requirements with the help of template and comes back to the
company with the requirements documents.
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.
Proof: The proof document of this phase is Requirements Document. This is

called with different names in different companies.
1. FRS (Functional Requirements Specification)
2. CRS (Customer Requirement Specification)
3. URS (User Requirement Specification)
4. BDD (Business Design Document)
5. BD (Business Document)
6. BRS (Business Requirement Specification)
Some companies may maintain the over all business flow information in one
document and the detailed functional requirement information in the other
document
Page 3
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.
II.
Analysis Phase:
(a) Tasks:
1.Feasibilty Study
2.Tentative planning
3. Technology Selection
(b) Roles:
4. Requirement Analysis
System Analyst, Project Manager, and Team Manager.
Process
1. Feasibility Study: - It is detailed study of the requirements in order to
check weather the requirements are possible or not.
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.
SRC- System requirement specification
Proof: - The proof of this phase is system Requirement specification.

III. Design Phase: Tasks:
1. High level designing
2. Low level designing
Roles: High-level designing is done by the chief Architect & Low level
designing is done by the Technical Lead
Page 4
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.
Proof: The proof document of this phase is Technical design document.

IV. Coding phase:
(a) Task: Developing or Programming
(b) Roles: Developers or Programmers
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..,
Proof: The proof document of this phase is source code Document.

E.g.: The programmer will develop some programs every one will develop his
program in different colors but the soft ware companies will ask the developers to
develop the program according to the company standards using proper color,
coding, commenting. So as to understand it easily.
V.
Testing Phase:
(a) Task: Testing
(b) Roles: Test engineers
Process:
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.
3. They will send the review report to the author of the
requirements document for clarifications.
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
Page 5
6. If at all any defects are found. They will list out all of them
in a defect profile template then
7. They will sent the defect profile document to the
development department and then will be waiting for the
next build to be released.
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 .
10. This process continuous till the product is defect free.
Proof: The proof of the testing phase is Quality Product.
Test Case: (def) Test case is an idea of a test engineer based on the customers
requirements in order to test a particular feature or a function.
VI. Delivery & Maintenance Phase:
Delivery:
(a) Task: - Installing the application in the clients environment
(b) Rolls: -Deployment engineer or Senior test engineers.
Process: - The senior test engineer or deployment engineer will be going to the
clients place and install the application in their environment with the help of the
guidelines provide in the deployment document.
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.
Page 6
************************^^^^^^^^^^^^^^^^^^^************************
Where exactly the testing comes in to picture?
Which sort of testing you are expecting?
How many sorts of testing are there?
There are two sorts of testing.
1. Un-conventional testing
2. Conventional testing
1.Un-conventional Testing: -Unconventional testing is a sort of testing done by
the quality assurance people, in which they test each and every out come document
right from initial phase of the SDLC (Soft ware development life cycle)
2.Conventional Testing: It is sort of testing done by the test engineers on the
application in the testing phase of SDLC.
Testing
Methodology or Testing techniques:
There are three methods of testing

(a) Black-Box Testing
(b) White-Box Testing
(a) Grey-Box 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.
(b) White-Box Testing: If one performs testing on the structural part of an
application then that method of testing is known as white box testing, usually
the developers or white box testers 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.
Page 7
Levels of Testing:
There are five levels of testing
1. Unit Level Testing
2. Module Level Testing
3. Integration Level Testing
4. System Level Testing
5. User Acceptance Testing (U.A.B)
1.Unit Level Testing: It is a level of testing in which one will perform testing on the units. It is a
white box testing and usually developers or white box testers will perform.
2.Module Level Testing: Module: Module is defined as a group of related functionalities to perform a major
task
It is a level of tasting in which one will perform testing on the modules. It is a black
box testing and usually test engineers perform it.
3.Integration Level Testing: It is a level of testing in which the developers will develop some interfaces to
integrate the modules and test whether the interfaces are working fine or not. It is a
white box testing usually developers or white box tasters perform.
The developers may follow one of the following approaches while integrating
the modules.
1.Top-down approach
2.Bottom up approach
3.Hybrid or Sandwich 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
Page 8
3.Hybrid approach Or Sandwich approach:- This is a mixed approach of
both the top down and bottom up approaches
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
DRIVER: -While integrating the modules in bottom up approach. If at all any

mandatory module is missing then that module is replaced with a temporary
program known as DRIVER
4.System Level Testing:

It is a level of testing in which one will install the complete application in to
the environment and then perform testing on it. At this level different types of
testing will be done one among those is system integration testing.
5.System integration Testing: It is a type of testing in which once the complete application is developed one
will perform an action at one module and checks for the reflections at the
corresponding modules. It is a black box testing and usually test engineers
perform.
6.User- Acceptance Testing: It is the level of testing in which one will perform the same system testing in
the presence of the user in order to make him accept the application. It is a black
box testing and usually Test engineer performs it.
Environment: - Environment is a combination of three layers (e.g.: Yahoo)
a. Presentation layer
b. Business layer
c. Data base Layer
Page 9
Software Development Models: 1.Water Falling Model

PHAS
INITIAL
ACTIVIT
OUTCO
Req.gathering
BRS
ANALYSIS
Sys.design
SRS
DESIGN
S/w design
TDD, GUI
UTR
CODING
TESTING
DEL&MAINT
Implementation
Black box testing
Unit test
Int. test
UTR
Mod Test
Sys.Test.
UAT
UTR
UTR
UTR
Delivery to
client
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
(b) Prototype Model: Unclear Req
Prototype
SRS Doc
Base lined
Client environment
confirmation
H/Wprototype
H/Wprototype
S/WPrototepe
H/Wprototype
REQ.are
BRS DOC
Refined
Baseclear
Lined
Whenever the customer is not
with the requirements this is the best
Advantages: -
suitable model for gathering the clear requirements.

Page 10
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.
(B)
Evolutionary Model:
Initial Req
N
Feed back with

new Req.
Dev.
Application
User
validation
User
accept
Appl is Base lined
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
Refining &
Planning for the
next cycle
Advantages: -
Risk Root cause

analysis
Estimation
Contingencies
Implementation
This is the best suitable for developing the highly risk based project
(scientific projects)
10
Page 11
Drawbacks:
(C)
Req. Gathering
Risk analysis and estimation is not an easy task

It is a costly model
It is a time consuming model
Fish Model: Analysis
Design
Delivery &
Maintenance
Coding
Sys testing
SRS
BRS Review
SRS Review
HLD
LLD
SCD
TDD Review
Black
White box
testing
Box
testing
Test S/W
Changes
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

Initial& design
Phase
Validation
11
Page 12
BRS
SRS
Design &
coding
Test
Preparing proj plan

Preparing Test plan
Req.Phase testing
Design Phase testing
Program phase testing
TDD
SCD
S/W Build
Testing
System testing
Test management Process
User acceptance testing
Port Testing
S/W efficiency
Delivery & Maintenance
DRE=A/A+B
Test S/W changer
End of the Basic part
Testing part to be continued.
1.Build Acceptance Testing Or Build Verification Testing Or Sanity

Testing: It is a types of testing in which one will conduct over all testing on the released build
in order to check whether it is proper for further detailed testing or not. Even some
companies call it as smoke testing, but some companies says that just before releasing the
build the developers will conduct the overall testing on the build that is known as smoke
testing and once the build is released what ever the test engineers do in order to accept the
build is known as B.A.T or B.V.T or Sanity Testing.
2.Regression Testing: It is a type of testing in which one will perform testing on the already tested
functionalities again and again.
12
Page 13
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 engineers 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.
4.
- Testing (Alpha Testing): It is a type of user acceptance testing in which the test engineers will test the
application in our company, in the presence of the customer.
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 endusers 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.
13
Page 14
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.
10. Monkey Testing: It is a type of testing in which one will perform abnormal action on the application
intentionally in order to check the stability of the application.
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.
12. Exploratory Testing: It is a type of testing in which one will (Domain Experts) will perform testing on the
application with out having the knowledge of requirements but by exploring the
functionality.
13.End-To- End Testing: It is a type of testing in which one will perform testing on all the end- to-end
scenarios of the application.
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
14
Page 15
b. Direct URL Testing (Uniform Resource Location)
c. Fire Wall Leakage Testing.
The Soft Ware Testing Life Cycle Contains Six

Phases
They are
Test Planning
Test Development
Test Execution
Result Analysis
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: bandaru7778@gmail.com
15
Page 16
1.1 Objective: The Purpose of the document is clearly described here in this section
1.2 Reference Document: The list of all the documents that are refereed to prepare the test plan will be
listed out her in the section.
2.0 Coverage Of Testing: 2.1 Features to be tested: The list of all the features that are to be tested in this phase will be clearly
mentioned here in this section.
2.2 Features not to be tested: The list of all the features that are not planned for testing based on the
following criteria will be listed out here in this section
a. Out of scope features
b. Low risk features
c. The functionalities that are planned to be incorporated in future
d. The features that are to be skipped based on the time constraints.
3.0 Test Strategy: 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.1 Levels of Testing: The list of all the levels of testing that are followed by that company are listed
out here in this section
3.2 Types of Testing: The list of all the types of testing that are followed in that company will be
listed out here in this section.
3.3 Test Design Techniques: Technique: Technique is some thing i.e., used for accomplishing a complex task in an
easy manner.
A list of all the techniques that are used by that company while developing
the test cases will be listed out here in this section.
16
Page 17
Eg: - BVA (Banded value analysis)
ECP (Equivalence Class Partition)
3.4
Configuration Management:- To be discussed later
3.5 Test Metrics: The list of all the metrics that are maintained in that company will be listed
out here in this section
3.6 Terminology: The list of all the terms and the meaning that are used in that company will
be listed out here in this section
3.7 Automation Plan: The list of all the areas that are plan for automation in that company will be
3.8 List Of Automated Tools: The list of all the automated tools that are used in that company will be listed
out here in this section.
4.0 Base Criteria: 4.1 Acceptance Criteria: When to stop testing feeling that enough testing has been done on the
application is clearly described here in this section.
4.1 Suspension Criteria: When to suspend testing suddenly (abruptly) will be clearly mentioned here
in this section.
5.0 Test Deliverable: 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.
6.0 Test Environment: The customer specified environment would be clearly described here in this
section. The same environment will be simulated in the company and will be used
for testing purpose.
7.0 Resource Planning: Who has to do what is clearly described here in this section.
8.0 Scheduling: bandaru7778@gmail.com
17
Page 18
The starting dates and the ending data of the each and every tasks is clearly
planned here in this section.
9.0 Staffing& Training: How much staff is to be recruited and what kind of training is to be provided
is clearly described here in this section.
10.0 Risks & contingencies (Solution Plans): The list of all the potential risks and the corresponding solution plans will be
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
Contingencies (solution Plans):

i. Proper plan ensurance.
ii. Employees need to be maintained on the bench.
iii. What not to be tested has to be planned in case of imposed
dead lines.
iv. Severity & Priority based testing.
v. Proper Training needs to be provided.
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.
12.0 Approval Information: Who has to approve what is clearly described here in this section.
FRS (Functional Requirement Specification)
HLI (High level

LLI
(Low-level
Information)
Information)
Screen Shots
18
Page 19
USE CASES
Use Cases:
Use case is a description of functionality of certain features of an application
in terms of actors, actions& responses
Input information required for preparing the use case Document: i.
ii.
iii.
iv.
i.
Screen shot
Functional requirements
Special requirement/Business rules/Validation
Template
Screen Shot: User name

Password
Connect to
Login
Clear
Cancel
ii. Functional Requirements: a. Login screen should contain username, password, Connects To fields
and login, clear, cancel buttons.
b. Connect to is not a mandatory field but when ever user requires it
should allow him to select a data base option.
c. Up on entering valid username, valid password and clicking on login
button corresponding page must be displayed.
d. Up on clicking on the clear button the information present in all the
fields must be cleared and the cursor must be available in the user
name field
e. Up on clicking on the cancel button login screen must be closed.
iii. Special requirement/Business ruled/Validation: -
19
Page 20
a.
b.
c.
d.
e.
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.
iv. Use Case Template:

Name Of The Use Case
Brief Description of Use Case
Actors Involved
Special Requirements
Pre Condition
Post-Conditions
Flow of Events
:
:
:
:
:
:
:
v. Use Case Document:

Name of the use case:
Login use case.
Brief Description of use case: It Describes the functionalities of all the

features present in the login screen.
Actors Involved:
Normal user, Admin User.
Special Requirements: There are two types of special requirements

1.Explicit requirements
2.Implicit requirements
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.
List of Explicit requirements:
Initially whenever the login screen is Invoked Login, clear buttons

must be disabled.
20
Page 21
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.
List of Implicit Requirements:
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
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
Pre-Conditions: Login screen must be available

Post-Conditions: Either home page or admin page for the valid user and error
message for the invalid users
Flow of Events: There are three flows for the application
1. Main Flow
2.Alternative Flow
3.Exceptional Flow
1.Main Flow:
21
Page 22
Action
Response
1.Actor invokes the application.
1.Login Screen is displayed with the following fields

Username, Password, Connect to, Login, Clear&
cancel.
2.Actor enters valid user name, Valid

password and clicks on login button.
2.Either home page or admin page is displayed

depending up on the actor entered by authenticating.
3.Actor enters valid user name, valid

password, selects a database option and
clicks on login button.
3.Authenticates,Either home page or admin page is

displayed depending up on the action entered with
mentioned data base connection.
4.Actor enters invalid user name Valid

4.Go to Alternative flow table 1
5.Actor enters valid user name, Invalid

6.Actor enters both username and

password invalid and clicks on login
button.
7.Actor enters some information in to any

of the fields and clicks on clear button.
7.Go to Alternative glow table 4
8.Actor clicks on the cancel button.
8.Go to Alternative flow table 5.
1.Alternative flow table 1: -(Invalid User name)

Action
Actor enters invalid user name, valid
password and clicks on login button
2.Alternative Flow Table 2: -(Invalid Password)

Action
Actor enters valid user name, invalid
Response
Authenticates an error message is

displayed Invalid User name Please Try
again.
Response

displayed Invalid User Password Please
Try again.
3.Alternative Flow Table 3: - (Invalid username & Password)

Action
Response
Actor enters invalid user name, invalid

displayed Invalid User name and
password Please Try again.
4.Alternative Flow Table 4: - (Clear Click)

Action
Actor enters some information in any of
the fields and clicks on clear button
Response
All the fields are cleared and cursor is
placed in the user name fields
22
Page 23
5.Alternative Flow Table 4: -(Cancel click).

Action
Actor Clicks on the cancel button.
Response
Login screen is close
Identify the module to which the use case belongs.

Security module.
Identify the functionality of the use case with respect to the total functionality
Authentication
Identify the functional points and prepare the functional point document.
Identify the input required to perform testing

Valid & invalid Inputs
Identify the actors involved in the used case
Normal user & Admin user.
Identify whether the use case is linked with any other use case.
Home page and Admin page use cases
Identify the pre conditions
Login Screen mist be available
Identify the post conditions
Either home page or admin page for valid users and error message for
invalid users
Understand the main flow of the application
Understand the alternative flow of the application
Understand the special requirements
Document the test cases for the main flow
Document the test cases for the alternative flow
Document the test cases for the special requirements
Prepare the cross-reference matrix.
Functional Point: The point where an user can perform some action is known as
functional point.
23
Page 24
Types Of Test Cases:

There are Two types of test cases if we see broadly they are:
1. GUI Test Cases
2. Functional Test Cases
The Functional cases are further divided in to Two types
(a) Positive Test Cases,
(b) Negative Test Cases.
Guide Lines fro developing the GUI Test Cases:
Check for the availability of all the objects

Check for the alignments of all the objects up on customer requirements
Check for the consistency of all the objects
Check for the spellings and grammar
Apart from the above guide lines any thing else that can be tested just by
looking with out doing any actions will fall under GUI test cases
Guide Lines for Positive Test Cases:
A test engineer should have positive mind set up

He should consider the positive flow of the application
He should use only the valid Input
Guidelines for developing Negative Test Cases:
A test engineer should have negative mind set up

He should consider the negative flow of the application
He should use at least one invalid input per a set of data
Test Case Template: (a) Test Objective

(b) Test scenario
(c) Test procedure
(d) Test Data
(e) Test Cases
(a)
Test Objective: The main purpose of the document is described here in this section
(b)
Test Scenarios: -
24
Page 25
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.
The plan for testing the functionalities is briefly described here
in this section
(d)
Test Data: The date that is required for testing is made available here in this
section
(e)
Test Cases: -
The format of a test case template is given below

TCID TC
DESCRIPTION EV AV Result Severity Priority Reference
TYPE
Test case Table

TC
ID
TYPE
GUI
GUI
GUI
Description
Expected Value
Actual Value
Check for the availability

of all the objects as per
the Login Obj Tab
All the objects must be All the objects

are available as
available as per the
per the login obj
login obj tab
Pass
tab
All the objects must be
All the objects
consistent with each
are consistent
other
with each other
Check for the constancy

of all the objects
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
Tab.xls
properly
Result Severity Priority Reference
Pass
Pass
25
Page 26
GUI
Check for the enable

property of login, clear
and cancel buttons
Initially login, clear

must be disabled and Login, clear and
cancel button must be cancel buttons
enabled
Fail
are enabled
Initially the cursor must Initially the
cursor is present
be positioned in the
in the username
user name field
Pass
field
Check for the initial

position of the cursor
Enter some information in
to user name and
Login button must be
password field and check
enabled
for the enabled property of
Positive login button
Enter some info in to any

of the fields and check for Clear button must be
enabled
the enabled property of
Positive clear button
10
11
12
13
14
15
GUI
Login button is
enabled
Clear button is
enabled
Corresponding
Corresponding page pages are
Enter user name,
must be displayed as displayed as per
Password as per the VIT per the VIT
valid in puts
Positive and click on login button
table
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
Positive option and click on login
base connection
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
Positive clear button
user name field.
Pass
Pass
Pass
Pass
Fail
Login screen should be

closed
Login screens
Pass
Positive Click on the cancel button
closed
Tabbing order is
as follows
Tabbing order must be
Username,
as follows User name,
Password,
Password, Connect to,
Connect to
Login, Clear, Cancel
Check for the tabbing
Login, clear,
Pass
Positive order of all the objects
Cancel
Enter username,
Password as per the IVIT
Negative and click on login button
Enter some information
only in to the user name
field and check for the
enabled property of login
Negative button
Enter some information
only in to the password
field and check for the
enabled property of login
Negative button
Corresponding
messages should be
displayed as per IVIT

disabled

disabled
Corresponding
error messages
are not displayed
Fail
as per IVIT
Login button is
enabled
Fail
Login button is
enabled
Fail
26
Page 27
LOGIN OBJ TAB

Sno
Obj Name
Type
1 User name
Text Box
2 Password
Text Box
3 Connect To
Combo box
4 Login
Button
5 Clear
Button
6 Cancel
Button
Valid Inputs Table

Sno User Name
Password
Expected Page
Actual value
Result
Suresh
qtp
Admin
Admin
Pass
Raja
rani
Home page
Home page
Pass
Chiru
mbbs
Home page
Home page
Pass
Praveen
puppy
Home page
Home page
Pass
NTR
illu
Home page
Home page
Pass
Admin
Admin
Admin
Admin
Pass
Valid Inputs Table (IVIT)

Sno User Name Password Expected Page
Actual value
Result
Suresh1
qtp
Invalid User name Plz try again
Admin
Fail
Raja2
rani
Invalid User name Plz try again
Invalid User name Plz try

again
Pass
Chiru
DADA
Praveen
TOPI
NTR1
illu4
Admin5
Admin6
Invalid password Plz try

again
Invalid password Plz try
again
Invalid user name &
password Plz try again
Invalid user name &
Invalid password Plz

try again
Invalid password Plz
try again
Invalid user name &
Invalid user name &
Pass
Pass
Pass
Pass
27
Page 28
A test Engineer will do the following during the test execution

1. He will perform the action that is described in the description column
2. He will observe the actual behavior under the actual value column.
3. He will document the observed value under the actual value column.
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: -
The lists of defect numbers are mentioned here in this section.

Defect Description: What exactly the defect is clearly described here in this section.
Steps for reproducibility: The list of all the steps that are followed by the test engineer to identify the defect
will be listed out 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.
28
Page 29
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 whom the defect is assigned.
Defect Id
Defect
Description
Initially Login, cear

buttons are
enabled instead of
being disabled
Steps for
Date Of
Version Build
Reproducibility Submitter Submission NO No
Assign
to
SeverityPriority Status
Not Applicable
Sri Balaji
11-Feb-08
1.0.0 1
Sri Balaji
11-Feb-08
1.0.0 1
Sri Balaji
11-Feb-08
1.0.0 1
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
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.
29
Page 30
Up on entering the
information only in
to the user name
field login button is
enabled instead of
being disabled
4
Upon entering the

information only in
to the password
field login button is
enabled instead
being disabled
5
1.Enter some
information in to
username field
2.Check for the
enabled property of
login button.
3.Observe that login
button is enabled
instead of being
disabled.
1.Enter some
information in tho
password field
2.Check for the
enabled property of
login button
3.Observe that login
button to enable
instead of being
disabled
Sri Balaji
14-Feb-08
1.0.0 1
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
Steps for reproducibility: The list of all the steps that are followed by the test engineer to identify
the defect will be listed out 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.
30
Page 31
Severity: How serious the defect is defined in terms of severity, Severity is
classified in to four types:
1.Fatal
2.Major
3.Minor
4.Suggestion
(Sev1) or S1 or 1
(Sev2) or S2 or 2
(Sev3) or S3 or 3
(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
Val2
Main Menu
Result
UN
AVAILABL
E
ADD
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
BAD
31
Page 32
4.Suggestions: If at all the problems are related to the value of the application then such
type defects are treated to be suggestions.
+Ve integer Box
Some
alphabets
Invalid
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.
32
Page 33
Bug Life Cycle: HOL

D
Testers
error
REQ
As per
design
No
Is it
Reall
y
Defe
ct
DEV
OP
EN
Rectific
ation
M1
Build #1
RE
ope
Nen
Is
defect
is
TESTING
really
If
verifie
Defect
d
Fixed for
verification
Build #2
Clos
STOP TESTING
ed
33
Page 34
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.
34
Page 35
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
35

Why Did You Choose This Course?: Project

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Why Did You Choose This Course?: Project

Uploaded by

Copyright:

Available Formats

Page 1

Why did you choose this Course?

Scope of getting job is very high.

explicitly the s/w companies are

can do the course?

Any graduate can do this course at this point of time

What exactly we require to get a job?

Project is some thing that is developed based on the particular

Classical definition for quality: - Quality is defined as justification of all the

Defect: - Defect is defined as deviation from the requirements

I. Initial Phase or Requirements Phase :

Proof: The proof document of this phase is Requirements Document. This is

Proof: - The proof of this phase is system Requirement specification.

Proof: The proof document of this phase is Technical design document.

Proof: The proof document of this phase is source code Document.

VI. Delivery & Maintenance Phase:

Methodology or Testing techniques:

There are three methods of testing

DRIVER: -While integrating the modules in bottom up approach. If at all any

4.System Level Testing:

Software Development Models: 1.Water Falling Model

Black box testing

suitable model for gathering the clear requirements.

Drawbacks: It is not a complete model

Feed back with

Appl is Base lined

Cannot define the dead lines

Spiral Model: Defining the objectives/WA/Constraints

Risk Root cause

Risk analysis and estimation is not an easy task

Fish Model: Analysis

Drawbacks: o Time consuming Model

(D) V-Model: Verification

Preparing proj plan

Delivery & Maintenance

Test S/W changer

End of the Basic part

Testing part to be continued.

1.Build Acceptance Testing Or Build Verification Testing Or Sanity

The Soft Ware Testing Life Cycle Contains Six

Plan: It is a strategic document, which describes how to perform a task in an effective,

1.0 Introduction: bandaru7778@gmail.com

Configuration Management:- To be discussed later

8.0 Scheduling: bandaru7778@gmail.com

Contingencies (solution Plans):

FRS (Functional Requirement Specification)

HLI (High level

Screen Shot: User name

iii. Special requirement/Business ruled/Validation: -

iv. Use Case Template:

v. Use Case Document:

Login use case.

Brief Description of use case: It Describes the functionalities of all the

Normal user, Admin User.

Special Requirements: There are two types of special requirements

List of Explicit requirements:

Initially whenever the login screen is Invoked Login, clear buttons

Cancels Button must be always enable.

List of Implicit Requirements:

Pre-Conditions: Login screen must be available

Flow of Events: There are three flows for the application

1.Actor invokes the application.

1.Login Screen is displayed with the following fields