Software testing by risk management

w w w . K N A P P . c o m

Software Testing by Risk Management


Testing methodology

Software testing methodology, as shown at the next slide,

implement the approach which supports examination of the

project’s requirements, setting priorities based on risk analysis,

and then determination of where to focus the testing efforts

within the budget and the time constrains

The test planning, based on the risk analysis, presents the

testing functional breakdown, and briefly describes each test

purpose. The design phase produces several STD documents

(for each of the usability, performance, functionality, values

range, track, recovery, & stability testing cycles

Each testing phase measurements and defects will be

concluded by a Software Test Report. A defects review ought to

be done in order to reassess the pre-defined requirements


Testing methodology

Development

Life Cycle Testing Life Cycle

Risk Analysis

Test Plan

Test Design

Requirements

Document

Detailed

Design

System Requirements

System Design

Risk Analysis

Document

System Test

Plan (STP)

Coding / Construction

System Test

Results (STR)

Regression Sanity Performance Functionality System Test

End to End Usability Stability Recovery Compatibility

Compliance Volume Load Stress

Non Functional

Testing Approaches

Reassessment of

Requirements


Testing Guidelines

New

Bug

Return

Bug

Requirements Enhancements Single

Flow

Business

Process

Regression x x x x x

Sanity x x x x x x

Performance

Functionality x x x x x x

System Test x x x x

End to End x x

Non

Functional


Testing approaches Regression

Regression testing is any type of software testing that seeks to uncover new errors, or regressions, in

existing functionality after changes have been made to a system, such as functional enhancements,

patches or configuration changes

Sanity

A sanity test or sanity check is a basic test to quickly evaluate whether a claim or the result of a

calculation can possibly be true. It is a simple check to see if the produced material is rational (that the

material's creator was thinking rationally, applying sanity). The point of a sanity test is to rule out certain

classes of obviously false results, not to catch every possible error

Performance

Performance Testing covers a wide range of engineering or functional evaluations where a material,

product, system, or person is not specified by detailed material or component specifications: rather,

emphasis is on the final measurable performance characteristics. Testing can be a qualitative or

quantitative procedure

Functionality

Functional testing is a type of black box testing that bases its test cases on the specifications of the

software component under test. Functions are tested by feeding them input and examining the output

System Test

System testing of software or hardware is testing conducted on a complete, integrated system to evaluate

the system's compliance with its specified requirements. System testing falls within the scope of black box

testing, and as such, should require no knowledge of the inner design of the code or logic

End to End

End-to-end testing is the process of testing transactions or business level products as they pass right

through the computer systems. Thus this generally ensures that all aspects of the business are supported

by the systems under test


Definitions

Functionality

the quality or state of being functional; especially: the set of functions or capabilities associated with

computer software or hardware or an electronic device

Enhancements

Heighten, increase; especially: to increase or improve in value, quality, desirability, or attractiveness

Patches

A patch is a piece of software designed to fix problems with, or update a computer program or its

supporting data

Configuration changes

Qualitative

The term refers to descriptions or distinctions based on some quality or characteristic rather than on some

quantity or measured value

Quantitative

The term refers to a type of information based in quantities or else quantifiable data

Black-box testing

Method of software testing that tests the functionality of an application as opposed to its internal structures

or workings (see white-box testing). Specific knowledge of the application's code/internal structure and

programming knowledge in general is not required. The tester is only aware of what the software is

supposed to do, but not how

White-box testing

Also known as clear box testing, glass box testing, transparent box testing, and structural testing) is

a method of testing software that tests internal structures or workings of an application, as opposed to its

functionality

Compliance

Conformity in fulfilling official requirements


Test Plan and Report– high level structure

Reporting and communication

– Test plan

– Test cases development and coverage

– Test execution progress

– Testing results


Developed Interfaces Testing approach

Regression – Scope / week X / NA

Sanity – Scope / week X / NA

Performance – Scope / week X / NA

Functionality – Scope / week X NA


Developed Components Testing approach






Developed Requirments Testing approach

R1

– Regression – Scope / week X / NA

– Sanity – Scope / week X / NA

– Performance – Scope / week X / NA

– Functionality – Scope / week X NA

R2

– Regression – Scope / week X / NA

– Sanity – Scope / week X / NA

– Performance – Scope / week X / NA

– Functionality – Scope / week X NA

– End to End - Scope / week X NA


Integration Requirments Testing approach






Failed Test Cases Analysis


Not tested and failed test cases

per suite <>

Component X

– Failed

– To be tested

Component X

– Failed

– To be tested

Component X

– 8 Failed

– To be tested

Component X

– Failed

– To be tested


Challenges during test

<>


Changes due to Challenges

<>


Open Issues

<>

Documents

Software testing by risk management