1 / 13

Software testing Realities

Software testing Realities. What is the realities of software testing Why does the software testing not complete Bugs follow bugs Why not fixed all bugs. It’s impossible to test a program completely. There are the reasons below: The number of possible inputs is very large.

karly-mendez
Download Presentation

Software testing Realities

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 Realities • What is the realities of software testing • Why does the software testing not complete • Bugs follow bugs • Why not fixed all bugs The Realities of software Testing

  2. It’s impossible to test a program completely • There are the reasons below: • The number of possible inputs is very large. • The number of possible outputs is very large. • The number of paths through the software is very large. • The software specification is subjective. The Realities of software Testing

  3. Software testing is a risk-bases exercise Every software project has an optimal test effort The Realities of software Testing

  4. Testing can’t show that bugs don’t exist • Are there bugs in our software? • Are there bugs in other software? • Can you guarantee that there are no bugs to find? The Realities of software Testing

  5. Bugs follow bugs • Frequently: find one bug, then find other and more, Why? • Programmers have bad days (เมื่อ programmerเจ้าของงานล้มป่วย ) • Programmers often make the same mistake (ธรรมชาติของมนุษย์ที่ทำงานแบบเดิมๆตามนิสัย) • Some bugs are really just the tip of the iceberg (การออกแบบงานมักเพื่อแก้ปัญหาพื้นฐาน ฉะนั้นปัญหาที่เกี่ยวข้องบางเรื่องไม่ได้คำนึงถึง ) The Realities of software Testing

  6. Not all bugs you find will be fixed Why? …..There are several reasons : • There are not enough time. • It is really not a bug. • It is too risk to fix. • It is just not worth it. The Realities of software Testing

  7. There are not enough time • In every project there are many software features: • Too few people to code and test. • Not enough room to left them • Must have software in time. The Realities of software Testing

  8. It is really not bug • It’s common for misunderstandings • Test errors • Specification change to result The Realities of software Testing

  9. It is too risk to fix • Software is fragile. • Sometime is like spaghetti. (inter-twined) • Under the pressure to release a product under tight schedule. It may be better to leave in the know bug to avoid the risk of creating than unknown ones The Realities of software Testing

  10. It’s just not worth it. • Bugs that would occur infrequently. • Bugs that appear in little-used features. • A user can prevent or avoid the bug. The Realities of software Testing

  11. What happens when you make the wrong decision? The Intel Pentium test engineers found bug before the chip was released, but the product team decided that it was such small, rare bug that it wasn’t worth fixing. They were under a tight schedule and decided to meet their current deadline and fix the bug in later releases of the chip. Unfortunately, the bug was discovered and rest. The Realities of software Testing

  12. Software testing terms and definitions • Precision :ถูกต้อง แน่นอน แม่นยำ กระฉับ พอดี พิถีพิถัน • Accuracy: ถูกต้อง แน่นอน แม่นยำ The Realities of software Testing

  13. Precision & Accuracy The Realities of software Testing

More Related