SOFTWARE TESTING METHODOLOGY UNIT-3

Test Management
Test Management is a process of managing the testing activities in order to ensure high quality
and high-end testing of the software application. The method consists of organizing, controlling,
ensuring traceability and visibility of the testing process in order to deliver the high quality
software application. It ensures that the software testing process runs as expected.

Test Management Process

Test Management Process is a procedure of managing the software testing activities from start
to the end. The test management process provides planning, controlling, tracking and monitoring
facilities throughout the whole project cycle. The process involves several activities like test
planning, designing and test execution. It gives an initial plan and discipline to the software testing
process.
There are two main Parts of Test Management Process: –

 Planning
1. Risk Analysis
2. Test Estimation
3. Test Planning
4. Test Organization
 Execution
1. Test Monitoring and Control
2. Issue Management
3. Test Report and Evaluation

PLANNING:
1.Risk Analysis: Risk is the potential loss (an undesirable outcome, however not necessarily so)
resulting from a given action or an activity.Risk Analysis is the first step which Test Manager
should consider before starting any project. Because all projects may contain risks, early risk
detection and identification of its solution will help Test Manager to avoid potential loss in the
future & save on project cost.

2.Test Estimation: An estimate is a forecast or prediction. Test Estimation is approximately

determining how long a task would take to complete. Estimating effort for the test is one of
the major and important tasks in Test Management.

3.Test Planning: A Test Plan can be defined as a document describing

the scope, approach, resources, and schedule of intended Testing activities. A project
may fail without a complete Test Plan. Test planning is particularly important in large software
system development. In software testing, a test plan gives detailed testing information regarding
an upcoming testing effort, including:

 Test Strategy
 Test Objective
 Exit /Suspension Criteria
 Resource Planning
 Test Deliverables

4.Test Organization: It is a procedure of defining roles in the testing process. It defines who is
responsible for which activities in testing process. Test functions, facilities and activities are also
explained in the same process. The competencies and knowledge of the people involved are also
defined however everyone is responsible for quality of testing process.
EXECUTION:
Test Execution refers to the execution of test cases of software applications to ensure they
meet the pre-defined requirements and specifications. In this case, it compares the intended
results with the actual results. The Test Execution phase is an essential part of the Software
Testing Life Cycle (STLC) and Software Development Life Cycle (SDLC). It begins with the
completion of the Test Planning phase.
1.Test Monitoring and Control: What will you do when your project runs out of
resource or exceeds the time schedule? You need to Monitor and Control Test activities to bring
it back on schedule. Test Monitoring and Control is the process of overseeing all the metrics
necessary to ensure that the project is running well, on schedule, and not out of budget.

Monitoring is a process of collecting, recording, and reporting information about the project
activity that the project manager and stakeholder needs to know

To Monitor, Test Manager does following activities

 Define the project goal, or project performance standard

  Observe the project performance, and compare between the actual and the planned
performance expectations
 Record and report any detected problem which happens to the project

Project Controlling is a process of using data from monitoring activity to bring actual
performance to planned performance. In this step, the Test Manager takes action to correct the
deviations from the plan. In some cases, the plan has to be adjusted according to project
situation.

2. Issue Management: As mentioned in the beginning of the topics, all projects may
have potential risk. When the risk happens, it becomes an issue. Risk to be avoided while testing:

 Missing the deadline

 Exceed the project budget
 Lose the customer trust

When these issues arise, you have to be ready to deal with them – or they can potentially affect the
project’s outcome.

3. Test Report and Evaluation: The project has already completed. It’s now time for look back
what you have done. “Test Evaluation Report” describes the results of the Testing in terms of Test
coverage and exit criteria. The data used in Test Evaluation are based on the test results data and
test result summary.

What is Test Coverage?

Test coverage is defined as a metric in Software Testing that measures the amount of testing
performed by a set of test. It will include gathering information about which parts of a program
are executed when running the test suite to determine which branches of conditional statements
have been taken.

For example:

If the number of lines of code in a system component is 500 and the number of lines executed
across all existing test cases is 50, then your test coverage is:

(50 / 500) * 100 = 10%

