1 / 12

Perencanaan Pengujian ( Test Plan ) Pertemuan 4

Perencanaan Pengujian ( Test Plan ) Pertemuan 4. Matakuliah : M0232/Testing dan Implementasi Tahun : 2008. TIK. Mahasiswa dapat menjelaskan pentingnya sebuah perencanaan pengujian. (C2) TIK-14 Mahasiswa dapat menghitung jumlah dokumen perencanaan pengujian yang harus dibuat. (C3) TIK-15

melania-taurus
Download Presentation

Perencanaan Pengujian ( Test Plan ) Pertemuan 4

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Perencanaan Pengujian (Test Plan)Pertemuan 4 Matakuliah : M0232/Testing dan Implementasi Tahun : 2008

  2. TIK • Mahasiswa dapat menjelaskan pentingnya sebuah perencanaan pengujian. (C2) TIK-14 • Mahasiswa dapat menghitung jumlah dokumen perencanaan pengujian yang harus dibuat. (C3) TIK-15 • Mahasiswa dapat membuat perencanaan pengujian (test plan) suatu proyek pengujian perangkat lunak. (C3) TIK-16

  3. Why I write Test Plan • What to set? • Scope • Schedule • Budget Parameter • Need more details? How?

  4. How Many Test Plans? • Making many test plans could be based on: • Different Time Periods • Different Methodologies • Different Objectives • Different Audiences

  5. Test Plan Template

  6. Scope

  7. Setting

  8. Quality Risk

  9. Proposed Schedule for Miles

  10. Entry Criteria • Are the necessary documentation, design, and requirements information available that will allow testers to operate the system and judge correct behavior? • Is the system ready for delivery, in whatever form is appropriate for the test phase in question? • Are the supporting utilities, accessories, and prerequisites available in forms that testers can use? • Is the system at the appropriate level of quality? • Is the test environment - lab, hardware, software, and system administration support - ready?

  11. Bug Isolation and Classification • Requirements Failure • Nonrequirement Failure • Waiver Requested • External Failure • Test Failure

More Related