Unit -III

1 Test Planning:

 The goal of software tester is to find bugs, find them as early as

possible & make sure that they get fixed.

 To achieve this goal through properly communicated & documented

the test effort with well-constructed test plan, test cases & test
reports.

 A Software Test Plan is a document describing the testing scope and

activities. It is the basis for formally testing any software/product in a
project.

 It identifies of test items, which features of application to be tested,

the different testing tasks, who will perform the respective task &
Following are the major activity done as a part of
test planning:

 Preparing a Test Plan

 Scope Management

 Deciding Test Approach

 Setting Up Criteria for Testing

 Identifying the Responsibility

 Staffing & Training

 Resource Requirement

 Test Deliverables
1)Preparing a Test Plan:
Writing test plan is one of the primary tasks in testing.
While writing a test plan, you specify the scope & objectives for the
testing are specified. It usually includes Scope, Methodology,
Requirements, and Criteria for Pass- Fail & Schedule.

-What needs to be tested & How the testing is going to be

performed
-What resources are needed for testing

Test Plan Types: One can have the following types of test plans:
Master Test Plan: A single high-level test plan for a project/product that
unifies all other test plans

Testing Level Specific Test Plans: Plans for each level of testing
2) Scope Management:
 With the help of scope management we can avoid the continuously growing
scope projects along with list of requirements.

 In the project scope we usually define, what is included, what is not included in
the project/system.

Scope Management Includes:

 Objective & requirement of the project.

 Breaking down the release into features & Risk, constraints.

 Giving priority to the feature of testing.

 Deciding which features will be tested & which will not be.
3) Deciding Test Approach:

The choice of test approaches or test strategy is one of the most

powerful factor in the success of the test effort and the accuracy of the
test plans and estimates. This factor is under the control of the testers
and test le aders.

Following are the major types of test strategies that are

commonly found:

--Analytical: The risk-based strategy involves performing a risk analysis

using project documents and stakeholder input, then planning,
estimating, designing, and prioritizing the tests based on risk.

--Model-Based: During requirement & design phase of project, some

formal & informal models are created. If the result of SUT (System under
test) is equal to the result of model then it is concluded that system is
Methodical: You might have a checklist that you have put together over
the years that suggests the major areas of testing to run or you might
follow an industry-standard for software quality, such as ISO 9126, for
your outline of major test areas.
Dynamic: Dynamic strategies, such as exploratory testing, have in
common concentrating on finding as many defects as possible during test
execution and adapting to the realities of the system under test as it is
when delivered.

Process-or Standard Compliant: You might adopt the IEEE 829 standard
for your testing
4) Setting Up Criteria for Testing:
This section depicts the number of criteria including Test
to Pass or Fail, When to suspend testing process or when
to resume. This gives the clear understanding to testers
while performing testing of applications.

--Pass or Fail Criteria: Specify the criteria that will be used

to determine whether each test item has passed or failed
testing.

--Suspend Criteria: Specify the criteria, to be used to

suspend the testing activity.

--Resume: Criteria: Specify testing activity which must be

5) Identifying the Responsibility:

 A testing project requires different people to play different roles. There are roles of test
engineers, test leads and test managers.

 There is also role definition on the dimensions of the modules being tested or the type of
testing. These different roles should complement each other. The different role definition
should.

 Ensure there is clear accountability for a given task, so that each person knows what he
or she has to do.

 Clearly list the responsibilities for various functions to various people, so that everyone
knows how his or her work fits into the entire project.

 Complement each other, ensuring no one steps on an others" toes.

 Supplement each other, so that no task is left unassigned

6) Staffing & Training Needs:
Specific training & staffing needs are essential to deliver the
acceptance of designed test plan. These need communicate the
resource requirements & get the approval for these resources. It wills
surely the delivery of test plan.

Training: Product tanning is provided to test analysts on the

application or system.

Staffing Needs: At first provide the information about the test team
size & number of resources required to be delivered to them.
7) Resource Requirement:
 This is one of the important activities under the test planning. As a Test Manager, he/she
has to estimate the hardware, software, people requirement during the phase. It includes
the environmental need like support staff, office space.

Some of the resources required are as follows:

 Configuration include RAM, Processor, HDD, etc

 Supporting software & OS must be available

 Required Number of license copies of all software

 Supporting tools like configuration management tools, test data generators, compilers, etc

 Special Testing Tools for load test & Performance Test

8) Test Deliverables:
In the process of software application development, test teams prepare
different documents to improve communication among the team members
and other stakeholders.

These documents are also known as Test Deliverables, as they are

delivered to the client along with the final product of software application.
Different types of artifacts ex. Special type of documents are given to the
stakeholders of the S/W project during the SDLC.

There are various Test Deliverable are generated at every phase of

SDLC. Some of the Test Deliverables are provided before testing phase or
during testing phase or after testing cycle is over.

The different types of Test Deliverables are:

9) Testing Task:
First of all, identify the various tasks required to perform testing.