Traceability Matrix
Traceability matrix is a table type document that is used in the development of software application
to trace requirements. It can be used for both forward (from Requirements to Design or Coding)
and backward (from Coding to Requirements) tracing. It is also known as Requirement
Traceability Matrix (RTM) or Cross Reference Matrix (CRM). It helps in tracing the
documents that are developed during various phases of SDLC. It ensures that the software
completely meets the customer's requirements. It helps in detecting the root cause of any bug.

The traceability matrix can be classified into three different types which are as follows:

o Forward traceability
o Backward or reverse traceability
o Bi-directional traceability

Below is the sample template of requirement traceability matrix (RTM):

JIRA is a tool developed by Australian Company Atlassian. This software is used for bug
tracking, issue tracking, and project management. The JIRA full form is actually inherited from
the Japanese word “Gojira” which means “Godzilla”. The basic use of this tool is to track issue
and bugs related to your software and Mobile apps.

Jira software can be used for the following purposes:

 Requirements and Test case management

 In Agile Methodology
 Project Management
 Software Development
 Product Management
 Task Management
 Bug Tracking
 Bugzilla is a bug tracking tool that helps to track the issues related to their product. Bugzilla
tool is written in Perl language, and it uses MySQL database. However, it can also be used as
a test management tool because it can be linked with other Test case management tools such
as Quality Center, Testlink, etc.

Defect/Bug tracking tool

We have various types of bug tracking tools available in software testing that helps us to track the
bug, which is related to the software or the application.

Some of the most commonly used bug tracking tools are as follows:

o Jira
o Bugzilla
o BugNet
o Redmine
o Mantis
o Trac
o Backlog
Bugzilla

Bugzilla is another important bug tracking tool, which is most widely used by many organizations
to track the bugs. It is an open-source tool, which is used to help the customer, and the client to
maintain the track of the bugs. It is also used as a test management tool because, in this, we can
easily link other test case management tools such as ALM, quality Centre, etc. It supports various
operating systems such as Windows, Linux, Mac.

Features of the Bugzilla tool

o A bug can be list in multiple formats
o Email notification controlled by user preferences.
o It has advanced searching capabilities
o This tool ensures excellent security.
o Time tracking

BugNet

It is an open-source defect tracking and project issue management tool, which was written in
Asp.net and C# programming language and support the Microsoft SQL database. The objective of
BugNet is to reduce the complicity of the code that makes the deployment easy. The advanced
version of BugNet is licensed for commercial use.

Features of BugNet tool

o It will provide excellent security with simple navigation and administration.
o BugNet supports various projects and databases.
o With the help of this tool, we can get the email notification.
o This has the capability to manage the Project and milestone.
o This tool has an online support community

Redmine

It is an open-source tool which is used to track the issues and web-based project management tool.
Redmine tool is written in Ruby programing language and also compatible with multiple databases
like MySQL and SQLite

Features of Redmine tool

o Flexible role-based access control

o Time tracking functionality
 o A flexible issue tracking system
o Feeds and email notification
o Multiple languages support (Albanian, Arabic, Dutch, English, Danish and so on)

MantisBT

MantisBT stands for Mantis Bug Tracker. It is a web-based bug tracking system, and it is also
an open-source tool. MantisBT is used to follow the software defects. It is executed in the PHP
programing language.

Features of MantisBT

o With the help of this tool, we have full-text search accessibility.

o Audit trails of changes made to issues
o It provides the revision control system integration
o Revision control of text fields and notes
o Notifications
o Plug-ins
o Graphing of relationships between issues.

Trac

Another defect/ bug tracking tool is Trac, which is also an open-source web-based tool. It is written
in the Python programming language. Trac supports various operating systems such as Windows,
Mac, UNIX, Linux, and so on. Trac is helpful in tracking the issues for software development
projects.

Backlog

The backlog is widely used to manage the IT projects and track the bugs. It is mainly built for the
development team for reporting the bugs with the complete details of the issues, comments,
updates and change of status. It is a project management software.

Features of backlog tool are as follows:

o Gantt and burn down charts

o It supports Git and SVN repositories
o It has the IP access control feature.
o Support Native iOS and Android apps.
Test Report:

A test report is an organized summary of testing objectives, activities, and results. It is created and
used to help stakeholders (product manager, analysts, testing team, and developers) understand
product quality and decide whether a product, feature, or a defect resolution is on track for release.

Test Data mining: -home assignment.

----------------------------------------------------------END----------------------------------------------------
-