1 / 20

Software Testing dan Quality Assurance Pendahuluan dan Konsep dasar

Software Testing dan Quality Assurance Pendahuluan dan Konsep dasar. Materi Pertemuan 3. Sub Pokok Bahasan. Revolusi dari Kualitas Kualitas Perangkat Lunak Peran Pengujian Verifikasi dan Validasi Tujuan dari pengujian Apa yang dimaksud dengan Test Case? Hasil yang diharapkan

dacey
Download Presentation

Software Testing dan Quality Assurance Pendahuluan dan Konsep dasar

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. Software Testing danQuality AssurancePendahuluandanKonsepdasar MateriPertemuan 3

  2. Sub PokokBahasan RevolusidariKualitas KualitasPerangkatLunak PeranPengujian VerifikasidanValidasi Tujuandaripengujian Apa yang dimaksuddengan Test Case? Hasil yang diharapkan Konseppengujian yang sempurna Isu-isuutamadalampengujian Kegiatanpengujian Level Pengujian SumberInformasiuntukpenyeleksian Test case Pengujian Black Box dan White Box Perencanaandanperancanganpengujian Pemantauan dan Pengukuran Pelaksanaan pengujian Alat-alatpengujiandanotomasi Organisasidanmanajementimpengujian

  3. RevolusidariKualitas DimulaidiJepang, oleh Deming, Juran, dan Ishikawa padatahun 1940 Padatahun 1950, Deminmemperkenalkan quality control dalambentukstatistik (Statistical Quality Control) kepadaInsinyur-insinyurygadadiJepang Statistical quality control (SQC) adalahsebuahbidangdisiplinilmuberdasarkanpengukurandanstatistik Metode SQC menggunakantujuh tools manajemenkualitas , yaitu : Pareto analysis, Trend Chart, Flow chart, Histogram, Scatter diagram, Control chart, Cause and effect diagram “Lean principle” (PrinsipPenyederhanaan ) dikembangkanolehTaiichiOhnodariToyota “Sebuahpendekatansistematisuntukmengidentifikasidanmenghilangkanpemborosanmelaluiperbaikanterus-menerus, menarikproduk yang telahberedardipasarandengantujuanuntukmendapatkankesempurnaan”

  4. RevolusidariKualitas Pada 1954, Juranmengubahistilah SQC menjadiTQC (Total Quality Control) elemenUtamadari TQC: Kualitasharusdiutamakan, karenabukanmerupakankeuntunganjangkapendek UtamakanPelanggan, bukanprodusen Keputusandiambilberdasarkanfaktadan data Manajemenberpartisipasidanmenghargaisemuakaryawan Management is driven by cross-functional committees sebuahmetodologi yang inovatifdiciptakanoleh Ishikawa, yang kemudiandisebut Diagram sebabakibat Gambar1.2: Ishikawa diagram

  5. RevolusidariKualitas National Broadcasting Corporation (NBC) dariAmerikaSerikatmenyiarkansebuahacara yang berisi : “If Japan Can ... Why Can’t We?” pada 24 Juni1980 parapemimpindi AS mulaimenekankanpadakualitas Pada 1987 diperkenalkanlah Malcolm Baldrige National Quality Award diAmerikaSerikat hampirsamadenganpenghargaan Deming yang adadijepang Di BaldrigeNational Award kualitasdikatakansebagai: sesuatu yang ditentukanolehpelanggan Di Deming prize, Kualitasdikatakansebagai: sesuatu yang ditentukanolehprodusendenganpenyesuaianterhadap spesifikasi yang dibutuhkan oleh pelanggan.

  6. Kualitas Software Lima sudut Pandang tentangkualitas software: Kerumit user Produksi Produk berdasarkannilai KualitasPerangkatLunakdalamhalfaktorkualitasdankriteria faktorkualitasadalahkarakterdarisebuahsistem Contoh : ketepatan, kehandalan, efisiensi, dan testability Kriteriakualitasadalahbagiandarifaktorkualitas yang berkaitandalampengembangan software n attribute of software architecture Model pengukurankualitasa.l : contoh: ISO 9126, CMM, TPI, and TMM

  7. PerananPengujian penilaiankualitas software dibagimenjadiduakategori: AnalisisStatis Menguji coding danpenyebabdarisemuakejadian yang mungkinakanmunculapabila software dijalankan contoh: review coding, dananalisisalgoritma AnalisisDinamis Eksekusi program untukmengetahuikemungkinankegagalan program Mengamatipolakerja program danmenyimpulkanmengenaikualitasdari program Analisisstatisdandinamissalingmelengkapisatusama lain keduapendekatanadabaiknyadilakukanuntukmendapatkanhasilpengujianmaksimal

  8. VerifikasidanValidasi Verifikasi Evaluasidariperangkatlunak yang membantudalammenentukanapakahproduk yang dikembangkanmemenuhikebutuhan yang ditetapkansebelumpembuatanperangkatlunakdimulai Membuat software dengantepat Validasi Evaluasiperangkatlunak yang membantudalammenentukanapakahprodukmemenuhikegunaan yang diinginkan Membuat software yang tepat

  9. TujuanPengujian Memastikan software bekerjadenganbenar Memperbaikikekurangan software Mengurangiresikokegagalan Mengurangibiayapengujian

  10. Apa yang dimaksuddengan Test Case? Test Case adalahsepasangistilahsederhana, yaitu <input, hasil yang diharapkan> Test cases adalahsesuatuygsederhana, dimana : haislnyahanyabergantungpada input yang diberikan Contoh : ATM ATM example: < cekSaldo, Rp.500.000 >, < penarikanuang, “jumlah?” >, < Rp.200.000, “Rp.200.000” >, < cekSaldo, Rp.300.000 >

  11. Hasil yang diharapkan Hasildarieksekusi program dapatberupa: Nilai yang dihasilkan perubahankondisi Sekumpulannilai-nilai yang harusdiintegrasikanuntukmendapatkanhasil yang valid Sebuahmekanismeuntukmemverifikasikebenaran output dr program disebutsebagaitest oracle: Menuliskanhasil yang diharapkanterhadaptes input Membandingkanhasilkeluaran yang seharusnyadenganhasileksekusi

  12. The Concept of Complete Testing Complete or exhaustive testing means “There are no undisclosed faults at the end of test phase” Complete testing is near impossible for most of the system The domain of possible inputs of a program is too large Valid inputs Invalid inputs The design issues may be too complex to completely test It may not be possible to create all possible execution environments of the system

  13. Testing Activities Identify the objective to be tested Select inputs Compute the expected outcome Set up the execution environment of the program Execute the program Analyze the test results Figure 1.6: Different activities in process testing

  14. Testing Level New test cases are not designed Test are selected, prioritized and executed To ensure that nothing is broken in the new version of the software Figure 1.8: Regression testing at different software testing levels

  15. White-box and Black-box Testing White-box testing a.k.a. structural testing Examines source code with focus on: Control flow Data flow Control flow refers to flow of control from one instruction to another Data flow refers to propagation of values from one variable or constant to another variable It is applied to individual units of a program Software developers perform structural testing on the individual program units they write Black-box testing a.k.a. functional testing Examines the program that is accessible from outside Applies the input to a program and observe the externally visible outcome It is applied to both an entire program as well as to individual program units It is performed at the external interface level of a system It is conducted by a separate software quality assurance group

  16. Test Planning and Design The purpose is to get ready and organized for test execution A test plan provides a: Framework A set of ideas, facts or circumstances within which the tests will be conducted Scope The domain or extent of the test activities Details of resource needed Effort required Schedule of activities Budget Test objectives are identified from different sources Each test case is designed as a combination of modular test components called test steps Test steps are combined together to create more complex tests

  17. Monitoring and Measuring Test Execution Metrics for monitoring test execution Metrics for monitoring defects Test case effectiveness metrics Measure the “defect revealing ability” of the test suite Use the metric to improve the test design process Test-effort effectiveness metrics Number of defects found by the customers that were not found by the test engineers

  18. Test Tools and Automation Increased productivity of the testers Better coverage of regression testing Reduced durations of the testing phases Reduced cost of software maintenance Increased effectiveness of test cases The test cases to be automated are well defined Test tools and an infrastructure are in place The test automation professionals have prior successful experience in automation Adequate budget have been allocation for the procurement of software tools

  19. Test Team Organization and Management Hiring and retaining test engineers is a challenging task Interview is the primary mechanism for evaluating applicants Interviewing is a skills that improves with practice To retain test engineers management must recognize the importance of testing efforts at par with development effort Figure 16.1: Structure of test groups

  20. END OF SLIDE

More Related