Download pdf - The Role of a Software Test Manager

7/31/2019 The Role of a Software Test Manager

1/14

Page 1ole of a software test manager

6/12/2012 11:28:11 AMsearchsoftwarequality.techtarget.com/tip/The-role-of-a-software-test-manager

Login

Become a member

RSS

Part of the TechTarget network

archSoftwareQuality.com

News

L

at

es

t

H

eadl

in

es

Mobile

app

development

:

New

strategies

for

developers

and

testers

MarryingScrum

methodology

with

XP

and

other

advice

from

Agile

expert

Mitch

Lacey

Adapting

a

Scrum

frameworkin

the

real

world

:

An

interview

with

Mitch

Lacey

View

All

News

Software Quality

Topics


2/14



ment

Outso

urcing

Softw

are

Projec

ts,

Projec

t

Mana

geme

nt

Proce

ss,Testin

g and

QA

Funda

menta

ls,

Softw

are

Projec

t

Team

s,

Projec

t

Track

ing,

Softw

are

Qualit

y

Mana

geme

nt

Models

and

Methodo

logies

Extre

me

Progr

amming

(XP),

Tradit

ional

Model

s

(RUP,

V-

Model

,

CMM

I,

Water

fall),

Agile,

Softw


3/14



ls,

Scrum

,

TDD

and

MDD

Require

ments

Softw

are

Requi

rements Use

Cases,

Softw

are

Requi

remen

ts

Techn

iques,

Softw

are

Requi

remen

ts

Tools,

Buildi

ng

securi

ty

into

the

SDLC

Security

Testing

and QA

Securi

ty

Testin

g,

Softw

are

Securi

ty

Testin

g

Tools,

Intern

et

Securi

ty,

Penetr

ation

Testin

g

Software

Testing


4/14



Testin

g,

Softw

are

Testin

g

Metho

dologi

es,

Regre

ssion

Testin

g,

User

Acceptance

Testin

g,

Mobil

e

Testin

g,

Softw

are

Test

Desig

n,

Cloud

Appli

cation

Testin

g,Testin

g

Tools

and

Frame

works

,

Explo

ratory

Testin

g,

Cloud

Comp

uting

Testin

g and

Devel

opme

nt,

Softw

are

Perfor

manc

e

Testin

g,

Functi

onal

Softw

are

Testin

g


5/14



e

Mana

geme

nt,

Softw

are

Requi

remen

ts

Mana

geme

nt,

Deplo

yment

Manageme

nt,

Softw

are

Maint

enanc

e

Proce

ss,

Versi

on

Contr

ol,

Confi

gurati

on

and

Chang

e

Mana

geme

nt,

Busin

ess

and

ROI

Analy

sis ,

ALM

Tools,

SLA

Mana

geme

nt,

ALM

Funda

menta

ls,

Cloud

ALM

Hot Topics

ALM

Softw

are

Testin

g

Projec


6/14



Advic

e &

Tutor

ials

Social

media

:

A

guide

to

enhancing

ALM

with

collaborative

tools

Quality

metrics

:

A

guide

to

measuring

software

quality

Software

Test

ProfessionalsConference

Fall

2011

Software

testing

and

ALM

:

A

cloud

computing

guide

Full

Spectrum

ofsoapUI

for

open

source

software

testing

:

Tutorial

Load

testing

and

performance

testing

with

JMeter


7/14



conference

news

Agile

backlash

series

:

Exploring

Agile

development

problems

and

solutions

Tech

nolog

y

Dicti

onary

Find

definitions

and

links

to

technical

resources

Powered

byWhatIs

.

com

Expert

Advice

Tip

s

Ten

ways

Agile

development

process

,

Waterfallapproach

differ

Idea

management

tools

and

features

that

support

ALM

Scrum

and

Kanban

:


8/14



frameworks

View

All

Tips

An

swe

rs

When

to

perform

post-

production

testing

Is

manual

testing

still

needed

alongside

automated

testing

?

Release

management

:How

DevOps

facilitates

collaboration

View

All

Answers

As

k a

Qu

esti

on

Gethelp

from

our

technical

community

Powered

by

ITKnowledgeExchange

.

com

White

Papers

Res

ear

ch


9/14



White

Papers

Business

Webcasts

Downloads

Powered

by

