chap8 - Chapter 8 Software Testing Slide 1 Chapter 8...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Chapter 8 Software Testing Slide 1 Chapter 8 Software Testing Chapter 8 Software Testing Slide 2 Topics covered Validation vs. defect testing Inspections and testing Development testing Unit testing Component testing System testing Test-driven develop- ment Release testing Requirements-based testing Scenario testing Performance testing User testing Chapter 8 Software Testing Slide 3 Topics covered Validation vs. defect testing Inspections and testing Development testing Unit testing Component testing System testing Test-driven develop- ment Release testing Requirements-based testing Scenario testing Performance testing User testing Chapter 8 Software Testing Slide 4 Program testing The term testing can refer to two distinct activities: Attempting to demonstrate (often to the customer) that a program does what it is intended to do, or Attempting to discover program defects before it is put into use. Testing can reveal the presence of errors but (normally) NOT their absence. (Machine-based) testing is part of a more general verification and validation process, which also includes static validation techniques (inspections, proofs of correctness, etc.). Chapter 8 Software Testing Slide 5 Program testing goals When the goal of testing is to demonstrate that software meets its requirements For custom software, this means that there should be at least one test for every user requirement, plus combinations of these requirements, in the requirements document. For generic software, this means that there should be tests for all of the system features, plus combinations of these features, that will be incorporated in the product release. (contd) Chapter 8 Software Testing Slide 6 Program testing goals (contd) When the goal of testing is to discover situations in which the behavior of the software in incorrect, undesirable, or does not conform to its specification Tests should be designed to root-out undesirable system behavior such as system crashes, unwanted interactions with other systems, incorrect computations, and data corruption. (contd) Chapter 8 Software Testing Slide 7 Program testing goals (contd) The first goal leads to validation testing . You expect the system to perform correctly and demonstrate this by using a given set of test cases that reflect the systems expected use. A successful test shows that the system operates as intended . The second goal leads to defect testing . The test cases are designed to expose defects . Test cases used in defect testing can be deliberately obscure and need not reflect how the system is normally used....
View Full Document

Page1 / 67

chap8 - Chapter 8 Software Testing Slide 1 Chapter 8...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online