Then identify interdependencies among the different testing related tasks.

Work breakdown structure is useful in this case, which shows hierarchical

arrangement of task needed to complete project.

 Identify special skills required for testing.

 What is Test Management?
 The important part of Software Quality is the process of testing &
validating the software.

 Test management is the process of managing the tests. A test

management is also performed using tools to manage both types of tests,
automated and manual, that have been previously specified by a test
procedure.

 Generally Test Management allows different Teams to Plan, Develop,

execute & assess all testing activities.

 Traditional tools used for Test Management include:

 Word Processor
 Spreadsheets
 Choice of Standard:

• Standards are defined to provide exact meaning to any subject.

There are standards for every activity which is the part of SDLC.

• In Software Development & Testing field, standards are defined

& used for coding, testing, reviewing, designing & requirement
analysis phases.
•
• Mainly two types of Standards:
 External Standard
1.External Standard:
 These are the standards made by an entity external to an organization.
These standards can be treated as legal requirements for a Product.

 Test Plan must mention these standards for the adoption. There are three
types of External Standard:

Customer Standards: refer to something defined by the customer as per

his/her business requirement for the given product.

National Standard: refer to something defined by the regulatory entities of

the country where the supplier / customer reside.

International Standard: are defined at international level and these are

applicable to all customers across the globe. Like IEEE, ISO,
2)Internal Standards:
 These standards are developed by the software development
organizations for their Internal use purpose.

• In some cases these standards may be derived from some

national or international standards. Ex. Templates of Defect
Report, Test Plan, Test Cases, etc.
 Test Infrastructure Management

 IT Infrastructure Ecosystem includes Operating Systems platforms,

Computer Hardware platforms, Internet platforms, Data Management and
Storage & Enterprise Software Applications.

 Every software requires an infrastructure to perform its actions.

Infrastructure testing is the testing process that covers hardware, software,
and networks.

 The Testing Infrastructure consists of the testing activities, events, tasks

and processes that immediately support automated, as well as manual,
software testing.

 More stability, continuity & reliability are provided to the automated testing
 The Testing Infrastructure Includes
o Test Plan, Test Cases

o Baseline Test Data

o A process to refresh baseline data

o Dedicated Test Lab

o TC Database

o A way to prioritize, or rank, test cases per test cycle

o Defect Tacking Database & Risk Management Process

o Configuration Management Process

o Integration group & process

o Metrics to Measure Improvement

 Purpose of Testing Infrastructure:

• Allows to run automated TCP

• Provides a Test Environment to avoid conflicts between manual

& automated testing

• Helps to track the result of TC i.e. pass or fail

• Gives report of test coverage levels

• Keep expected result remain consistent across tests runs A

Test Lab to conduct multi-user & Stress Testing

 Components of Testing Infrastructure:
 Required Hardware Infrastructure:
This is the main component of Testing Infrastructure. Efficient, high
configuration as well as old configuration, dedicated infrastructure must available
for testing.

 Required Software Infrastructure:

This is another component of Testing Infrastructure. Latest as well as
previous software's should be available for testing.

 Required Automated Testing Tools Infrastructure:

Most Important, Different testing tools for different type of testing is
required to improve quality of software product.
 3. Test People Management:
• The importance of skilled testing has been proven during many software
projects. An application or product success is high just because of use of
efficient & effective testing techniques.

• It is commonly said that bugs/defects are found based on the skills &
knowledge of a tester & the dedication of the test teams. A test team is
formed of people with varying skills & experience levels.

• Also these team members come up with different expertise levels,

different attitudes & different expectations & interest level. So in order to
maximize quality, all these factor has to be integrated correctly & have to
bridge the skill gap if necessary.

• They need to work together, follow the applied test processes &
deliver the work within specified schedule. This generates the need for
test management which is perform by test lead
 Test Lead Skills:
• To lead team of tester with full efficiency. This is required to meet the product goal &
ultimately organization goal.

 Test Lead Responsibility:

• Identify how the test team are formed & aligned within an organization

• Decide the way through which roadmap for the project & organization can be

achieved

• Identify the scope of the testing using requirement document

• Create healthy environment for all resources to gain maximum throughput

• Identify skill gap present or not & Identify the tools required during testing
 Test Team Management:

Following are the set of activities required to manage

test team effectively:

o Initiate the test planning activities for test case design

o Encourage the team to conduct review meetings & incorporate

meeting comments

o Monitor test progress, check available resources & rebalance

or reallocate them as required

o Bridge any gaps between the testing team & the management
 Test Process:
Testing is not single activity. Instead it's a set of number of processes. It
starts with test planning then designing test case, execution & evaluation
& at the end test closer.

The Fundamental of Test Process is divided into following

steps:

 Test Planning & Control

 Test Analysis and Design

 Test implementation and execution

 Evaluating exit criteria and Reporting

 What we have to do in Test Process?

1)Base Lining a Test Plan:

It is one of the type of non-functional testing. which means it has