Bitpipe

.

com

Pro

duc

t

De

mo

s

Try

out

software

demos

Powered

by

2020

Software

.com

Blogs

Bl

o

gs

Software

Quality

Insights

Powered

by

ITKnowledgeExchange

.

com

Search this site SEARCH Search

Home

Topics

Software Project Management

Software Testing and QA Fundamentals

The role of a software test manager


10/14



r nt

A

AA

AAA

LinkedIn

Facebook

Twitter

Share This

Reprints

e role of the software test manager or test lead is to effectively lead the testing team. To fulfill this role, the lead must understand the discipline of testing

d how to effectively implement a testing process while fulfilling the traditional leadership roles of a manager. What does that mean? The manager must

anage and implement or maintain an effective testing process. That involves creating a test infrastructure that supports robust communication and a cost-

ective testing framework.

hat the test manager is responsible for:

Defining and implementing the role testing plays within the organization.

Defining the scope of testing within the context of each release/delivery.

Deploying and managing the appropriate testing framework to meet the testing mandate.

Implementing and evolving appropriate measurements and metrics.

To be applied against the product under test.

To be applied against the testing team.

Planning, deploying and managing the testing effort for any given engagement/release.

Managing and growing testing assets required for meeting the testing mandate:

Team members

Testing tools

Testing processes

Retaining skilled testing personnel.

e test manager or lead must understand how testing fits into the organizational structure. In other words, he must clearly define its role within the

ganization. This is often accomplished by

Requires Free Membership to View

Login

E-mail Address:

Become a Member

By submitting your registration information to SearchSoftwareQuality.com you agree to receive email communications from TechTarget and

TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your

registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your

personal data transferred to and processed in the United States. Your use of SearchSoftwareQuality.com is governed by our Terms of Use. You may

contact us at [email protected].

Developers, get IBM PureSystems in your hands - at no charge

When you register, you'll receive targetedemailsdesigned to keep you informed of the most relevant information on Agile

development, application security, testing & QA, software requirements, and more.

Hannah Smalltree, Editorial Director


11/14



afting a mission statement or a defined testing mandate. Example: "To prevent, detect, record and manage defects within the context of a defined release."

w it becomes the test lead's job to communicate and implement effective managerial and testing techniques to support this "simple" mandate. Your team,

ers' (development lead, deployment lead and other leads) and superior's expectations need to be set appropriately given the timeframe of the release and

maturity of the development team and testing team. These expectations are usually defined in terms of functional areas deemed to be in scope or out of

ope. Examples of those in scope include creating a new customer profile and updating a customer profile. Examples of those out of scope mayinclude

curity and backup and recovery.

e definition of scope will change as you move through the various stages of testing. The key thing is to make sure your testing team and the organization

a whole clearly understands what is being tested and what is not being tested for the current release.

e test lead/manager must employ the appropriate testing framework or test architecture to meet the organization's testing needs. Although the testing

mework requirements for any given organization are difficult to define, there are several questions the test lead/manager must ask. The answers to thoe

estions and others will define the short- and long-term goals of the testing framework.

hat is the relationship between product maturity and testing?

the chart below, the first arrow leads to the product being ready for deployment. The second arrow leads to the product being ready to be tested as an

egrated or whole system. The third arrow indicates functional testing can be performed against delivered components. The fourth arrow indicates the

veloper can test the code as an un-integrated unit. And the fifth arrow leads to the product concept being captured and reviewed.

Construction -- How much more construction is required to complete the product.

Product -- How much of the product has been constructed.

ow can the testing organization help prevent defects?

ere are really two sides to testing verification and validation. Unfortunately the meaning of those terms has been defined differently by several governing/


12/14



iverables. Example of development models and at what point during those models you can get information for the review process:

Cascade or waterfall

Requirements

Functional specifications

Agile or Extreme Programming

High-level requirements

Storyboards

sting needs to be included in this review process, and any defects found need to be recorded and managed.

ow and when can the testing organization detect software defects?

e testing organization can detect software defects after the product or some operational segment of it has been delivered. The type of testing to be

rformed depends on the maturity of the product at the time . The classic hierarchy or sequence of testing is as follows:

Design review

Unit testing

Functional testing

System testing

User acceptance testing

e testing team should be involved in at least three of those phases: design review, function testing and system testing.

