Software Testing: A Comprehensive Guide by Uzma and Gulnaz, Lecture notes of Finance

Download Software Testing: A Comprehensive Guide by Uzma and Gulnaz and more Lecture notes Finance in PDF only on Docsity!

Software TestingSoftware Testing

Presented by “Uzma” & “Gulnaz” MIT first Minhajj University Lahore

OBJECTIVES

 (^) Uncover as many as errors (or bugs) as possible in a given product.

• (^) Demonstrate a given software product matching its requirement specifications.
• (^) Validate the quality of a software testing using the minimum cost and efforts.
• (^) Generate high quality test cases, perform effective tests, and issue correct and helpful problem reports.

Error, Bug, Fault & Failure

Fault :

It is a condition that causes the software to fail to perform its required function.

Failure :

It is the inability of a system or component to perform required function according to its specification

Defect :

Commonly refers to several troubles with the software products, with its external behavior or with its internal features. A defect is said to be detected when a failure is observed. Error, Bug, Fault, Failure $ & Defect

 (^) Standard model used world wide to develop a software.  (^) A framework that describes the activities performed at each stage of a software development project.  (^) Necessary to ensure the quality of the software.  (^) Logical steps taken to develop a software product. SDLC(Software Development Life Cycle)

Project Initiation System Study Summary Reports Analysis Regression Test Report Defects Execute Test Cases ( manual /automated ) Design Test Cases Test Plan

Testing Life Cycle

Test

Plan

It is a systematic approach to test a system i.e. software. The plan typically contains a detailed understanding of what the eventual testing workflow will be.

• (^) Verification : The software should confirm to its specification (Are we building the product right?)
• (^) Validation : The software should do what the user really requires (Are we building the right product?)

Verification vs Validation

Testing VS Debugging Debugging is not Testing. Debugging always occurs a consequence of testing. Debugging attempts to find the cause of an error and correct it.

Testing Methodologies White Box Testing Black Box Testing System Testing Usability Testing Static Testing Dynamic Testing Performance Test Walkthrough Unit Testing Code Reviews Integration Testing

Black box testing  (^) No knowledge of internal program design or code required.  (^) Tests are based on requirements and functionality.  (^) (also known as clear box testing, glass box testing, transparent box testing and structural testing) White box testing  (^) Knowledge of the internal program design and code required.  (^) Tests are based on coverage of code statements, branches, paths, conditions.

White box testing

Component

code

Test

outputs

Test data

Tests Derives

Testing Levels

• Unit testing
• Integration testing
• System testing