ISTQB - What's testing
- 3. Contents 1. What is Tesing? 2. Why is tesing necessary? 3. Seven testing principles?
- 4. What is Testing? Software testing is a process which includes many different activities to assess the quality of the software and to reduce the risk of software failure in operation. Software testing Involve: • Dynamic Testing & Static Testing • Verification & Validation
- 5. Typical Objectives of Testing To evaluate work products such as requirements, user stories, design, and code To verify whether all specified requirements have been fulfilled To validate whether the test object is complete and works as the users and other stakeholders expect To build confidence in the level of quality of the test object To prevent defects To find failures and defects
- 6. Typical Objectives of Testing To provide sufficient information to stakeholders to allow them to make informed decisions, especially regarding the level of quality of the test object To reduce the level of risk of inadequate software quality (e.g., previously undetected failures occurring in operation) To comply with contractual, legal, or regulatory requirements or standards, and/or to verify the test object’s compliance with such requirements or standards
- 7. Testing and Debugging Executing tests can show failures that are caused by defects in the software in operation Debugging is the development activity that finds, analyzes, and fixes such defects
- 8. Why is testing neccesary? FL-1.2.1 (K2) Give examples of why testing is necessary FL-1.2.2 (K2) Describe the relationship between testing and quality assurance and give examples of how testing contributes to higher quality FL-1.2.3 (K2) Distinguish between error, defect, and failure FL-1.2.4 (K2) Distinguish between the root cause of a defect and its effects
- 9. Why is testing neccesary?
- 10. Why is testing neccesary?
- 11. Why is testing neccesary? • Tàu thăm dò khí hậu Sao Hỏa được phóng lên vào năm 1998 đã bị phá hủy do ma sát với bầu khí quyển Sao Hỏa khi sai số lên đến 100 km bởi một lỗi dẫn đường (người điều khiển ở mặt đất đã sử dụng feet trong khi các phần mềm tính toán lại sử dụng hệ mét) • Trong năm 2014, GM đã triệu hồi gần 2,6 triệu xe do lỗi ở bộ phận đánh lửa khiến túi khí không bung ra trong trường hợp xảy ra tai nạn. (lỗi này khiến 124 người chết và 275 người bị thương).
- 12. Why is testing neccesary? Software Testing is necessary because humans make mistakes all the time. Testing can help reduce the risk of failures occurring during operation. Testing contributes to the quality of the components or systems. In addition, software testing may also be required to meet contractual or legal requirements or industry-specific standards.
- 13. Testing’s Contributions to Success Appropriate test techniques are applied with the appropriate level at the appropriate points => reduce the frequency of such problematic deliveries • In requirements reviews or user story refinement => reduces the risk of incorrect or untestable functionality being developed. • In system design => reduce the risk of fundamental design defects and enable tests to be identified at an early stage. • In development => reduce the risk of defects within the code and the tests. • Verify and validate the software prior to release => Increases the likelihood that the software meets stakeholder needs and satisfies requirements.
- 14. Quality Assurance and Testing Quality assurance and testing are not the same, but they are related. A larger concept, quality management, ties them together. • Quality assurance is focused on adherence to proper processes. When processes are carried out properly, the work products are generally of higher quality, which contributes to defect prevention. • Quality control involves various activities, including test activities, that support the achievement of appropriate levels of quality. Test activities are part of the overall software development or maintenance process. Since quality assurance is concerned with the proper execution of the entire process, quality assurance supports proper testing.
- 15. Errors, Defects, and Failures A person can make an error (mistake) => defect (fault or bug) in the software code or in some other related work product = > failure (false) in execute
- 16. Errors, Defects, and Failures Mother of bug - 9-9-1947
- 17. Defects, Root Causes and Effects • The root causes of defects are the earliest actions or conditions that contributed to creating the defects
- 18. 1.Seven testing principles (K2) Explain the seven testing principles
- 19. Testing shows the presence of defects, not their absence • Testing can show the defects are present, but cannot prove that there are no defects.
- 20. Exhaustive testing is impossible • Testing everything including all combinations of inputs and preconditions is not possible • risk analysis, test techniques, and priorities to focus testing efforts
- 21. Early testing saves time and money • In the software development life cycle testing activities should start as early as possible and should be focused on defined objectives.
- 22. Defects cluster together • A small number of modules usually contains most of the defects or is responsible for most of the operational failures. • Predicted defect clusters are an important input into a risk analysis used to focus the test effort
- 23. Beware of the pesticide paradox • If the same tests are repeated over and over again, eventually these tests no longer find any new defects. • To detect new defects, existing tests and test data may need changing, and new tests may need to be written.
- 24. Testing is context dependent Testing is basically context dependent. • Different kinds of program are tested differently • Testing is diffent in Different kinds of lifecycle project
- 25. Absence-of-errors is a fallacy • It is a fallacy (i.e., a mistaken belief) to expect that just finding and fixing a large number of defects will ensure the success of a system.
- 26. THANKS! Any questions? You can find me at @Hoang Hien/ hthien@software.misa.com.vn