bug tracking database (2) pertemuan 7

Bug Tracking Database (2)Pertemuan 7

Matakuliah : M0232/Testing dan ImplementasiTahun : 2008

Bina Nusantara

• Mahasiswa dapat menggunakan Bug Tracking Database sebagai alat bantu pengujian. (C3) TIK-23

• Mahasiswa dapat menghasilkan laporan pengujian dengan baik dalam berbagai macam bentuk grafik. (C3) TIK-24

TIK

2

Bina Nusantara

What the Bug Relates To: Subsystem, Configuration, and Quality Risks

• Breakdown the subsystem– For DataRocket Case

Study, eg:• Mainboard• Video• SCSI• Network• telecommunication• Other hardware• BIOS• Other software

– For SpeedyWriter Case Study, eg:

• User Interface• Tools• File• Edit Engine• Install/config• Docs/Packaging

Bina Nusantara

Where the Bug Came From: Resolution and Root Cause

Bina Nusantara

Bug Taxonomy• Functional

– Specification– Function– Test

• System– Internal Interface– Hardware Devices– Operating System– Software Architecture– Resource Management

• Process– Arithmetic– Initialization– Control or Sequence– Static Logic– Other

Bina Nusantara

Bug Taxonomy• Data

– Type – Structure– Initial Value– Other

• Code• Documentation• Standards• Other• Duplicate• NAP• Bad Unit• RCN• Unknown

Bina Nusantara

How Long Was the Bug Around?• 8 phases of projects

– Requirements– Design– Implementation– Component Test– Integration Test– System test– Acceptance Test– Post Release

Bina Nusantara

The Finalized Bug Tracking Database

Bina Nusantara

The Finalized Bug Tracking Database

Bina Nusantara

A complete Bug entry Form

Bina Nusantara

Bina Nusantara

Bina Nusantara

RPN (Risk Priority Numbers)• Prioritas dan Serverity tidak selalu sejalan. Dalam

sistem testing mungin ditemukan suatu bug yang memiliki severity 5 tetapi ber-prioritas 1.

• RPN = Priority x Serverity• RPN dapat bernilai 1 sampai dengan 25.• Bug yang paling berbahaya memiliki RPN=1

Bina Nusantara

Pengelolaan Bugs Life Cycle

Bina Nusantara

Bug State

Bina Nusantara

Bug State (2)

Bina Nusantara

Bina Nusantara

Tampilan Layar untuk Memasukkan Bug

• Bug ID: nomor urut bug.• Date Opened: tanggal pelaporan bug.• Project Name: nama proyek.• Tester: nama teknisi• Severity• Priority: prioritas ; & RPN• Summary, Steps to Reproduce, Isolation

Bina Nusantara

• State (text)• Owner (text): penanggung jawab.• Estimate fix (date): perkiraan bug teratasi.• Status / LOG (memo)• Subsystem: area/komponen yang akan terpengaruh oleh bug.• Configuration: konfigurasi sistem yang mengakibatkan bug.• Close date: tanggal saat bug terselesaikan.• Resolution: penjelasan singkat bagaimana bug

diatasi/diperbaiki.• Root Cause: akar penyebab terjadinya kesalahan (developer

atau test engineer).

Tampilan Layar untuk Memasukkan Bug

(lanjutan)

Bina Nusantara

Pelacakan Perubahan Status

Bina Nusantara

Informasi Tentang Bug

Bina Nusantara

Bug Analysis Chart• Generate Bug Analysis Charts

– excellent for communicating with management• The information-rich chart provides answers to a number of

questions.– Are you ready to ship the product?– Have you finished fixing bugs?– Is the bug management process working?– How do milestones in the project relate to inflection points,

changes in the slope of the opened or closed curves?

Bina Nusantara

Opened / Closed Charts

Bina Nusantara

Opened / Closed Charts

Bina Nusantara

Endless Bug Discovery

Bina Nusantara

The Nightmare of ignored Bugs

Bina Nusantara

The Nightmare of Mismanaged Bugs

Bina Nusantara

A Root Cause Breakdown

Bina Nusantara

A Closure Period Chart

Bina Nusantara

A Subsystem Breakdown

Bina Nusantara

Politics and Misuse of Bug Data• Don't Fail to Build Trust• Don't Be a Backseat Driver• Don't Make Individuals Look Bad