Testing Material

TARAKESH
TESTING TOOLS
MANUAL TESTING
Software:
A Group of statements ,set of logic and related data which gives
instructions to system what to do and how to do.
As per the usage ,Software has divided into two types,
1.Product Software
2.Project Software
Product Software:
Software which is developing for Specific segment of customers
(Group of customers).
Project Software:
Software which is developing for the single client.
As per the work ,there are two different types of companies available in
industry.
Types of Companies:
1.Product based company
2.Service based company
Product based company:
A Company which is mainly focussing on developing their own
software product is called product based company .
EX:
Microsoft ,Google ,HP ,Yahoo ,Dell , etc.....
Service based company:
A Company which is mainly focussing on developing individual project
to the individual client is called service based company .
EX:
Accenture ,Infosys ,TCS ,CTS ,CSC ,etc.......
TARAKESH
tarakeshsaptesting@gmail.com
Page 1
TARAKESH
TESTING TOOLS
Different types of teams in project :

There are two types of teams available in every project.
1.Development team
2.Testing team
Development team:
The responsibility of the development team has to develop the
application as per the client requirements .
Testing Team:
The responsibility of the testing team has to test the application. or
verify whether the development team has developed the application as
per the client requirements or not
Note:
Even though ,we have two different types of teams in a project finally
both the teams has to work only based on client requirements.
History of the software :
Software came into the picture on early 1990`S to avoid the manual
transaction in client business .
Software testing came into the picture in 1996-97 to maintain the
quality in the software .
DIFFERENCE BETWEEN DEVELOPMENT AND TESTING
1DEVELOPMENT
TESTING
1.Development is respective to the

technology .
EX:
As java developer we can able
to develop only java applications.
1.Testing is irrespective of the

technology
2.More technical knowledge is

required to develop the application
EX:
As a Tester we can able to test
any application which has
developed in any technology .
2.Less technical knowledge is
required
3.Technology might be changing

TARAKESH
Page 2
TARAKESH
TESTING TOOLS
frequently.
Software testing :
Performing Testing on the software application or product is it
working as per the client requirement is called software testing.
Software testing has been divided into two Ways or Styles or
methods
1.Manual testing.
2.Automation testing.
Manual testing:
Performing testing on the software applications with the human
interaction is called manual testing
Automation testing :
Performing testing on the software application with the help of any
Automation tools is called Automation Testing.
Note:
In both manual and Automation we are Performing The same testing.
but the way we are performing testing is different in both manual and
automation testing .
Company:
Company is the Organization who is developing the software as per
the client requirements.
EX:
TCS, Infosys, CSC, etc.....
Client:
Client is the individual (or) Organisation who is providing requirements
to company to develop the software.
EX:
TARAKESH
Page 3
TARAKESH
TESTING TOOLS
ICICI, Ariel, Vodafone, Indian railways etc..
****************
Testing Types:
Sanity Testing or Build Acceptance Testing or Build Verification
Testing:
Validating or Testing the Major Functionality of the application is called
Sanity Testing. Once the application is developed and deployed into
Testing Environment. we perform the sanity testing because the major
functionality of application is working properly, then only we can continue
further testing.
During the Sanity Testing, if we identify any defect, we have to report the
defect immediately to the development team. Development team has to
fix the defect immediately.
Usability Testing or User interface Testing:
Verify the user friendliness of the application in terms of Colour, Logos,
Images, Fonts and alignment of the pages etc. is called the Usability
Testing.
Ex:
Perform Sanity Testing and Usability Testing on Car?
Sanity Testing
1.Verifying whether Car is starting
or not
2.Verifying whether break is
working or not
Usability Testing
1.Verifying the Colour of the Car
2.Verifying whether the car is
comfortable or not
3.Verifying the Interior of the Car.
3.Verifying whether clutch is

working or not
Functionality Testing:
TARAKESH
Page 4
TARAKESH
TESTING TOOLS
Validating the overall functionality of the application that includes both
Major and Minor functionalities is called Functionality Testing.
EX: Car is Starting or not , colour of the car etc.
Data Base Testing:
Validating the back-end database with respect to the front end application
is called data base testing.
During the data base testing we perform three types of Validations.
1. whatever we are performing in the front end application, that should
reflect successfully in the back end data base.
Ex:
If we add one user in the front end application, that user should add
successfully in the back-end database.
Application
Data Base
Name:--------------------Address:------------------City:-----------------------Name
SAVE
Address
Tarake Hyd
sh
City
Hyderaba
d
2. Whatever we
back-end database,
reflect successfully in the front end application.
perform in the
that should
Ex: If we delete one user in back-end database, that the user should
delete successfully in front end application.
TARAKESH
Page 5
TARAKESH
TESTING TOOLS
Application
Data Base
Name:--------------------Address:------------------City:------------------------
Displ
SAVE ay
Nam Address
e
City
Hem AU
a
CH
3. Verifying the
whether the
application is fetching or getting or retrieving the data from the back-end
to front end application or not.
TARAKESH
Page 6
TARAKESH
TESTING TOOLS
Application
Data Base
SEAR
CH
Nam
e
Address
City
Hem
a
Rajt
ha
Compatibility Testing
compatibility Testing
browser Testing:
or Browser
or Cross
Performing testing on application in different browsers like Internet

explorer, fire fox and Chrome etc. is called Compatibility testing.
There are two types.
TARAKESH
Page 7
TARAKESH
TESTING TOOLS
1. Backward compatibility
2.Forward compatibility
Testing the application in the older versions of the browser which was
developed in latest versions.
Backward compatibility:
Ex: Testing in IE6 and IE7 which was developed in IE10.
Forward compatibility:
Testing the application in the New versions of the browser which was
developed in old versions.
Ex: Testing in IE10 which was developed in IE6 and IE7.
Configuration Testing:
Testing application on different system configurations like RAM, Hard disc,
processor and OS is called Configuration testing.
Internationalization Testing or Globalization Testing or I18N
Testing:
Performing testing on the application in different languages like French,
Spanish and Chinese etc. is called Internationalisation Testing.
Localization Testing or L10N Testing:
Performing Testing on the application in different local languages like
Telugu, Tamil and Hindi etc is called Localization testing.
Note: The terms are frequently abbreviated to the numeronyms i18n (where 18 stands for the number of
letters between the first i and the last n in the word internationalization, a usage coined at DEC in the 1970s or
80s)[1] and L10n respectively, due to the length of the words.
Partial Release:
In this approach, we are releasing the completed modules to client in the
current release and rest of the incomplete modules will be released along
with the next release.
TARAKESH
Page 8
TARAKESH
TESTING TOOLS
Postponed Release:
In this approach, Client will postpone the release date to future, so by that
time we have to complete the project.
Different Status of the Project:
There are three different status available in a project.
1. Green
2. Yellow
3. Red
Green:
If everything is going fine in the project that means, development team
has completed development in time and Testing team has completed
testing in time, then the Status of the project is Green.
Yellow:
Some delay in the project, but we can able to complete the project in time
by working extra hours or in week end. In that case, the Status of the
project will be yellow.
RED:
More delay in the project and we cannot able to complete the project in
time. In that case, the Status of project will be RED.
Test Data:
A data or a value which we use to perform testing on the application is
called Test data.
Ex: user name, Password
Positive Testing:
Performing testing on the application with positive data or valid data is
called positive testing.
Ex: Testing the Login functionality with Valid UID and Password
Negative Testing:
TARAKESH
Page 9
TARAKESH
TESTING TOOLS
Performing the testing on the application with negative data or invalid
data is called Negative Testing.
Ex: Testing the Login functionality with Invalid UID and Password
Static Testing:
Performing Testing on the application without performing any activity or
action is called Static Testing.
Ex: User can able to see Name, Address, City and Save on the application.
SAVE
Dynamic Testing:
Performing Testing on the application by performing an activity or action is
called Dynamic Testing.
Ex: User can successfully register by entering Name, Address, City and
Save.
SAVE
TARAKESH
Page 10
TARAKESH
TESTING TOOLS
Parallel Testing:
Performing Testing on the application by comparing with similar type of
application in the market is called Parallel Testing.
we perform this testing only when we don't have the clear requirements.
Ex: Performing Testing in the ICICI online banking application by
comparing with SBI online application.
Recovery Testing:
During this Testing we verify how much time the application is taking to
come back from the abnormal state(Down state) to normal state(upstate)
is called the Recovery Testing
We need to calculate how much time the application is taking to come
back from abnormal state to Normal state. While releasing the application
to client, we need to provide this recovery time.
Accessibility Testing:
Verifying whether the application has developed in World Wide Web
standards or not . This Testing is suitable only for web based applications.
Installation Testing or Deployment Testing:
During this Testing, development team will be involving to perform the
testing on the application to verify whether the application has been
deployed successfully from one environment to another environment or
not.
TARAKESH
Page 11
TARAKESH
TESTING TOOLS
Ex: In most of the projects, deployment testing will be performed only by
the development team. Because development team only will do the
deployment in a project.
Different Environments in a Project:
There are four different types of environments available in a project.
1. Development Environment
2.Testing Environment
3. UAT Environment or pre production
4. Production environment
1. Development Environment:
This is the first environment in every project, development team will be
involving to develop the application as per client requirement. After
successful completion of the development, they will deploy the application
into testing environment.
2.Testing Environment:
Testing team will be involving to perform testing on the application as per
the client requirement. After successful completion of the testing in
Testing environment. Testing team will give the confirmation to the
development team. Based on the confirmation development team will
deploy the application into UAT.
3. UAT Environment:
Testing Team along with client will be involving to perform testing on the
application
4. Production environment:
In this environment, Client or end user will be involving to use or work on
the application.
SDLC
TARAKESH
Page 12
TARAKESH
TESTING TOOLS
Software Development Life Cycle
or
System Development Life Cycle
Or
Development Life Cycle
SDLC is the Step by Step Process which we follow to complete the soft
ware Project that includes both development and Testing.
Different Phases in SDLC:They are six different phases are there in SDLC, They are
1. Feasibility Analysis and Requirement collection
2. Planning
3.Design
4.Coding
5.Testing
6.Delivery and Maintenance
Requirements:
This is the first phase of SDLC, once the project has been confirmed
between client and company then client will provide the requirements to
company or BA(Business Analyst) team from the company will collect
requirements from the Client.
For Collecting the requirements from the client BA team follow the below
techniques.
1. KT( Knowledge Transfer)
2.Questionniares
3.Inspection
1. KT( Knowledge Transfer):
TARAKESH
Page 13
TARAKESH
TESTING TOOLS
Client team will explain the complete business process and their
requirement to the BA.
In this technique, BA Team will collect the requirement by requesting the
client to transfer information about their business.
Questionnaires:
In this technique, BA team will collect the requirement by asking some
questions to the client about client business.
Inspection:
In this technique, BA team will collect the requirement directly by step
into client business and observe how the client is doing the business
manually.
Analysis :
During this phase, BA team will be involving to analyse the collected
requirement and they will be designing the understandable form of the
requirement documents called BRS(Business requirement specification),
FRS and SRS.
BRS:
One BRS document is the word format template and contains one flow of
the requirements. BRS document defines what to develop and what to
test. Based on the BRS the development team can understand what to
develop and the testing team can understand what to test.
Ex:
1. User can able to see logo in the top left hand corner, Date & Time in top
right corner.
2. User can able to see UID, Password, Sign in button.
TARAKESH
Page 14
TARAKESH
TESTING TOOLS
FRS Document:
FRS document is in excel format and contains the rules and conditions of
all requirements of BRS documents. FRS document defines how to develop
and test. Based on this document dev.team can understand how to
develop and Testing team can understand how to test in a project.
S.No
BRS
1 BRS 1.1
Req No1.1
2 BRS 1.2
Req No1.2
3 BRS 1.3
Req No 1.3
4 BRS 1.4
Req No 1.4
5 BRS 1.5
Req No 1.5
TARAKESH
Rules and Conditions
Author
Date
Logo size should be

24*18
Date format should be
MM/DD/YYYY
Time format should be
24 Hours
UID, PWD should be text
box
Text Box
Sign in should be
Button
Page 15
TARAKESH
TESTING TOOLS
2) Planning & Design:
In this phase the system and software design is prepared from the requirement specifications which
were studied in the first phase. System Design helps in specifying hardware and system requirements
and also helps in defining overall system architecture. The system design specifications serve as
input for the next phase of the model.
Based on the user requirements and the detailed analysis of a new system, the new system
must be designed. This is the phase of system designing. It is the most crucial phase in the
development of a system. The logical system design arrived at as a result of system analysis
and is converted into physical system design. In the design phase the SDLC process
continues to move from the what questions of the analysis phase to the how . The logical
design produced during the analysis is turned into a physical design - a detailed description of
what is needed to solve original problem. Input, output, databases, forms, codification
schemes and processing specifications are drawn up in detail. In the design stage, the
programming language and the hardware and software platform in which the new system will
run are also decided. Data structure, control process, equipment source, workload and
limitation of the system, Interface, documentation, training, procedures of using the system,
taking backups and staffing requirement are decided at this stage.
There are several tools and techniques used for describing the system design of the system.
These tools and techniques are: Flowchart, Data flow diagram (DFD), Data dictionary,
Structured English, Decision table and Decision tree which will be discussed in detailed in the
next lesson.
3) Coding: On receiving system design documents, the work is divided in modules/units and
actual coding is started. Since, in this phase the code is produced so it is the main focus for
the developer. This is the longest phase of the software development life cycle.
The system design needs to be implemented to make it a workable system. his demands the
coding of design into computer language, i.e., programming language. This is also called the
programming phase in which the programmer converts the program specifications into
computer instructions, which we refer to as programs. It is an important stage where the
defined procedures are transformed into control specifications by the help of a computer
language. The programs coordinate the data movements and control the entire process in a
system. A well written code reduces the testing and maintenance effort. It is generally felt that
the programs must be modular in nature. This helps in fast development, maintenance and
future changes, if required. Programming tools like compilers, interpreters and language like
c, c++, and java etc., are used for coding .with respect to the type of application. The right
programming language should be chosen.
4) Testing: After the code is developed it is tested against the requirements to make sure that
the product is actually solving the needs addressed and gathered during the requirements
phase. During this phase unit testing, integration testing, system testing, acceptance testing
are done.
Before actually implementing the new system into operations, a test run of the
system is done removing all the bugs, if any. It is an important phase of a
successful system. After codifying the whole programs of the system, a test
plan should be developed and run on a given set of test data. The output of the
TARAKESH
Page 16
TARAKESH
TESTING TOOLS
test run should match the expected results. Sometimes, system testing is
considered as a part of implementation process.
Using the test data following test run are carried out:
Program test
System test
Program test : When the programs have been coded and compiled and brought
to working conditions, they must be individually tested with the prepared test
data. All verification and validation be checked and any undesirable happening
must be noted and debugged (error corrected).
System Test :
After carrying out the program test for each of the programs of the system and
errors removed, then system test is done. At this stage the test is done on
actual data. The complete system is executed on the actual data. At each stage
of the execution, the results or output of the system is analyzed. During the
result analysis, it may be found that the outputs are not matching the
expected output of the system. In such case, the errors in the particular
programs are identified and are fixed and further tested for the expected
output. All independent modules be brought together and all the interfaces to
be tested between multiple modules, the whole set of software is tested to
establish that all modules work together correctly as an application or system
or package.
When it is ensured that the system is running error-free, the users are called
with their own actual data so that the system could be shown running as per
their requirements.
5) Deployment: After successful testing the product is delivered / deployed to the customer for their
use.
After having the user acceptance of the new system developed, the implementation phase begins.
Implementation is the stage of a project during which theory is turned into practice. The major steps
involved in this phase are:
Acquisition and Installation of Hardware and Software
Conversion
User Training
Documentation
The hardware and the relevant software required for running the system must be made fully
operational before implementation. The conversion is also one of the most critical and expensive
activities in the system development life cycle. The data from the old system needs to be converted to
operate in the new format of the new system. The database needs to be setup with security and
recovery procedures fully defined.
During this phase, all the programs of the system are loaded onto the users computer. After loading
the system, training of the user starts. Main topics of such type of training are:
TARAKESH
Page 17
TARAKESH
TESTING TOOLS
How to execute the package?
How to enter the data?
How to process the data (processing details)?
How to take out the reports?
After the users are trained about the computerized system, working has to shift from manual to
computerized working. The process is called Changeover. The following strategies are followed for
changeover of the system.
1. Direct Changeover: This is the complete replacement of the old system by the new system. It
is a risky approach and requires comprehensive system testing and training.
2. Parallel run : In parallel run both the systems, i.e., computerized and manual, are executed
simultaneously for certain defined period. The same data is processed by both the systems.
This strategy is less risky but more expensive because of the following facts:
Manual results can be compared with the results of the computerized system.
The operational work is doubled.
Failure of the computerised system at the early stage does not affect the working of the
organization, because the manual system continues to work, as it used to do.
(iii) Pilot run: In this type of run, the new system is run with the data from one or more of the previous
periods for the whole or part of the system. The results are compared with the old
system results. It is less expensive and risky than parallel run approach. This strategy builds the
confidence and the errors are traced easily without affecting the operations.
The documentation of the system is also one of the most important activity in the system development
life cycle. This ensures the continuity of the system. Generally following two types of documentations
are prepared for any system.
User or Operator Documentation

System Documentation
User Documentation: The user documentation is a complete description of the system from the users
point of view detailing how to use or operate the system. It also includes the major error messages
likely to be encountered by the user.
System Documentation: The system documentation contains the details of system design, programs,
their coding, system flow, data dictionary, process description, etc. This helps to understand the
system and permit changes to be made in the existing system to satisfy new user needs.
Maintenance:
Once when the customers starts using the developed system then the actual
problems comes up and needs to be solved from time to time. This process
where the care is taken for the developed product is known as maintenance.
Maintenance is necessary to eliminate errors in the system during its working
life and to tune the system to any variations in its working environments. It
must meet the scope of any future enhancement, future functionality and any
TARAKESH
Page 18
TARAKESH
TESTING TOOLS
other added functional features to cope up with the latest future needs. It has
been seen that there are always some errors found in the systems that must
be noted and corrected. It also means the review of the system from time to
time.
The review of the system is done for:

knowing the full capabilities of the system
knowing the required changes or the additional requirements
studying the performance.
If a major change to a system is needed, a new project may have to be set up
to carry out the change. The new project will then proceed through all the
above life cycle phases.
Agile software development stresses rapid iterations, small and frequent

releases, and evolving requirements facilitated by direct user involvement in the
development process. Serenas application lifecycle management tools provide a
framework to visualize scope, orchestrate mundane and repetitive development
tasks, and enforce process. Unlike agile-specific products offered by agile-only
TARAKESH
Page 19
TARAKESH
TESTING TOOLS
vendors, Serena products are methodologyneutral and can be applied equally
well to agile as well as more traditional serial development processes, so they
can support all the development activities within an enterprise.
Scrum concepts For more detailed information on Scrum, refer to one of the
many books on the topic, visit www.scrumalliance.org, or visit wikipedia. Here
are a few of the most important concepts: Burndown chart. This chart, updated
every day, shows the work remaining within the sprint. The burndown chart is
used both to track sprint progress and to decide when items must be removed
from the sprint backlog and deferred to the next sprint. Product backlog. Product
backlog is the complete list of requirementsincluding bugs, enhancement
requests, and usability and performance improvementsthat are not currently in
the product release. ScrumMaster. The ScrumMaster is the person responsible for
managing the Scrum project. Sometimes it refers to a person who has become
certified as a ScrumMaster by taking ScrumMaster training. Sprint backlog.
Sprint backlog is the list of backlog items assigned to a sprint, but not yet
completed. In common practice, no sprint backlog item should take more than
two days to complete. The sprint backlog helps the team predict the level of
effort required to complete a sprint.
Agile development model is also a type of Incremental model. Software is developed in incremental, rapid cycles. This results
in small incremental releases with each release building on previous functionality. Each release is thoroughly tested to
ensure software quality is maintained. It is used for time critical applications. Extreme Programming (XP) is currently one of the
most well known agile development life cycle model.
Diagram of Agile model:
Advantages of Agile model:
Customer satisfaction by rapid, continuous delivery of useful software.

People and interactions are emphasized rather than process and tools. Customers, developers and testers
constantly interact with each other.
Working software is delivered frequently (weeks rather than months).
Face-to-face conversation is the best form of communication.
TARAKESH
Page 20
TARAKESH
TESTING TOOLS
Close, daily cooperation between business people and developers.
Continuous attention to technical excellence and good design.
Regular adaptation to changing circumstances.
Even late changes in requirements are welcomed
Disadvantages of Agile model:

In case of some software deliverables, especially the large ones, it is difficult to assess the effort required at the
beginning of the software development life cycle.

There is lack of emphasis on necessary designing and documentation.
The project can easily get taken off track if the customer representative is not clear what final outcome that they
want.
Only senior programmers are capable of taking the kind of decisions required during the development process.
Hence it has no place for newbie programmers, unless combined with experienced resources.
When to use Agile model:
When new changes are needed to be implemented. The freedom agile gives to change is very important. New
changes can be implemented at very little cost because of the frequency of new increments that are produced.
To implement a new feature the developers need to lose only the work of a few days, or even only hours, to roll back
and implement it.
Unlike the waterfall model in agile model very limited planning is required to get started with the project. Agile
assumes that the end users needs are ever changing in a dynamic business and IT world. Changes can be discussed and
features can be newly effected or removed based on feedback. This effectively gives the customer the finished system
they want or need.
Both system developers and stakeholders alike, find they also get more freedom of time and options than if the
software was developed in a more rigid sequential way. Having options gives them the ability to leave important decisions
until more or better data or even entire hosting programs are available; meaning the project can continue to move forward
without fear of reaching a sudden standstill.
STLC
Software Testing life Cycle
or
End to End Process of Testing
or
Testing Life Cycle
or
Manual Testing Process
STLC is the step by step process which we follow to complete the testing
activities in a project.
They are 12 different Phases or stages available in STLC.
TARAKESH
Page 21
TARAKESH
TESTING TOOLS
1. Test initiation
2. Test Plan
3. Identify the Test Scenarios
4. Identify the Testable Requirements
5. Test Case Design
6. Test Data Preparation
7. Test case Execution in Testing Environment
8. Defects
9. Test Case Execution in UAT Environment
10. Defects
11. Regression Testing
12. Test Closure
1. Test initiation:
This is the first phase in STLC, once the project has been confirmed
between the company and Client. Project Manager will get the
confirmation mail from the higher level management. Once the project
manager gets the confirmation mail, PM will be analyzes the Scope of the
project and forms the team by recruiting the resources.
PM will recruit the resources in two different ways.
1. Internal Recruitment
2. External Recruitment
1. Internal Recruitment:
Recruiting the resources from the available resources within the company
or who are on the bench is called internal recruitment.
TARAKESH
Page 22
TARAKESH
TESTING TOOLS
2. External Recruitment:
Recruiting the resources from other companies is called external
recruitment.
Once the PM has formed the Team based on the scope and complexity,
Client and PM will be dividing the entire work into multiple projects(Tasks)
and PM will be assigning the recruited resources to the project based on
the experience, designation and skill set.
Ex:
2. Test Plan:
During this phase Test lead along with Senior members in a project will be
involving to design the Test Plan Document.
Test Plan Document is the route map document or high level document
for testing. This document designs what to test, who test, when to test
and how to test. This document is in the format of Word which is available
in share point.
Contents in the Test Plan document:
1. Description or Summary:
It defines the brief description of the Project, for the project which we are
designing the Test Plan and the project description need to be Specified in
the contents.
Ex:
If we are designing the Test Plan document for Personal Banking Project,
we need clearly specify the description about the personal banking.
2. Author(Test Lead):
It defines the resource who has designed this document(Test Lead).
3. Reviewed by:
It defines who has reviewed this document(PM, Client or Onsite
coordinator).
4.Entry Criteria:
TARAKESH
Page 23
TARAKESH
TESTING TOOLS
It defines when to start the Testing Activities in a Project. We start the
Testing Activities in a Project as soon as we got the requirement in the
form of BRS and FRS document from BA team.
5.Exit Criteria:
It defines when to close the Testing Activities in a Project. we close Testing
activities only when we executed all the test cases and once all the
defects are closed.
6.Suspension Criteria:
It defines when to stop or Suspend the Testing activities in a Project. we
suspend the testing activities in the below situations.
a. Environment Issues: Application is not opening and Application is
Closing suddenly etc.
b. Exceptions: Java exception error, null pointer exception error, page
not found error
c. Application Crashes: Application hanging, closing suddenly
7. Resumption Criteria:
If defines when to resume or Continue the testing activities in a project.
We resume the Testing Activities in the below situations.
a. When the Environment issues resolved
b. When Exceptions got cleared
c. When the application Crashing issues got resolved
8.Resources:
It defines resources who are working in the project. It includes both
offshore team, onsite team, BA Team, PM and client.
Ex:
Off shore Team: 20 Testers
Onshore Team : 1 Tester
BA Team : 3 Members
PM: 1 Member
Client: ABC
Note: Client: A person or who is working in Clients Business is called
client. or who gave us the project.
TARAKESH
Page 24
TARAKESH
TESTING TOOLS
9.Features to be tested:
It defines the features or functionalities which we need to test the project
in current release.
10.Features not to be tested:
It defines the features or functionalities which we need not to test the
project in current release.
Ex: As per the client requirements we need to test 150 functionalities out
of 200 functionalities in a application. In that case we need to specify the
150 functionalities which we need to be tested and remaining 50
functionalities not to be tested.
Testing Types to be performed: It defines the types of testing which
we need to use to perform testing on application. The types of Testing
which we are performing will be different from application to application.
so that whichever the types of testing ,we have to specify clearly in this
content
EX:
compatibility and performance testing is mandatory for web based and
not required for the windows application
12.automation tools to be used:
It defines the types of the automation tools which we need to use to
perform automation testing in project .
EX:
QTP, Selenium, QC,...etc
13.Technology to be used:
It defines the Software, Hardware, Databases, Which the
development team is using to develop the application in the project.
EX:
Java, . Net, Oracle etc........
14.Test strategy:
It defines The Process OR approach which we need to follow to complete
The testing activities in project.
TARAKESH
Page 25
TARAKESH
TESTING TOOLS
3.Identify the test scenario:
During this phase senior members in project will be involving to
identify the test scenarios
Test scenarios is nothing but The high level requirement. which
contains multiple sub requirements.
Once we get the requirements in the form of BRS and FRS
documents we need start identifying the test scenarios . we are
identifying The Test scenarios in excel and after that we are
performing reviews.
4.Identify the Testable Requirement:
During this phase Testing team will be involving to identify the
testable requirement in a project.
Testable requirement is, The requirement which we need
to test in current release. Some of the requirements we are going
to test in future releases. so that whichever the requirements we
need to test in the current releases, those requirements are
identifying as a testable requirements.
we are identifying the testable requirement in excel sheet
and after that we are performing reviews after completion of
client review, client will sign-off the requirements and then we
are exporting the requirements from excel sheet to Quality
Centre.
EX:
S.N
O
Scenario
Req No
Internet
Banking
Loan
BRS1.1
Req 1.1
BRS
Require
ment
Author
Date of
commen
t
TARAKE 09/03/20
SH
15
Test Case Design:

TARAKESH
Page 26
TARAKESH
TESTING TOOLS
During this phase, testing team will be involving to design the test case
for identified requirement.
Test case:
A sequential, elaborated, executable form of the requirement is
called Test case.
In every project, we are getting the requirement in the short cut
format. It is difficult to perform the testing on application with
short cut requirement format. That is the reason we are
elaborating requirement in the step by step executable format is
called Test Case.
Test case Design Technique:
A technique which we use to design the test cases in a project is
called Test case Design technique or black box testing technique
or Testing Techniques.
There are three different types of techniques.
1. BVA ( Boundary Value Analysis)
2.ECP(Equivalence Class Partition)
3. Error Guessing
BVA:
BVA defines the range of data which we need to use to perform
testing on the application. If any requirement is having the range
of the data, we need to prepare the BVA for that requirement and
based on the BVA only we design test cases.
They are different Classes available in the BVA.
1. Minimum
2.Maximum
3. Minimum - 1
4. Maximum -1
5. Minimum + 1
6. Maximum + 1
TARAKESH
Page 27
TARAKESH
TESTING TOOLS
Ex:
1. UID Should accept the 7-14 Characters
Min = 7 - Pass
Max = 14 - pass
Min-1 = 6 - Fail
Max - 1 = 13 - pass
Min + 1 = 8 - Pass
Max + 1 = 15 - Fail
2. Password should accept only (5-10) characters
Min = 5 - Pass
Max = 10 - Pass
Min - 1 = 4 - Fail
Max - 1 = 9 Pass
Min + 1 = 6 - Pass
Max + 1 = 11 - Fail
3. Prepare the BVA for the calendar which should accepts the
dates from 01-01-2000 to 01-01-2100.
Date format MM/DD/YYYY
Min = 01-01-2000 - pass
Max = 01-01-2100 - pass
Min - 1 = 12-31-1999 - fail
Max -1 = 12-31-2099 - pass
Min+1 = 01-02-2000 - Pass
Max +1 =01-02-2100 - fail
Equivalence Class Partition:

ECP defines the types of the data which we need to use to
perform testing on the application. If any requirement is having
the type of the data we need to prepare the ECP for that
requirement and based on the ECP only we design the test cases.
They are two different classes available.
1. Valid
TARAKESH
Page 28
TARAKESH
TESTING TOOLS
2. Invalid
Ex:
1. UID Should accept only alphabets.
Valid
a-z
A-Z
a-z, A-Z
Invalid
0-9
Special characters : @
Spaces
2. Password should accept only alpha numeric

Valid
(a-z),(0-9)
(A-Z), (0-9)
(a-z),(A-Z),(0-9)
Invalid
(a-z)
A-Z
Special characters &...Spaces
Error Guessing:
It defines the error which we are expecting from the application
as per action we performed it.
Ex:
1. BRS 1.1 - User can successfully register by entering name,
address, city and click on register button.
S.N
o
BRS
Rule/Condition
Author
Date
All the fields are

mandatory except city and
Error message should
appear if the customer
missed the mandatory
field.
"Field should not be
empty"
S.N
o
Action
TARAKESH
Error
Page 29
TARAKESH
TESTING TOOLS
1.
2.
3.
Fill all the fields and click

on register
Enter Name, Address &
Click on Register
Enter name and City then
click on Register
No Error
No Error
Address field
should be filled
Test Case Template:

A Template or a format which we use to design the test case is
called Test case template.
In Every Project we design the test case in excel sheet based on
the requirement of the client.
They are three different types.
1. Standard template
2.Test Case Template without Test management tool
3. Test case Template with Test management tool
1. Standard template
In this template we design all the test cases and also we execute
the test cases in single excel sheet.
S.No
BRS
Test
nam
e
Step
No
Descript Expec
ion
ted
Result
Actu
al
Resu
lt
Stat
us
Comme
nts
S.No: It defines the test case number.

BRS:
It defines the requirement information that means for which
requirement we design the test case. We need to specify the
requirement information in this BRS column.
Test Name:
It defines the name of the test case.
TARAKESH
Page 30
TARAKESH
TESTING TOOLS
Step No:
It defines the step number of the test case.
Note: Every test case should contains minimum of one step and
max. will be unlimited that depends on the requirement.
Description:
It defines the activity or action going to perform on the
application. In simple words description is "What we are going to
do on the application"
EX:
1. Enter UID, Enter Password.
2. Click on ok button.
3. Launch the application.
4. Close the application.
5. Select the check box.
6. Select the value in list box.
7. Verify button.
8. Verify application.
Expected result:
It defines what we are expecting from the application as per
the client requirement after performing the action on the
application .In simple words Expected result is "The client
requirement in application"
EX:
1. Button should be enable.
2. Edit box should be focussed.
3. Link should be available.
Actual result:
TARAKESH
Page 31
TARAKESH
TESTING TOOLS
It defines What actually application is showing after performing
the activity (or) action. in simple words actual result is "what
developer has developed in the application"
EX:
1. Button is enabled.
2. Edit box is focussed.
3. Link is disabled.
4. Check box is selected.
5. Application has closed.
Status:
It defines the status of the test step. The status of the step
is pass if the expected result is same as the actual result and the
status of the step will be fail If the expected result is
mismatching with actual result.
Comments:
It defines the comments of the test step.
Test case template without using test management tool:
This template is suitable for the projects in which we are not
using any one of the test management tool like QC, bugzilla,
etc...In this template we are designing one test case in one sheet
and also executing The test cases From excel sheet.
Step No BRS
Descript Expecte
ion
d
Result
Actual
Result
Status
Comme
nts
Test case template with using test management tool:

This template is suitable for the projects in which we are using
any one of the test management tools like QC, Bugzilla, .... In this
TARAKESH
Page 32
TARAKESH
TESTING TOOLS
template we are designing one test case in one excel sheet and
after that exporting The test cases into test management tool
and execute test case from test management tool.
Step No
BRS
Description
Expected
result
Note:
While designing the test cases we are designing only up to
Expected result (ER).Actual result(AR),Status will be providing
only during Execution time.
EX:
1. Valid User can successful login to Gmail application by entering
UID, PWD and click on sign in.
Ste BRS
p
No
1
BRS1.1
Req 1
BRS1.1
2
Req1
BRS1.1
Req1
Description
Expected result
Launch Gmail
Application
Gmail application
should be
launched
Verify UID
PWD, Sign in
Enter valid
UID, PWD
and click on
Sign in
AR
Stat
us
Com
men
t
UID,PWD. Sign in
Should be
available
User should be
able to login to
Gmail application
2 . Valid user can successfully register by entering name,

address, city, State and click on register button in registration
application.
Description
TARAKESH
Expected result
Page 33
TARAKESH
TESTING TOOLS
Launch registration
application
registration application should

be launched
verify name, address, city,

state,
and register.
Name, address, city, state,

register should be available.
Enter valid name ,address,

city, state and click on
register
Valid user should be able to

register in registration
application
3. Valid user can successfully register by entering name, address,

city, and click on save in Gmail application
FRS Document
S
NO
1
BRS
Rule/Condition
BRS1.1
Reg 3
BRS1.1
Reg3
Name should be text box and should accept only

6-10 characters .
And below error msg should appear when BVA
fail. "and name should accept only 6-10
characters"
Address should be text box & should accept only
5-15 character &
Error msg should appear
"Address should accept 5-15 characters.
BVA for name: (Range 6-10)

min =6
pass
max=10
pass
min-1=5
-fail
max-1=9
-pass
TARAKESH
Page 34
TARAKESH
TESTING TOOLS
min+1=7 - pass
max+1=11-fail
BVA for name:
Description
Launch abc application.
verify name.
verify type of name.
enter name as 6 character
&and click on Enter.
Enter name as 10 character
and click on enter.
Enter name as 5 character ,
click on enter.
click on enter.
click on enter.
click on enter.
Expected result
Abc application should be
launched.
Name should be available.
Name should be a text box
Error message should not
appear.
appear.
Name should accept 6-10
character.
appear.
appear.
Name should accept 6-10
character.
BVA for address:

min=5
-pass
max=15 - pass
min-1=4
-fail
max-1=14
-pass
min+1=6
- pass
max+1=16
-fail
abc-address-BVA
TARAKESH
Page 35
TARAKESH
TESTING TOOLS
Description
Launch abc application
verify address
verify type of address
enter address as 5 character ,
click on enter.
Enter address 15 character ,
click on enter
enter address as 4 character
click on enter
Enter address as 14 character
click on enter
Enter address as 6
character ,click on enter
Enter address as 16 character
,click on enter
Expected result
launched
Address should be available.
Address should be text box.
Error massage should not
appear.
appear.
Address should accept 5-15
character
appear.
appear.
Address should accept 5-15
character
4. Valid User can successfully register by entering name, address,

city and click on save in ABC application.
FRS Document
S.No
1.
BRS
BRS 1.2
Req 4
2.
BRS 1.2
Req 4
TARAKESH
Rule/Condition
Name should accept
only alphabets and
below error message
should appear if ECP
fails.
"Name should
accept only
alphabets"
Address should
accept only alpha
numeric's and below
Page 36
TARAKESH
TESTING TOOLS
error message
should appear if ECP
fails.
"Address should
accept only alpha
numeric"
Ex: ECP for Name
Valid
(a-z)
(A-Z)
a-z, A-Z
ECP for Address:
Invalid
(0-9)
Special Characters
Spaces
Valid
(a-z),(0-9)
(A-Z),(0-9)
a-z,A-Z,0-9
Invalid
a-z
A-Z
0-9, Special characters, Spaces
Test Case for Valid ECP or Name:

abc-name-Ecp-valid
Description
launch abc application.
Verify name
Verify type of name
Enter name as (a-z)
Click on enter
Enter name as (A-Z)
Click on enter
Enter name as (a-z),(A-Z)
Click on enter
Expected Result
Application should be launched
Name should be available
Name should be text box
appear
appear
appear
Test case for invalid Ecp for name:

abc-name-Ecp-invalid
Description
Verify name
Verify type of name
Enter name as (0-9)&click on
enter
TARAKESH
Expected result
launched
Name shiuld be available
Name should be text box
Name should be alphabet
Page 37
TARAKESH
TESTING TOOLS
Enter name as special character
&click on enter
Enter name as space &click on
name & click on enter

Test case for valid Ecp for address:

abc-Address-Ecp-invalid
Valid
(a-z),(0-9)
(A-Z),(0-9)
a-z,A-Z,0-9
********************
Invalid
a-z
A-Z
0-9, Special characters, Spaces
Description
Expected result
launched
Address should be available
Address should be text box
appear
appear
appear
Verify address
Verify type of address
Enter address as (a-z) , (0-9) &
click on enter
Enter address as (A-Z ),(0-9) &
click on enter
Enter address as (a-z),(A-Z),(09) & click on enter
Test case for invalid Ecp for Address

abc-address-Ecp-invalid
Description
Verify address
Verify type of address
Enter address as (a-z) & click
on enter
TARAKESH
Expected result
launched
Address should be available
Address should be text box
Address should be accept
alphabet
Page 38
TARAKESH
TESTING TOOLS
Enter address as
on enter
Enter address as
on enter
Enter address as
character & click
(A-Z) & click

(0-9) & click
Special
on enter.

alphabet
alphabet
alphabet
5. Save and submit button will be disabled when user enter name
and address .
save button will be enabled where user select city
submit button will be in enabled &in focused when user select
the state
application will automatically closed when user click save &
submit button in registration application .
Description
Launch registration application
Verify name
,address,city,state,save and
submit
Enter name , enter address
Select city
Select state
Click on save
Click on submit
TARAKESH
Expected result
Registration application should
be launched
Verify name
,address,city,state,save and
submit are available
save and submit button should
be available
Save button should be enabled
Submit button should be
enabled and focused
Registration application should
be closed
Page 39
TARAKESH
TESTING TOOLS
6.Register button will be in Disabled when user enter name and
address
and it will be enabled when the user select the City and State
and it will be focussed when user enters phone number and
salary in abc application
and abc application will close and confirm abc application launch
when user clicks on registration
Ok and done buttons will be enabled when user enter PAN CRAD
no
and done button will be in focus when the user enters Date of
birth
and confirm,
abc application is automatically closed when user click on ok and
done buttons.
Description
Verify Name, Address, City,
State, Phone number, Salary
register fields.
Enter Name
Enter Address
Select City
Select State
Enter phone number
Enter Salary
Click on Register button
Verify OK, done, PANCARD

DOB
Enter Pan card number
Click on ok
Click on done
TARAKESH
Expected Result
launched
Name, Address, City, State,
Phone number, Salary register
fields are available.
Register button should be
disabled
disabled
focussed
Abc application should close
and confirm abc application
should be launched
OK, Done, PANCARD NO,DOB
should be available.
Ok & Done button should be
enable, done button should be
focussed
Confirm abc application should
be automatically closed.
Page 40
TARAKESH
TESTING TOOLS
7 (a). Valid user can successfully login to enrolment application
and navigates to case search screen by entering UID PWD and
click on sign in button in enrolment application.
(b). user can successfully search for the case by entering test
case ID and click on search button and user navigates to SSN
(social security number ) inform screen when click on next
button.
(c). User can able to see 100 SSN numbers and every SSN
number starts with 7 and user navigates to personal information
screen when click on first SSN number and user can able to
name , address , city, state, salary department and user can
navigates to product screen when click on next button.
Description
Launching enrolment.
Verify UID ,PWD ,sign in
Enter valid UID
Enter valid PWD
Click on sign in
Verify case search screen
Expected result
Enrolment application should be
launched.
UID , PWD, sign in should be
available
Valid user can successfully
login to enrolment application
Valid user should navigates to

case search
Verify case ID , search next.
Case ID, search, next should be
available.
Enter case ID
User should successfully search
Click on search
for the case.
Click on next.
User should navigates to SSN
information
Verify SSN information.
User should able to see 100 SSN
number.
Verify every SSN number.
Every SSN number should start
with 7
Click first SSN number.
User should navigate to
personal information screen.
Verify Name address , city, sate, Name , address, city, state ,
salary department
salary department should be
available.
Click on next.
User should navigates to
product screen.
TARAKESH
Page 41
TARAKESH
TESTING TOOLS
8.(a)user can able to see 5 product along with apply button in
product screen and user navigates to pre rating question screen
when click on apply button for first product.
(b)user can able to see 2 questions along with yes or no radio
button and user navigates to medical question screen after
selecting both the questions as yes and click on next button.
(c)user can able to see 5 questions along with yes and no radio
buttons and user navigates to coverage screen when click on next
button after selecting all the questions as NO
NOTE:
when we are writing the test case from the middle of the
application instead of launching the application again we specify
pre-condition in test case.
pre-condition:
a condition which should be satisfied in the application before executing
the test case is called pre-condition.
Description
Pre-condition:
User should login to
enrolment application and
navigates to product screen
Verify product screen
Expected result
Click on apply button

Verify pre rating question screen
verify next button
Verify next button select both
question as yes. and click on next
Verify medical question screen
Select all the questions as no , click
on next
Product screen should contain

5products along with apply button.
User should navigate to pre rating
question screen
User should able to see 2 question
along with yes and no radio button
next button should be available
User should navigates to medical
question screen
User should able to see 5 question
along with YES & NO radio button
User should navigate to coverage
screen.
9. coverage screen contains 3 fields employee , spouse , Child

coverage.
TARAKESH
Page 42
TARAKESH
TESTING TOOLS
EE coverage -20 values ,(100000-200000) min and max 10000
intervals ,10 %
Spouse coverage -20,(50000-100000), 5000 , 10 or 8%
Child coverage -10, (2000-10000),2000,10 or 2%.
Description
Pre-condition:
User should login to
enrolment application and
navigates to coverage screen
Verify coverage screen
Expected result
Coverage screen should contain

3 fields namely EE coverage,
spouse coverage, Child
coverage.
Verify EE coverage
EE coverage should contain 20
values.
Verify minimum& maximum
Min and max values should be
values of EE coverage.
(100000-200000)
Verify the interval between the
Intervals between the values
values of EE coverage
should be (10000)
Select EE coverage
EE premium text box should be
available
Verify EE premium Text box
EE premium text box should
contain 10% of selected
employee coverage
Verify sp coverage screen
SP coverage screen should
contain 20 values
Verify min and max values of sp Min and max values should be
coverage
(5000-100000)
Verify the interval between the
Interval between the values
values
should be 500
Select special coverage
Special premium text box
should be available
Verify special premium text box Special premium text box
should contain 8% of the
selected spouse coverage
Verify Child coverage screen
Child coverage screen should
contain 5 values
Verify min and max values Child Min & max values should be
coverage
(2000-10000)
Verify the intervals between the Interval between the value
values
should be 2000
TARAKESH
Page 43
TARAKESH
TESTING TOOLS
Verify Child coverage
Verify Child premium text box

Verify total premium text box
Verify done button
Click on done button
Child premium text box should

be available and total premium
should appear
Premium text box should
contain 200 every time
Total premium text box should
be sum of EE, SP, Child premium
Done button should be
available
User should navigate to product
screen on enrolment application
Test cases for Fresher's:

The following type of test cases are mandatory for fresher's.
The main intention of asking these questions is to check the
analytical skills of the candidate. When we face these type of
questions we need to consider below 3 conditions
1. Think about the product for some time
2.Start working the test cases for mandatory functionalities
3. write max.no of test cases.
Ex:
1. Prepare the test cases for ceiling fan?
2.Prepare the test cases for chair?
3.Prepare the test cases for Pen?
4.Prepare test cases for lift?
5.Prepare a test case for sending SMS from mobile?
6.ATM
************************
6.Test data Preparation:
During this phase, Testing team will be involving to design the
test data, which is required to perform testing on the application.
TARAKESH
Page 44
TARAKESH
TESTING TOOLS
we design the test data in excel sheet based on the test cases
and usually we design multiple sets of test data.
**********************
Software Testing Life Cycle:

Requirement Analysis: During this phase, test team studies the requirements
from a testing point of view to identify the testable requirements. The QA team
may interact with various stakeholders (Client, Business Analyst, and technical
Leads, system Architects etc) to understand the requirements in detail.
Requirements could be either Functional (defining what the software must do) or
Non Functional (defining system performance /security availability) .Automation
feasibility for the given testing project is also done in this stage.
Activities:
Identify types of tests to be performed.
Gather details about testing priorities and focus.
Prepare Requirement Traceability Matrix (RTM).
Identify test environment details where testing is supposed to be carried out.
Deliverables:
RTM
Test Planning: This phase is also called Test Strategy phase. Typically, in this
stage, a Senior QA manager will determine effort and cost estimates for the
project and would prepare and finalize the Test Plan.
Activities:
Preparation of test plan/strategy document for various types of testing
Test tool selection
Test effort estimation
Resource planning and determining roles and responsibilities.
Training requirement
TARAKESH
Page 45
TARAKESH
TESTING TOOLS
Deliverables:
Test plan /strategy document.
Effort estimation document.
Test case Development: This phase involves creation, verification and rework
of test cases & test scripts. Test data , is identified/created and is reviewed and
then reworked as well.
Activities:
Create test cases, automation scripts (if applicable)
Review and baseline test cases and scripts
Create test data (If Test Environment is available)
Deliverables:
Test cases/scripts
Test data
Test Environment Setup: Test environment decides the software and

hardware conditions under which a work product is tested. Test environment setup is one of the critical aspects of testing process and can be done in parallel
with Test Case Development Stage. Test team may not be involved in this
activity if the customer/development team provides the test environment in
which case the test team is required to do a readiness check (smoke testing) of
the given environment.
Activities:
Understand the required architecture, environment set-up and prepare hardware

and software requirement list for the Test Environment.
Setup test Environment and test data
Perform smoke test on the build
Deliverables:
Environment ready with test data set up

Smoke Test Results.
Test Execution: During this phase test team will carry out the testing based on
the test plans and the test cases prepared. Bugs will be reported back to the
development team for correction and retesting will be performed.
Activities:
Execute tests as per plan
TARAKESH
Page 46
TARAKESH
TESTING TOOLS
Document test results, and log defects for failed cases
Map defects to test cases in RTM
Retest the defect fixes
Track the defects to closure
Deliverables:
Completed RTM with execution status
Test cases updated with results
Defect reports
Test Cycle Closure: Testing team will meet, discuss and analyze testing
artifacts to identify strategies that have to be implemented in future, taking
lessons from the current test cycle. The idea is to remove the process
bottlenecks for future test cycles and share best practices for any similar
projects in future.
Activities:
TARAKESH
Page 47
TARAKESH
TESTING TOOLS
Evaluate cycle completion criteria based on Time, Test coverage, Cost, Software,
Critical Business Objectives , Quality
Prepare test metrics based on the above parameters.
***********************************************
Traceability or Cross Reference Matrix:
Whenever requirements are added or modified in the application there is a

need to change the test cases. If the test case sheet is very large it will be very
difficult to find the test cases affected by that change. Instead if the
requirements are numbered and referenced in the test case sheet it would be
very easy to track the test cases that were affected. It is nothing but the
traceability.
Traceability matrix links the business requirement matrix with the

corresponding functional requirements and the test cases.
Traceability matrix is nothing but a document which contains a table of linking
information used for tracking back for the reference in any kind of confused or
questionable situations.
If a test case fails it helps determine the corresponding functionality easily. It
also helps to ensure that all the requirements are tested.
Defects: While executing the test cases we find the actual results vary with
expected results. This is nothing but a defect also called as bug, incident,
problem or issue.
TARAKESH
Page 48
TARAKESH
TESTING TOOLS
Defect Report: To convey the information of the defects found during testing to
the development team testers prepare defect report. To make the developer
understand the defect the following should be documented in a defect report:
Defect Id: Unique identification for the defect
Defect Description: Detailed description of the defect including information

about the module in which defect was found.
Version: Version of the application in which defect was found
Steps: Detailed steps along with the screenshots with which the developer can
reproduce the defect.
Date Raised: Date when the defect is raised
Reference: Provide reference to the documents referenced, i.e. requirements,

design, architecture etc
Detected By: Name/Id of the tester who raised the defect
Status: Status of the defect
Fixed by: Name/Id of the developer who fixed it.
TARAKESH
Page 49
TARAKESH
TESTING TOOLS
Date Closed: Date when the defect is closed
Severity: describes the impact of the defect on the application
Priority: is related to defect fixing urgency
Severity and Priority of defect: Severity is nothing but the seriousness of the
defect. Severity could be high, medium, low depending on the impact of the
defect on the application. Based on the severity defects are classified as Fata,
Major, Minor defects.
Fatal defects: Defects related to navigation blocks of the application or which

makes the main functionality unavailable are called fatal defects.
Ex: login button missing
Major defects: Defects which points the incorrect functionality or defects which
are because of incorrect functionality are called major defects.
Minor defects: Defects which are related to the look and feel of the application
are called minor defects.
Priority of the defects: Priority is nothing but the order in which the defects
should be resolved or fixed.
Priority is classified into 4 types:
TARAKESH
Page 50
TARAKESH
TESTING TOOLS
Critical, High, Medium, Low
Usually based on the severity priority will be given to the defects. But depending
on the situations the priority will be changed by the development lead.
Least Severity and Highest Priority: Cosmetic defects are generally given
least severity but during customer visits it will be given highest priority
Highest Severity and Least Priority: If some part of the application is still
under development and not released to the testing department testers will
assign fatal but it will be
**********************************************************************
Defect Life Cycle: From the point of indentifying a defect till the defect is closed
the defect goes through different stages in a life cycle called defect life cycle.
Suppose the tester finds the defect is assigned status new. Development team
analyses the defect whether it is a valid defect or not. Consider the flight
reservation application. Defects due to corrupted test data, misconfigurations in
test environments and defects with invalid expected results are assigned a
status Rejected.
IF it is not rejected then it is checked whether it is in scope or not. Defects

which are out of scope of the current project is assigned a status deffered.
Then the development team checks whether the defect is raised earlier. If yes
the defect is assigned a status Duplicate. If it is not a duplicate defect the
development team starts fixing the defect. During that stage the defect is
assigned a status in progress. Once code is fixed the defect is assigned a status
fixed. Then the tester retests the code .In case the test case passes the defect
TARAKESH
Page 51
TARAKESH
TESTING TOOLS
is closed. If the test case fails the defect is Re-opened and again assigned to
developer. Sometimes a closed defect will be re-opened.
New: Whenever the defect is identified for the first time then the test engineer
will set the status as new.
Open: Whenever the developer accepts the defect then he will set the status as
open.
Fixed: Whenever the developer rectifies the defect before releasing the next
build he will set the status as fixed.
Reopen & Closed: Whenever the next build is released, the test engineers will
check whether the defects are properly rectified or not. If at all the defect is
properly rectified then the defect is assigned a status closed. Otherwise it is
reopened.
Hold: Whenever the developer is not sure to accept or reject the defect, he will
set the status as Hold
Rejected: Invalid defects are assigned a status rejected.

************************************************7
Configuration Management: Configuration management (CM) is the

detailed recording and updating of information that describes an enterprise's
computer systems and networks, including all hardware and software
components
Such information typically includes the versions and updates that have
been applied to installed software packages and the locations and network
addresses of hardware devices. Special configuration management software is
available. When a system needs hardware or software upgrade, a computer
technician can accesses the configuration management program and database to
TARAKESH
Page 52
TARAKESH
TESTING TOOLS
see what is currently installed. The technician can then make a more informed
decision about the upgrade needed.
An advantage of a configuration management application is that the entire
collection of systems can be reviewed to make sure any changes made to one
system do not adversely affect any of the other systems Configuration
management is also used in software development. Using CM, developers can
keep track of the source code, documentation, problems, changes requested,
and changes made.
Visual Source Safe(VSS) : VSS is a Configuration Management tool. It is

used throughout the life cycle. The purpose of this tool is identifying the
configurable items in the project. Keep those in repository and maintain version
controlling.
Source Control Systems are software that is used to track changes to
source code files and also to safely store source code.
Keep backup of your source code or documents.
Maintain all versions of your files so that you can retrieve any of the old
versions of the file easily without searching all over your hard drive.
Track which person changed what and when.
Control who changes the file to avoid more than one person changing the
file at the same time.
At any point of time, any of the team members can get the latest
version of all files from one single location, without the need to ask each
member for the latest files.
Track progress - project manager or team leader can monitor the file
change activity in source control systems to find out how much work each
person has done on each day.
Check-in: When any person creates a new file in the project, he will add it to
the Source Control System in the corresponding to folder. This process is called
"Check in".
Most of the source control systems provide a windows explorer like user
interface. You can check in files in different ways:
Drag and drop files from windows explorer to appropriate folder in source
control explorer.
Go to appropriate folder in source control system, right click on the folder

name and select 'Add Files'. This will launch a file browser which will allow you to
select files.
TARAKESH
Page 53
TARAKESH
TESTING TOOLS
After you add (check in) a file to source control, the file is "controlled" by
source control system. If anybody want to change the file (including the person
who created the file), he has to check out the file from the source control
system.
Check out Process:
If you want to edit a file that is checked in to source control, you must go
to source control system and "checkout" the file. All you have to do is, right click
on appropriate file in the source control explorer and select "Checkout File". The
source control system will remember the folder structure you specified and copy
the latest version of the file to the appropriate folder.
When you checkout a file from Source Control, it will copy the latest
version of that file into your computer. This will overwrite your copy of that file.
So, if you have made any changes to the file in your computer without checking
out, those changes will be lost
Advantage of source control system:
One of the primary advantages of using a source control system is

maintaining versions and tracking changes.
Every time you check in a file to the source control, it will create a new
version of the file. If you right click on any file and select 'View History', it will
display all versions numbers of the file and also show details like who checked in
that version and when was it checked in. You can select any of the versions in
the history and view that version of that file. This will help you to easily revert to
an old version of the file if you find that the old version was working better than
the new version. Also, you can select any 2 versions in the history and
'compare'. This will display the difference between those 2 versions. Depending
on the source control software, it will display line by line comparison results. This
will help you to easily find which member of the team made what change to the
file in each version. So you cannot escape saying 'I am not the person who made
that stupid change!
9.Test case execution in UAT environment:

During this phase ,testing team along with the client will be
involving to perform testing on the application by executing the
test cases . during this phase , we are performing different
types of testing like sanity testing , usability testing , functional
testing, etc......
10.Defects:
TARAKESH
Page 54
TARAKESH
TESTING TOOLS
during this phase , testing team will be involving to report the
new defects and also performing re-testing on the migrated
defects . if the migrated defects working properly we need to
close the defects.
after successfully completion of executing all the test cases
and when all the defects are closed in UAT environment we
perform the regression testing.
11.Regression testing :
During this phase ,testing team will be involving to perform
regression testing to verify whether the closed defects are
impacting on the related functionality of the application or not
that is the reason we are executing again all the failed test
cases during this regression testing.
Regression test cases:

A test case which has failed during execution time is called
regression test case.
Regression defect:
A defect has been identified during performing testing is called
regression defect .
NOTE:
regression defect is not a standalone defect and it is the
impacted defect of the another defect.
Regression suit:
Collection of multiple regression test cases is called regression
suit. usually we are performing regression testing by executing
regression suit only .
TARAKESH
Page 55
TARAKESH
TESTING TOOLS
12.Test closure:
During this phase ,project manager will be involving to sign-off
the testing activities and development team will be involving to
deploy the application into production environment . project
manager will sign-off the testing activities only when we
executed all the test cases &all the defects are closed and
regression testing should be completed . some time , project
manager will sign off the test case even though some defects
are in open status . but those open status defects should not be
critical defects in projects .
What is a Defect Life Cycle or a Bug lifecycle in

software testing?
Defect life cycle is a cycle which a defect goes through during its lifetime. It starts when defect is
found and ends when a defect is closed, after ensuring its not reproduced. Defect life cycle is related
to the bug found during testing.
TARAKESH
Page 56
TARAKESH
TESTING TOOLS
The bug has different states in the Life Cycle. The Life cycle of the bug can be shown
diagrammatically as follows:
Bug or defect life cycle includes following steps or status:

1.
New: When a defect is logged and posted for the first time. Its state is given as new.
2.
Assigned: After the tester has posted the bug, the lead of the tester approves that the bug is
genuine and he assigns the bug to corresponding developer and the developer team. Its state
given as assigned.
3.
Open: At this state the developer has started analyzing and working on the defect fix.
4.
Fixed: When developer makes necessary code changes and verifies the changes then
he/she can make bug status as Fixed and the bug is passed to testing team.
5.
Pending retest: After fixing the defect the developer has given that particular code for
retesting to the tester. Here the testing is pending on the testers end. Hence its status is pending
retest.
6.
Retest: At this stage the tester do the retesting of the changed code which developer has
given to him to check whether the defect got fixed or not.
7.
Verified: The tester tests the bug again after it got fixed by the developer. If the bug is not
present in the software, he approves that the bug is fixed and changes the status to verified.
8.
Reopen: If the bug still exists even after the bug is fixed by the developer, the tester changes
the status to reopened. The bug goes through the life cycle once again.
TARAKESH
Page 57
TARAKESH
TESTING TOOLS
9.
Closed: Once the bug is fixed, it is tested by the tester. If the tester feels that the bug no
longer exists in the software, he changes the status of the bug to closed. This state means that
the bug is fixed, tested and approved.
10.
Duplicate: If the bug is repeated twice or the two bugs mention the same concept of the bug,
then one bug status is changed to duplicate.
11.
Rejected: If the developer feels that the bug is not genuine, he rejects the bug. Then the
state of the bug is changed to rejected.
12.
Deferred: The bug, changed to deferred state means the bug is expected to be fixed in next
releases. The reasons for changing the bug to this state have many factors. Some of them are
priority of the bug may be low, lack of time for the release or the bug may not have major effect
on the software.
13.
Not a bug: The state given as Not a bug if there is no change in the functionality of the
application. For an example: If customer asks for some change in the look and field of the
application like change of colour of some text then it is not a bug but just some change in the
looks of the application.
TARAKESH
Page 58

Testing Material

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Testing Material

Загружено:

Авторское право:

Доступные форматы

TARAKESH

Different types of teams in project :

1.Development is respective to the

1.Testing is irrespective of the

2.More technical knowledge is

3.Technology might be changing

3.Verifying whether clutch is

Performing testing on application in different browsers like Internet

1. KT( Knowledge Transfer):

Rules and Conditions

Logo size should be

Acquisition and Installation of Hardware and Software

How to execute the package?

How to enter the data?

How to process the data (processing details)?

How to take out the reports?

The operational work is doubled.

User or Operator Documentation

The review of the system is done for:

Agile software development stresses rapid iterations, small and frequent

Advantages of Agile model:

Customer satisfaction by rapid, continuous delivery of useful software.

Working software is delivered frequently (weeks rather than months).

Face-to-face conversation is the best form of communication.

Close, daily cooperation between business people and developers.

Continuous attention to technical excellence and good design.

Regular adaptation to changing circumstances.

Even late changes in requirements are welcomed

Disadvantages of Agile model:

beginning of the software development life cycle.

When to use Agile model:

Test Case Design:

2. Password should accept only (5-10) characters

Equivalence Class Partition:

2. Password should accept only alpha numeric

All the fields are

Fill all the fields and click

Test Case Template:

S.No: It defines the test case number.

Test case template with using test management tool:

2 . Valid user can successfully register by entering name,

registration application should

verify name, address, city,

Name, address, city, state,

Enter valid name ,address,

Valid user should be able to

3. Valid user can successfully register by entering name, address,

Name should be text box and should accept only

BVA for name: (Range 6-10)

BVA for address:

4. Valid User can successfully register by entering name, address,

Test Case for Valid ECP or Name:

Test case for invalid Ecp for name:

Name should be alphabet

Test case for valid Ecp for address:

Test case for invalid Ecp for Address

(A-Z) & click

Address should be accept

Verify OK, done, PANCARD

Valid user should navigates to

Click on apply button

Product screen should contain

9. coverage screen contains 3 fields employee , spouse , Child

Coverage screen should contain