[工学]第一部分软件测试概述-第三章.pptVIP

第一部分 软件测试概述 第三章 软件测试的现实 Ch.3 The Realities of Software Testing a. Testing Axioms b. Terms and Definitions for software testing MYTHS ABOUT TESTING MORE MYTHS ABOUT TESTING Testing Axioms Testing Axioms 2 Testing Axioms 3 Terms and Definitions for software testing Precision and Accuracy Verification and Validation Quality and Reliability Testing and Quality Assurance (QA) Precision vs. Accuracy Answers are accurate if it they are within a close tolerance of the “true” answer. Answers are precise if they are all close together, even if they are not close to the “true” answer. Example, if the true answer is 0.123, an answer of 0.125 would be accurate if the tolerance is .003, but it would not be precise to 3 decimal places. Often, of course, we want both. Precision vs. Accuracy (2) VERIFICATION VALIDATION Verification vs. Validation Verification confirms that the software meets its specification. - Are we building the product right？ Validation confirms that the software meets the user’s requirements. - Are we building the right product? Never assume the specifications are correct when testing, Both VV tests must be performed. Example: The Hubble Space mirror was ground incorrectly (because the specs were wrong) and, consequently, it failed to produce clear pictures when originally launched. Quality vs. Reliability SQA - SOFTWARE QUALITY ASSURANCE Involves the entire software development PROCESS Monitors and improves the process Makes sure any agreed-upon standards and procedures are followed Ensures that problems are found and handled Oriented towards “prevention” of problems. Testing vs. Quality Assurance (QA) The goal of a testing person is to find bugs, find them as early as possible, and make sure they are fixed. The goal of a QA person is to create and enforce standards and methods to improve the development process so that bugs are prevented. In smaller organizations, the same people often wear both hats. But, larger organizations often separate