Minggu 3 Metode Dan Alat Untuk Pengujian

You might also like

Download as ppsx, pdf, or txt
Download as ppsx, pdf, or txt
You are on page 1of 12

Metode dan Alat untuk

Pengujian
DIII Sistem informasi
Pengujian

Dinamis Statis

Metode Viewpoint Jenis kebutuhan

Pengujian Wh itebox Blackbo x

Fungsional Non-fungsional Review, dll.


Statis

Apa itu ●
Code is not executed
Pengujian ●
Checks the code, requirement documents, and design documents to find errors

Statis dan
Dinamis? Dinamis


Code is executed.

Checks for functional behavior of software system, memory/cpu usage and overall
performance of the system
 Manual/automatic reviews of document
 Examples of Work documents:
 Requirement specifications
 Design document
Pengujian  Source Code
Statis  Test Plans
 Test Cases
 Test Scripts
 Help or User document
 Web Page content        
Statis vs
Dinamis
 Test object is fed with input and executed
 Sometimes, the test object cannot be run alone
but must be embedded into a test harness or
test bed
Pengujian
 The test object will usually call different parts
Dinamis of the program through predefined interfaces
 These parts of the program are represented by
placeholders called stubs when they are not
yet implemented
 The test cases are derived from the
specification, or they are already available as
part of the specification
Pengujian  Often called specification-based testing
Black Box techniques because they are based on the
specification/requirement of the program
 Pemilihan input penting  jika bisa mengcover
seluruh input maka complete tapi tidak realistis
 Tidak bisa menemukan masalah jika dari awal
program sudah dibangun dengan requirement
Kelemahan yang salah
Pengujian  Tidak bisa menemukan fungsi tambahan yang
Black Box tidak diperlukan begitu saja, kecuali tidak
sengaja mengeksekusinya
 Often called structure-based testing
techniques because they are based on the
Pengujian structure (of the program)
White Box  The source code must be available, and in
certain cases, it must be possible to manipulate
it, that is, to add code.
 Sulit menemukan jika ada implementasi
requirement yang kurang/salah
Kelemahan
 Hanya bisa memverifikasi kode program yang
Pengujian
sudah ada atau requirement yang sudah
White Box terimplementasi saja; bukan kode yang
harusnya ada di sana tapi tidak ada
 Equivalance Class Partitioning
Teknik  Boundary Value Analysis
Pengujian  State Transition Testing
Black Box  Logic-based Techniques
 Use-case-based Testing
Teknik  Statement testing and coverage
Pengujian  Decision/branch testing and coverage
White Box  Test of conditions

You might also like