value of software testing

1
Having testers engaged throughout every stage of the project benefits the business in many ways providing a different focus and insight, which allows issues to be addressed early and consequently cheaply! Are naturally curious Challenge assumptions Do not readily accept things Ask difficult questions Act as a bridge between Business and Technical Initiation Design Delivery Closure Bridge between Business and technical. Challenge early assumptions. Look for measurable, realistic outcomes. Gap Analysis Bridge between Business and technical. Challenge early assumptions. Look for measurable, realistic outcomes. Gap Analysis Bridge between Business and technical. Challenge early assumptions. Look for measurable, realistic outcomes. Gap Analysis Bridge between Business and technical. Challenge early assumptions. Look for measurable, realistic outcomes. Gap Analysis Test Inputs Quality, Risk assessment. ISO 9126 Everything being considered? Developable and Testable? Validate requirements and design against the Business Case and each other Verify the solution works as defined Validate that the solution does what it needs to do Controlled exit, baseline of code and deliverables and test assets. Business areas of focus Technical areas of focus Amount of latent risk Point of Testing Engagement Acceptable for go live? Residual risk Time Benefits of testing Results of poor test engagement Problems found during roll out: Delays if issues arise in training and site implementation when users find functionality is missing, wrong or has bugs Delays in implementation in the field while problem are investigated and resolved independent check on the development life cycle from business case to live operation Find issues early to reduce cost Reduce risk leakage between phases Ensuring adequate entry and exit criteria are set and observed at each stage of development and testing Problems found in live operation: Reputational damage to IT eroding trust and adversely affecting confidence in future work Significant additional project or support costs while issues are resolved Additional manual work in the business or IT support to implement workarounds Disruption to other development projects due to support requests Delayed and/or reduced Return on Investment Risk of investigation of the issues by auditors and/or regulatory bodies (especially if issues arise in billing or poor treatment of consumers). Prevent the costs of risk mitigation slipping to later stage of projects Improve the quality of requirements and design Assure business/functional requirements are unambiguous, measureable and testable Testers can also help review designs (architecture, database structures) and even code Be the “glue” across the project. Testers have to engage with a project from start to finish. No- one else gets that detailed end-to-end view or can add value to all activities. Examples of Examples of Static Testing - outcomes Number of Defects Found Time Static Testing helps to push the curve to the left Costs of defect resolution Cost of correction Good testers

Upload: qualitest-group

Post on 05-Dec-2014

68 views

Category:

Software


4 download

DESCRIPTION

The National Institute of Standards and Technology estimates that software bugs cost the U.S. economy $59.5 billion annually. If more comprehensive software testing was performed, a third of these costs could be avoided. The value of software testing is derived from the quality, price and time that are saved by releasing superior products to satisfied customers. Through techniques such as the utilization of knowledgeable and inventive software testers and early identification of defects, a company can decrease the time to market and the cost of quality, while amplifying the end-user satisfaction level. - See more at: http://www.qualitestgroup.com/The-Value-of-Software-Testing#sthash.BJI9tf3b.dpuf

TRANSCRIPT

Page 1: Value of software testing

Having testers engaged throughout every stage of the

project benefits the business in many ways providing

a different focus and insight, which allows issues to

be addressed early and consequently cheaply!

Are naturally curious

Challenge assumptions

Do not readily accept things

Ask difficult questions

Act as a bridge between Business and

Technical

Initiation

Design

Delivery

Closure

Bridge between Business and technical.

Challenge early assumptions.

Look for measurable, realistic outcomes.

Gap Analysis

Bridge between Business and technical.

Challenge early assumptions.

Look for measurable, realistic outcomes.

Gap Analysis

Bridge between Business and technical.

Challenge early assumptions.

Look for measurable, realistic outcomes.

Gap Analysis

Bridge between Business and technical.

Challenge early assumptions.

Look for measurable, realistic outcomes.

Gap Analysis

Test Inputs

Quality, Risk assessment. ISO 9126

Everything being considered?

Developable and Testable?

Validate requirements and design against the Business Case and each

other

Verify the solution works as definedValidate that the

solution does what it needs to do

Controlled exit, baseline of code and deliverables and test

assets.

Businessareas of focus

Technical areas of focus

Am

ou

nt

of

late

nt

risk

Point of Testing

Engagement

Acceptable for go live?

Residual

risk

Time

Benefits of testing Results of poor

test engagementProblems found during roll

out:• Delays if issues arise in training

and site implementation when

users find functionality is missing,

wrong or has bugs

• Delays in implementation in the

field while problem are investigated

and resolved

• independent check on the

development life cycle from

business case to live operation

• Find issues early to reduce cost

• Reduce risk leakage between

phases

• Ensuring adequate entry and exit

criteria are set and observed at

each stage of development and

testing

Problems found in

live operation:•Reputational damage to

IT eroding trust and

adversely affecting

confidence in future

work

•Significant additional

project or support

costs while issues are

resolved

•Additional manual work

in the business or IT

support to implement

workarounds

•Disruption to other

development projects

due to support

requests

•Delayed and/or

reduced Return on

Investment

•Risk of investigation of

the issues by auditors

and/or regulatory

bodies (especially if

issues arise in billing

or poor treatment of

consumers).

• Prevent the costs of risk

mitigation slipping to

later stage of projects

• Improve the quality of

requirements and design

• Assure

business/functional

requirements are

unambiguous,

measureable and testable

• Testers can also help

review designs

(architecture, database

structures) and even

code

• Be the “glue” across the

project. Testers have to

engage with a project

from start to finish. No-

one else gets that

detailed end-to-end view

or can add value to all

activities.

Examples

of

Examples

of

Static

Testing - outcomes

Num

ber o

f

Defe

cts

Found

Time

Static Testing helps to push the

curve to the left

Costs of defect

resolution

Cost

of

correction

Good testers