Teknik Pengujian (1) - Bahan Kuliah-STMIK Bandung file03/07/2017 · Teknik Pengujian (1) Pengujian...

Teknik Pengujian (1)

Pengujian Perangkat Lunak

The Six Essential of Software Testing

1. The quality of the test process determine the success of the test effort

2. Prevent defect migration by using early life cycle technique

3. The time for SW testing tools is now

4. A real person must take responsibility for improving the testing process

5. Testing is a professional discipline requiring trained, skilled people

6. Cultivate a positive team attitude of creative destruction

2/28/2011 Bayu Hendradjaya -http://www.if.itb.ac.id/~bayu

2

Development and Testing Evolution


3

Characteristic 1960 1970 1995

Software size Small Moderate Very Large

Degree of SW Complexity Low Medium High

Size of Development Team Small Medium Large

Development methods and standard Ad hoc Moderate Sophisticated

Test methods and standards Ad hoc Primitive Emerging

Independent Test Organizations Few Some Many

Recognition of Testing's importance Little Some Significant

Number of Testing Professional Few Few Many

The Economic of Testing

2/28/2011 Bayu Hendradjaya - http://www.if.itb.ac.id/~bayu 4

Extent of Testing

Cost of Testing

OverTest

Number of Defects

UnderTest

OptimumTest

Quantity

Problem:

• Failure to define testing objectives

• Testing at the wrong phase in the life cycle

• Use of ineffective test techniques

Common Computer Problem

Software Problem

Incomplete Design or Erroneous decision-making criteria

• actions have been incorrect

• inappropriate decision making criteria

Fail to meet customer requirement

• logic error or programming error

Ommitting needed edit checks for completeness of output data

Data Problems

Incomplete Data

Incorrect Data

Obsolete Data


5

Coding

Errors

36 %

Analysis and

Design Errors

64 %

Economics of SDLC Testing

2/28/2011 Bayu Hendradjaya - http://www.if.itb.ac.id/~bayu 6

Requirements20 Errors

Design20 Errors

Code20 Errors

Test80% Error Reduction

Production"0" Defects

cost detect = 1

cost detect = 1

cost detect = 1

cost detect = 10

cost detect = 100

SDLC Testing

Accumulated

Test Cost

Accumulated

Erros/1000

loc

10 10

25 15

42 18

182 4

582 0

Normal SDLC

Accumulated

Test Cost

Accumulated

Erros/1000 loc

0 20

0 40

0 60

480 12

1680 0

The Structured Approach To Testing


7

Life CyclePhase

Verification Activities

Requirements Determine verification approach Determine adequacy of requirements Generate functional Test Data Determine consistency of design with requirements

Design Determine adequacy of design Generate structural and functional test data Determine consistency with design

Program(Build/construction)

Determine adequacy of implementation Generate structural and functional test data for

programs

Test Test application system

Installation Place Tested system into production

Maintenance Modify and retest

Testing in Life Cycle


8

UNIT

INTEGRATION

SYSTEMACCEPTANCE

REGRESSIOIN

VERIFICATION

VALIDATION

SYSTEM TESTING/QUALITY CONTROL

Analyze Design Build Test Install Maintain

• Verification is the process of evaluating a system/component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase (IEEE/ANSI)

• Validation is the process of evaluating a system/component during or at the end of the development process to determine whether it satisfies specified requirements (IEEE/ANSI)

Basic Forms of Testing

Full Testing

starts no later than the requirement phase and continues through acceptance testing

Partial Testing

begins any time after functional design has been completed, with less than optimal influence on requirements and functional design

Endgame Testing

is highly validation oriented, with no influence on requirements or functional design

Audit-Level Testing

is a barebones audit plans, procedures, and products for adequacy, correctness, and compliance to standards.


9

cost

of

test

ing

Error-detection effectiveness

Audit Level

Endgame

Partial

Full

Computer System Strategic Risk

A risk is a condition that can result in a loss

A risk is related to the probability of a loss

The risk is always exists, although the loss may not occur

Risk can not be eliminated, but the impact of the loss can be reduced

The most effective methods to reduce the impact of the loss is testing

Types of strategic risk Incorrect result, unauthorized transaction, lost of integrity

of file, processing can not be reconstructed, lost of continuity of processing, degradation of services for user, security, unreliable result, difficulties to use and operate, unmaintainable program, not portable, not be able to interconnect, unacceptable performance level


10

Test Strategy

A strategy must address the risks and present a process that can

reduce those risks

Two component of Testing Strategy

Test FactorTest Factor - The risk or issue that needs to be addressed as part of the test strategy.

• Correctness, authorization, file integrity, audit trail, continuity of process, service levels, access control, compliance, reliability, ease of use, maintainability, portable, coupling, performance, ease of operation

Test PhaseTest Phase - The phase of the SDLC in which testing will occur

Note:

The risk associated with testing will be called “Test Factors”

Not all test factors will be applicable

The test phase will vary based on the testing methodology used


11

Developing Test Strategy

Select and rank test factor

Identify the system development phase

Identify the business risk associated with the system under development

Place risks in the matrix


12Requirem

ents

Desi

gn

Build

Test

Inte

gra

te

Main

tain

Test

Phase

Test

Factors

FACTO

RS

RIS

K

Strategical/Tactical Testing Cube

The testing methodology cube represents a detailed work program for testing application system

The tactics add the test plans, test criteria, testing techniques and testing tools used in validating and verifying the SW system under development


13Requirem

ents

Desi

gn

Build

Test

Inte

gra

te

Main

tain

Test

Phase

Test

Factors

FACTO

RS

RIS

K

Test

Tactics

Test Strategy

PLANS

• A detailed testing work program is important to ensure that the test factors have been adequately addressed at each phase.

• The first and most important dimensions are the test factors

Developing Testing Tactics

Acquire and study the test strategy

Determine the type of development project

Determine the type of software system

Determine the project Scope

Identify the tactical risks

Determine when testing should occur

Build the system test plan

Build the unit test plans


14

Type of Development Project


15

Type Characteristic Test Tactic

Traditional uses a system developmentmethodology

User knows requirements Development determines

structure

Test at end of each task/step/phase Verify that specs match need Test function and structure

Iterative/Protyping/CASE

Requirement unknown Structure predefined

Verify that CASE tools are usedproperly

Verify that prototypes match need Test functionality

SystemMaintenance

Modify Structure Test Structure Works best with release methods Requires regression testing

Purchased/Contracted SW

Structure unknown

May contain defects Functionality defined in user

documentation

Documentation may varyfrom Software

Verify that functionality matchesneeded

Test functionality Test fit into environment

Type of Software System

Batch (general)

Event Control

Process Control

Procedure Control

Advanced Mathematical Models

Message processing

Diagnostic software

Sensor and Signal Processing

Simulation

Database Management

Data acquisition

Data presentation

Decision and planning aids

Pattern and Image processing

Computer System Software

Software Development Tools


16

Date post:	10-Mar-2019
Category:	Documents
Upload:	nguyendang
View:	226 times
Download:	0 times

Teknik Pengujian (1) - Bahan Kuliah-STMIK Bandung file03/07/2017 · Teknik Pengujian (1) Pengujian...

Documents