cs608-Software Verfication and Validation, Schemes and Mind Maps of Software Engineering

Download cs608-Software Verfication and Validation and more Schemes and Mind Maps Software Engineering in PDF only on Docsity!

Software Verification and Validation

Lecture No. 16

Module 102:

Regression Testing

Regression Testing

 (^) Regression Testing  (^) Software evolve over time.  (^) Reasons may include:  (^) Requirements / design changes due to:  (^) Addition of new functionality  (^) Modification in existing functionality  (^) Design changes  (^) Bug fixing  (^) Maintenance  (^) We need to validate if the changes have not caused any regression in the rest of the system

Regression Testing

 (^) Regression testing at different levels:  (^) Regression testing at the unit level  (^) Re-integration  (^) Regression testing at the function level  (^) Regression testing at the system level  (^) Definition  (^) Let P be a procedure or program, let P’ be a modified version of P, and let T be a test suite for P.

Regression Testing

 (^) Step 1 is regression test selection problem  (^) Step 3 addresses the coverage identification problem  (^) Steps 2 and 4 address the test suite execution problem  (^) Step 5 addresses the test suite maintenance problem: the problem of updating and storing test information.

Module 103:

Regression Testing Requirement

Regression Testing Requirement

 (^) What artifacts are needed to perform software regression testing?  (^) Software change information (change notes).  (^) Updated software Requirements and Design specifications, and user manuals.  (^) Software regression testing process and strategy.  (^) Software regression testing methods and criteria.

Module 104:

How changes effect System Under Test (SUT)

How Changes Effect SUT

 (^) How to identify software change impacts in a systematic way?  (^) REQ impacts  (^) Design impacts  (^) Implementation impacts  (^) User impacts  (^) Test impacts  (^) How to select subset of test cases from existing test suite:  (^) Re-testable  (^) Reusable  (^) Obsolete  (^) Adding new test cases

How Changes Effect SUT

 (^) Therefore, Major regression testing problems:  (^) How to use a systematic method or tool to identify changed software parts?  (^) How to use a systematic method or tool to identify software change impacts?  (^) How to use a systematic method or tool to identify affected software test cases?

Module 105:

Effects of Requirement Change in Regression Testing

Effects of Requirement Change

 (^) Effects of changes in requirements and activities that may induce change:  (^) Add new functional features  (^) Change current function features  (^) Delete existing function features  (^) System Design  (^) System architecture changes

Module 106:

Effects of Maintenance in Regression Testing

Effects of Maintenance

 Effects of maintenance:

 change state-based

behaviors

 change component

interfaces

 change database design

 change GUI design

 change function design

 low-level design doc.

Changes

 change algorithm logic

 change component

structure