Tahun : 2008
Bina Nusantara
Test System
Sistem Pengujian yang lengkap (complete test system) adalah
lingkungan pengujian dan sistem pelaporannya yang terintegrasi
dan terawat.
Fungsi utamanya adalah untuk menemukan, menghasilkan,
mengisolasi, mendeskripsikan, dan mengelola kesalahan (bugs)
pada perangkat lunak atau perangkat keras yang dalam pengujian.
Testing Processes: written and unwritten procedures, checklists,
other agreements about the way the test team does its testing
Testware : tools, documents, scripts, data, cases, tracking
mechanisms, and so forth that the test team uses to do its testing
Test environment : Hardware, software, networking and other
infrastructures, paper and other supplies, facilities, lab, and so forth
that the test team procures, installs and configures to host the
system under test in order to test it.
Bina Nusantara
Test System
Bina Nusantara
Arsitektur Pengujian
Arsitektur Pengujian mendefinisikan prinsip-prinsip
perancangan, struktur, dan alat bantu dan hubungan
antara unsur-unsur tersebut.
Sifatnya tidak bergantung pada proyek tetapi
mencerminkan sistem yang diuji.
Perencanaan pengujian (test plan) akan memanfaatkan
sistem pengujian dalam suatu proyek pengujian.
Bina Nusantara
Testware Components
Bina Nusantara
Komponen Pelaksana Pengujian
Alat Bantu Pengujian (Test Tools)
Kumpulan Kasus Pengujian (Test Case Library)
Test Suites
Bina Nusantara
Action Components
Bina Nusantara
Kemampuan Sistem Pengujian
Sistem pengujian yang dirancang dengan baik
memberikan fasilitas yeng diperlukan untuk
melaksanakan proyek pengujian.
Ketelitian sistem pengujian (test system fidelity) adalah
tingkat dimana sistem pengujian dapat memodelkan
perangkat keras pengguna, perangkat lunak, dan
lingkungan antar muka serta mensimulasikan aktivitas
pengguna secara akurat.
Bina Nusantara
Test System Quality
ANSI/ISO 9126 characteristics for software quality:
functionality
reliability
usability
efficiency
maintainability
portability
Bina Nusantara
Consistency and Simplicity
Consistency: Limit the tool set
Simplicity of the test system is essential to usability
Bina Nusantara
Principles for Quality test Systems
Documentation - test system should also document itself
Test system software should not become full of junk such as non-
test-related documents, unidentifiable log files, output files
associated with old bug isolation operations, and so forth
a well-designed test system promotes accountability
Avoid two mistakes that are archetypal in software development
Bina Nusantara
A Basic Testing Templates
Bina Nusantara
Avoiding the dreaded "Test Escape"
Test Escapes usually arise through one or a combination
of the following types of problems:
A low-fidelity test system
A regression test gap
A test result interpretation error
Bina Nusantara
Four Ways to Spread Tests Across Cycles
Assigning a priority in advance to each test suite, and then running the test
suites in a way that favors the higher-priority tests
Assigning priorities dynamically to each test suite as each test cycle begins,
and then running the test suites in priority order
Shotgunning the test suites across the test cycles
Running the entire set of test suites straight through as many times as
possible (definitely more than once), which I call railroading the tests
Figure 3.13, 3.14, 3.15, 3.16, and 3.17
Bina Nusantara
Test Case: Incremental Improvement
Responding to Failures
Adopting Best Practices
Using Exploratory Testing
Bina Nusantara