Software Verification and Validation: Concepts, Techniques, and Best Practices, Summaries of Software Engineering

An overview of software verification and validation, covering key concepts, testing purposes, processes, and classification of testing techniques. It highlights the importance of early testing to identify and address errors, as well as the differences between developer and independent tester perspectives. The characteristics of a "good" test, including the objectives, criteria, and constraints. It also outlines the major testing activities, including planning, execution, analysis, and feedback. Additionally, the document presents various types of testing questions, such as basic, technique-related, and management-focused. The content covers both white-box and black-box testing approaches, providing a comprehensive understanding of software testing methodologies.

Typology: Summaries

2021/2022

Uploaded on 06/22/2022

straw-hat-luffy
straw-hat-luffy 🇵🇰

1 document

1 / 17

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
SE-323
Software
Verification &
Validation
Lecture: 03
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff

Partial preview of the text

Download Software Verification and Validation: Concepts, Techniques, and Best Practices and more Summaries Software Engineering in PDF only on Docsity!

SE-

Software

Verification &

Validation

Lecture: 03

Sequence [ Todays Agenda ]

Content of Lecture

  • Concepts, Issues
  • Testing Purpose
  • Testing Processes, Activities and

Context

  • Classification of Testing Techniques

Basic Concept

Lessons

  • (^) Many errors are made in the early phases
  • (^) These errors are discovered late
  • (^) Repairing those errors is costly
 It pays off to start testing real early

Software Testing

Testing is the process of exercising a program with theTesting is the process of exercising a program with the

specific intent of finding errors prior to delivery to the end specific intent of finding errors prior to delivery to the end

user. user.

errors errors

requirements conformance requirements conformance

performance performance

an indication an indication

of quality of quality

Who Tests the Software?

developer developer independent testerindependent tester

Understands the system Understands the system but, will test "gently" but, will test "gently" and, is driven by " and, is driven by " deliverydelivery "" Must learn about the system, Must learn about the system, but, will attempt to but, will attempt to breakbreak (^) itit and, is driven by and, is driven by (^) qualityquality

What is a “Good” Test?

  • (^) a high probability of finding an error
  • (^) not redundant.
  • (^) neither too simple nor too complex OBJECTIVE: OBJECTIVE: CRITERIA: CRITERIA: CONSTRAINT: CONSTRAINT: to uncover errors to uncover errors in a complete manner in a complete manner with a minimum of effort and time with a minimum of effort and time

Testing Activities

Questions about Testing

  • (^) Basic Questions
  • (^) Testing Technique questions
  • (^) Activity/Management Questions.

16 Software Testing

White-Box Testing White-Box Testing

... our goal is to ensure that ... our goal is to ensure that allall statements and conditions statements and conditions (^) havehave been executed at least been executed at least onceonce ...... Black-Box Black-Box TestingTesting requirementsrequirements events events input input output output

17