Testing Perangkat Lunak

Oleh : Oerip S. Santoso

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

Coding Errors 36 %

Analysis and Design Errors 64 %

12/17/03

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

Economics of SDLC Testing

Normal SDLC Accumulated Test Cost 0 0 0 480 1680 Accumulated Erros/1000 loc 20 40 60 12 0 SDLC Testing Accumulated Accumulated Erros/1000 Test Cost loc 10 10 25 42 182 582 15 18 4 0

Requirements 20 Errors cost detect = 1 Design 20 Errors cost detect = 1 Code 20 Errors cost detect = 1 Test 80% Error Reduction cost detect = 10 Production "0" Defects cost detect = 100

12/17/03

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

The Structured Approach To Testing

Life Cycle Phase Requirements Verification Activities Determine verification approach Determine adequacy of requirements Generate functional Test Data Determine consistency of design with requirements Determine adequacy of design Generate structural and functional test data Determine consistency with design Determine adequacy of implementation Generate structural and functional test data for programs Test application system Place Tested system into production Modify and retest

Design Program (Build/constructi on) Test Installation Maintenance

12/17/03

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

Testing in Life Cycle

Analyze Design Build Test Install Maintain

UNIT

SYSTEM

ACCEPTANCE

INTEGRATION

REGRESSIOIN

VERIFICATION

VALIDATION SYSTEM TESTING/QUALITY CONTROL

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)
12/17/03

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

Basic Forms of Testing

Full Testing
starts no later than the requirement phase and continues through acceptance testing begins any time after functional design has been completed, with less than optimal influence on requirements and functional design is highly validation oriented, with no influence on requirements or functional design is a barebones audit plans, procedures, and products for adequacy, correctness, and compliance to standards.

Partial Testing

Endgame Testing

Audit-Level Testing

cost of testing

Full Partial Endgame Audit Level Error-detection effectiveness

12/17/03

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

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
12/17/03

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

Test Strategy
A strategy must address the risks and present a process that can reduce those risks Two component of Testing Strategy
Test 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 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

12/17/03

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

Developing Test Strategy

Select and rank test factor Identify the system development phase Identify the business risk associated with the system under development Test Place risks in the matrix Phase
Requirements Design Build Test Factors Test

Integrate

CT

FA

12/17/03

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

IS

Maintain
9

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 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
Test Strategy Requirements Integrate Maintain Test Phase Test Factors
st s e T tic c Ta

Design

Build

Test

R IS K

FA

12/17/03

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

PL

AN

CT

10

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

12/17/03

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

11

Type of Development Project

Type Traditional Characteristic uses a system development methodology User knows requirements Development determines structure Requirement unknown Structure predefined Modify Structure Structure unknown May contain defects Functionality defined in user documentation Documentation may vary from Software Test Tactic Test at end of each task/step/phase Verify that specs match need Test function and structure Verify that CASE tools are used properly Verify that prototypes match need Test functionality Test Structure Works best with release methods Requires regression testing Verify that functionality matches needed Test functionality Test fit into environment

Iterative/ Protyping/ CASE System Maintenance

Purchased/ Contracted SW

12/17/03

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

12

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

12/17/03

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

13