nothing to do with the testing of functionality of an application.
Rather testing of documents is done which create a solid
foundation of the work to be done in the future.

i.e. A baseline is a formal document that acts as a base document

for future work. Ex. for making a building, you require a base.

The same thing applies to test. We need to create a Baseline,

from which further testing is done
 2. Test Case Specification:

• Test Case Specification document described detailed

summary of what scenarios will be tested, how they
will be tested, how often they will be tested, and so on
for a given feature.

• It specifies the purpose of a specific test, identifies the

required inputs and expected results, provides step-
by-step procedures for executing the test, and outlines
the pass/fail criteria for determining acceptance.

• Test Case Specification has to be done separately for

each unit. Based on the approach specified in the test
 3. Update of Traceability Matrix:

• Requirement Traceability Matrix (RTM) is a document that maps

and traces user requirement with test cases.

• It captures all requirements proposed by the client and

requirement traceability in a single document, delivered at the

conclusion of the Software development life cycle.

• The main purpose of Requirement Traceability Matrix is to validate

 Test Reporting:
Once Testing is completed, tester generate metrics & make final reports on
their Test Effort & concluded weather or not the software Tested is ready for
release.

3.4.1: Recommending Product Release:

• One of the purpose of testing is to decide the fitness of a product for
release.

• It is said that testing can never conclusively prove the absence of defects
in a software product. Instead of that it provides an evidence of what kind
of defects in the product, their severity & impact.

• As we know the job of the testing team is to provide information about

testing result to the senior management & the product release team.
 Executing Test Cases:

• Test Cases which are prepared in earlier phase have to be executed at

appropriate time. For instance; on daily basis execute Smoke & Sanity

Tests Cases.*

• The term 'Smoke Testing' is came from the hardware testing; These

test cases are executed prior to start actual testing to check critical

functionalities of the program are working fine.

• 'Sanity Testing' is carry out to check whether the bugs reported in

 Test Execution has the following Major
Task:

• Follow Test Procedure to execute Test Suites & individual TC

• Comparison of actual & expected results

• In case of differences between the actual & expected result, defect

occurrences is reported

• During the execution of TC defect database must be updatedwith earlier

defects & newly founded defects.

• Do the confirmation of testing or retesting to re-execute the tests that

previously failed in order to confirm a fix
 3. Prepare Test Summary Report:

• Here is the typical Test Summary Report Template. Its contents may vary
based on each Company's format & practice.

 Step 1: Purpose of the Documents: It gives the short description about the
objectives behind preparation of the documents. Eg. Documents explaining
various activities performed as a part of Testing.

 Step 2: Overview of an Application: It gives brief description about the

application to be tested is mentioned.

 Step 3: Testing Scope: In Scope, Out of Scope, Items not TestedIn this
section it gives an explanation about the function/modules in scope & out of
scope for testing along with this, it also gives information about any item
Step 4: Metrics: In this section, it gives information about metrics. These metrics
will help to understand the Test Execution results, status of test cases & defects
etc.

Step 5: Types of Testing Performed: Smoke Testing, System Integration

Testing, Regression Testing.In this section, description about various types of
testing that is to be performed for the project is given. By doing this, one thing is
ensured that the application is being tested properly through testing types
agreed as per Test Strategy.

Step 6: Information of Test Environment Tools: In this section, details of

test environment in which the testing is carried out is given. It include
Step 7: Lesson Learned: This section describe the crucial
issue occurred & faced. Also gives detail solutions. This will help
to make protective decision during the next Testing Phase where
we can avoid these mistake.

Step 8: Recommendations: Suggestions about different

activities can be mentioned here

Step 9: Best Practices: As testing phase comprised of many

different phases, where some of them could have saved time,
some of them could be good & efficient etc. This information is
documented & presented to stake holders.

Step 10: Exit Criteria: It provides information about

Step 11. Conclusion/Sign off: In this section, exit criteria

for an application is set & checked to release it. Testing team

verifies the application against set criteria. If it is not met,

then decision about its release is taken by senior

management or stake holders.

Step 12: Definitions, Acronyms & Abbreviations: In

this, meaning of Abbreviated terms used in this documents &

any other new definitions are mentioned.

 4. Types of Test Report:
Once testing is completed, tester generate metrics & make final
report on their test efforts & concludes weather or not the
software tested is ready for the release. Test Reporting is a
meaning of archiving this communication. There are two types of
reports:
a) Test Incident Reports b) Test Summary Report

a)Test incident report:

A test incident report is communication that happens
through the testing cycle as and when defects are
 b) Test cycle report:
A test cycle entails planning and running certain test in cycle, each
cycle using a different build of the product As the product
progresses through the various cycles it is expected to stabilize.
Test cycle report gives:

 A summary of the activities carried out during that cycle

 Defects that are uncovered during that cycle based on severity and impact

 Progress from the previous cycle to the current cycle in terms of defect fixed

 Outstanding defects that not yet to be fixed in cycle

 Any variation observed in effort or schedule