nctional testing involves the design, implementation and execution of test cases against the functional specification and/or functional requirements for the

oduct. This is where the testing team measures the functional implementation against the product intent using well-formulated test cases and notes any

crepancies as defects (faults). One example is testing to ensure the Web page allows the entry of a new forum member. In that case , you are testing to

sure the Web page functions as an interface.

stem testing follows much the same course (design, implement, execute and defect), but the intent or focus is very different. While functional testing

cuses on discrete functional requirements, system testing focuses on the flow through the system and the connectivity between related systems. An

ample of that is testing to ensure the application allows the entry, activation and recovery of a new forum member. In that case, you are testing to ensure

system supports the business. There are several types of system tests; what is required for any given release should be determined by the scope:

Security

Performance

Integration

hat are the minimum set of measurements and metrics?

e single most important deliverable the testing team maintains is defects. Defects are arguably the only product the testing team produces that are seen

d understood by the project as a whole. This is where the faults against the system are recorded and tracked. At a minimum each defect should contain

following:

Defect name/title

Defect description: What requirement is not being met?

Detailed instructions on how to replicate the defect.

Defect severity.

Impacted functional area.

Defect author.

Status (open, in progress, fixed, closed)

is will then provide the data for a minimal set of metrics:

Number of defects raised

Distribution of defects in terms of severity

Distribution of defects in terms of functional area

om this baseline the measurements and metrics a testing organization maintains are dependent on its maturity and mission statement. The Software

gineering Institute (SEI) Process Maturity Levels apply to testing as much as they do to any software engineering discipline:

1. Initial: (Anarchy) Unpredictable and poorly controlled.

2. Repeatable: (Folklore) Repeat previously mastered tasks.

3. Defined: (Standards) Process characterized, fairly well understood.

4. Managed: (Measurement) Process measured and controlled.

5. Optimizing: (Optimization) Focus on process improvement.

How disciplined the testing organization needs to become and what measurements and metrics are required depend on a


13/14



rly in development

et your testers sharing ideas

pressured by product delays. Motivation and retention of key testing personnel under these conditions is critical. How do

you accomplish this seemly impossible task? I can only go by my personal experience both as a lead and a team member:

If the timelines are impacted, modify the test plan appropriately in terms of scope.

Clearly communicate the situation to the testing team and project management.

Keep clear lines of communication with development and project management.

Whenever possible sell, sell, sell the importance and contributions of the testing team.

Ensure the testing organization has clearly defined roles for each member of the team and a well-defined career path.

Measure and communicate the testing team's return on investment. If the detected defect would have reached the field, what would have been the

cost?

Explain testing expenditures in terms of investment (ROI) not cost.

Finally, never lose your cool

od luck.

--------------------------------------

out the author: David W. Johnson is a senior computer systems analyst with over 20 years of experience in IT across several industries. He has played

y roles in business needs analysis, software design, software development, testing, training, implementation, organizational assessments and support of

siness solutions. David has developed specific expertise over the past 12 years on implementing "Testware," including test strategies, test planning, test

tomation and test management solutions. You may contact David at [email protected].

ore News and Tutorials

Articles

Exploratory testing: Misunderstood concepts and common challenges addressed

Quality metrics: Defect tracking throughout the software lifecycle

How to write an effective test report

Strategies for minimizing regression defects

Proper defect management increases the likelihood for better software quality

Related tags

management

manager

profile

qa

responsibilities

role

role of a test manager

software

test

testing

Related glossary terms


14/14



Tweet 0

Like

0 0ShareShare 0 3

error handling

quality assurance (QA)

build

garbage in, garbage out (GIGO)

white box

conformance testing

load testing

auditor

is was first published in April 2007

in the conversationComment

are

mments

1. There are currently no responses.

Be the first to tell us what you think.

sults

ntribute to the conversation

l fields are required. Comments will appear at the bottom of the article.

1. Comment:

2.

ubmit

sclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT

ofessionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the

aterial submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials

eived through this Web site is at your own risk.

ck to top

u May Also Be Interested In...

re Background

Cloud computing: Addressing software QA environment issues

What upper management should know about managing software testing processes

re Details

Four ways to reduce software testing cost without sacrificing quality

Managing software testing processes on an Agile development team