Section 1: Introduction To Software Testing: Module 2: Types of Testing

Download as pdf or txt
Download as pdf or txt
You are on page 1of 15

Course Name : Testing and Systems Implementation

Year : 2020

Section 1 : Introduction to
Software Testing

Module 2 : Types of testing


Section Goal

Student will understand about software testing


definition, how important is software testing and
types of testing
References

• Homès, Bernard. (2012).Fundamentals of Software Testing. ISTE


– Wiley. London – Hoboken. ISBN: 978-1-84821-324-1. (p. 66-74)
• Burnstein, I. (2006). Practical software testing: a process-oriented
approach. Springer Science & Business Media
Module Goal

Student will understand the types of testing


Subtopics

• Level of testing
• Functional test
• Structural test
Level of testing

Unit test • component

Integration • Groups of
test component

• A whole
System test system

Acceptance •Whole system


according user
test requirement
Unit test

• Testing the smallest testable component in software.


• It also called unit test, “white box” test
• Test object test that is usually tested: components, program
modules, single functions, programs, database, modules, SQL
requests
• It has goal to detect failure in the components
Integration Test

• Testing the interface and relation between components


• Test object : components, infrastructure, database , system file,
also interface between hardware and software
Integration testing type

• Big bang integration


• Bottom up integration
• Top-down integration
• Integration by functionalities
• Neighbourhood integration
System Test

• Test complete software system to ensure it meet to specification


and requirements
• Test object : whole software, documentation, software
configuration
• Its goal to test end to end transaction and follow the
user/business process.
• System test is execute by test team
Type of system test

• Functional testing
• Performance testing
• Stress testing
• Configuration testing
• Security testing
• Recovery testing
Acceptance test

• Testing the whole system to obtain customer or user acceptance


• Acceptance test is conduct by user or customer representative
• The goal of acceptance test is to gain confidence in the system
• Type of acceptance level :
– User acceptance test
– Operational acceptance
– Contractual acceptance
– Regulatory acceptance
– Alpha test
– Beta test (beta version)
– Pilot phase
– Plant acceptance
Type of acceptance test

• User acceptance test


• Operational acceptance
• Contractual acceptance
• Regulatory acceptance
• Alpha test
• Beta test (beta version)
• Pilot phase
• Plant acceptance
Black box and White Box
testing

Tester execute the Tester look at the line-


software based on of-code to find the
functional or error
requirement of the
software component test

“functional test”
Acceptance test

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy