SlideShare a Scribd company logo
Testing Throughout The Software
Life Cycle
Presented by
Tyas Setyo Indria
11453201869
ProgramStudiS1 SistemInformasi
FakultasSainsDanTeknologi
UniversitasIslamSultanSyarif KasimRiau
2017
TEST TYPES: THE TARGETS OF TESTING
Reference Graham et.al (2006)
Test types are introduced as a means of clearly defining the objective of a certain test level for a
programme or project. We need to think about different types of testing because testing the func
tionality of the component or system may not be sufficient at each level to meet the overall test
objectives. Focusing the testing on a specific test objective and, therefore, selecting the appropria
te type of test helps making and communicating decisions against test objectives easier.
A test type is focused on a particular test objective, which could be the testing of a function to b
e performed by the component or system; a non-functional quality characteristic, such as reliabilit
y or usability; the structure or architecture of the component or system; or related to changes, i.e.
confirming that defects have been fixed (confirmation testing, or re-testing) and looking for unint
ended changes (regression testing). Depending on its objectives, testing will be organized differen
tly. For example, component testing aimed at performance would be quite different to componen
t testing aimed at achieving decision coverage.
Test Type
Testing of function (functional testing)
Functional testing considers the specified behavior and i
s often also referred to as black-box testing. This is not
entirely true, since black-box testing also includes non-fu
nctional testing
The function of a system (or component) is 'what it does'. Th
is is typically described in a requirements specification, a fun
ctional specification, or in use cases. There may be some fun
ctions that are 'assumed' to be provided that are not docum
ented that are also part of the requirement for a system, tho
ugh it is difficult to test against undocumented and implicit r
equirements. Functional tests are based on these functions, d
escribed in documents or understood by the testers and may
be performed at all test levels (e.g. test for components may
be based on a component specification).
Testing of function (functional testing)
Function (or functionality) testing can, based upon ISO 9126 , be d
one focusing on suitability, interoperability, security, accuracy and
compliance. Security testing, for example, investigates the functions
(e.g. a firewall) relating to detection of threats, such as viruses, from
malicious outsiders It has been replaced by ISO/IEC 25010:2011
Testing of function (functional testing)
Testing functionality can be done from two perspectives:
requirements-based or business-process-based.
 Requirements-based testing uses a specification of the functional requirements
for the system as the basis for designing tests. A good way to start is to use the
table of contents of the requirements specification as an initial test inventory or
list of items to test (or not to test). We should also prioritize the requirements b
ased on risk criteria (if this is not already done in the specification) and use this
to prioritize the tests. This will ensure that the most important and most critical
tests are included in the testing effort.
 Business-process-based testing uses knowledge of the business processes. Busi
ness processes describe the scenarios involved in the day-to-day business use of
the system. For example, a personnel and payroll system may have a business pr
ocess along the lines of: someone joins the company, he or she is paid on a reg
ular basis, and he or she finally leaves the company. Use cases originate from ob
ject-oriented development, but are nowadays popular in many development life
cycles. They also take the business processes as a starting point, although they s
tart from tasks to be performed by users. Use cases are a very useful basis for te
st cases from a business perspective.
Testing of software product characteri
stics (non-functional testing)
Non-functional testing, as functional testing, is performed at all test levels. Non-fu
nctional testing includes, but is not limited to, performance testing, load testing,
stress testing, usability testing, maintainability testing, reliability testing and porta
bility testing. It is the testing of 'how well' the system works.
Many have tried to capture software quality in a collection of characteristics a
nd related sub-characteristics. In these models some elementary characteristic
s keep on reappearing, although their place in the hierarchy can differ. The Int
ernational Organization for Standardization (ISO) has defined a set of quality c
haracteristics [ISO/IEC 9126, 2001]. This set reflects a major step towards cons
ensus in the IT industry and thereby addresses the general notion of software
quality. The ISO 9126 standard defines six quality characteristics and the sub
division of each quality characteristic into a number of sub-characteristics. This
standard is getting more and more recognition in the industry, enabling devel
opment, testing and their stakeholders to use a common terminology for quali
ty characteristics and thereby for non-functional testing.
Testing of software product chara
cteristics (non-functional testing)
The characteristics and their sub-characteristics are, respectively:
 functionality, which consists of five sub-characteristics: suitability, accuracy,
security, interoperability and compliance; this characteristic deals with func
tional testing as described in Section 2.3.1;
 reliability, which is defined further into the sub-characteristics maturity (ro
bustness), fault-tolerance, recoverability and compliance;
 usability, which is divided into the sub-characteristics understandability, le
arnability, operability, attractiveness and compliance;
 efficiency, which is divided into time behavior (performance), resource uti l
ization and compliance;
 maintainability, which consists of five sub-characteristics: analyzability, cha
ngeability, stability, testability and compliance;
 portability, which also consists of five sub-characteristics: adaptability, inst
allability, co-existence, replaceability and compliance.
Testing of software structure/architec
ture (structural testing)
The third target of testing is the structure of the system or compone
nt. If we are talking about the structure of a system, we may call it th
e system architecture. Structural testing is often referred to as 'white
-box' or 'glass-box' because we are interested in what is happening '
inside the box'.
At component level, and to a lesser extent at component integration testing, t
here is good tool support to measure code coverage. Coverage measurement
tools assess the percentage of executable elements (e.g. statements or decisio
n outcomes) that have been exercised (i.e. covered) by a test suite. If coverag
e is not 100%, then additional tests may need to be written and run to cover t
hose parts that have not yet been exercised. This of course depends on the ex
it criteria.
The techniques used for structural testing are structure-based techniques, also
referred to as white-box techniques. Control flow models are often used to s
upport structural testing.
Testing related to changes (confirmati
on and regression testing)
Confirmation testing (re-testing)
When a test fails and we determine that the cause of the failure is a software
defect, the defect is reported, and we can expect a new version of the softwar
e that has had the defect fixed. In this case we will need to execute the test a
gain to confirm that the defect has indeed been fixed. This is known as confir
mation testing (also known as re-testing).
When doing confirmation testing, it is important to ensure that the test is exe
cuted in exactly the same way as it was the first time, using the same inputs,
data and environment. If the test now passes does this mean that the software
is now correct? Well, we now know that at least one part of the software is cor
rect where the defect was. But this is not enough. The fix may have introduced
or uncovered a different defect elsewhere in the software. The way to detect t
hese 'unexpected side-effects' of fixes is to do regression testing.
Testing of software structure/architect
ure (structural testing)
Regression testing
The term 'regression testing' is something of a misnomer. It would be better if it w
ere called 'anti-regression' testing because we are executing tests with the intent of
checking that the system has not regressed (that is, it does not now have more defe
cts in it as a result of some change). More specifically, the purpose of regression test
ing is to verify that modifications in the software or the environment have not cause
d unintended adverse side effects and that the system still meets its requirements.
It is common for organizations to have what is usually called a regression test suite
or regression test pack. This is a set of test cases that is specifically used for regressi
on testing. They are designed to collectively exercise most functions (certainly the m
ost important ones) in a system but not test any one in detail. It is appropriate to h
ave a regression test suite at every level of testing (component testing, integration t
esting, system testing, etc.). All of the test cases in a regression test suite would be
executed every time a new version of software is produced and this makes them ide
al candidates for automation. If the regression test suite is very large it may be mor
e appropriate to select a subset for execution.
Backlink Website Kampus
UIN Suska Riau
JL. H.R Soebrantas No.155 KM.35 Simpang Baru Panam Pe
kanbaru-Riau
 http://sif.uin-suska.ac.id/
 http://fst.uin-suska.ac.id/
 http://www.uin-suska.ac.id/
Thank you

More Related Content

What's hot

Testing throughout the software life cycle
Testing throughout the software life cycleTesting throughout the software life cycle
Testing throughout the software life cycle
aidul azmi
 
Chapter 2 Testing Throughout the Software Life Cycle
Chapter 2 Testing Throughout the Software Life CycleChapter 2 Testing Throughout the Software Life Cycle
Chapter 2 Testing Throughout the Software Life Cycle
Siti Deny Nadiroha
 
Materi Testing dan Implementasi Sistem - Testing throughout the software life...
Materi Testing dan Implementasi Sistem - Testing throughout the software life...Materi Testing dan Implementasi Sistem - Testing throughout the software life...
Materi Testing dan Implementasi Sistem - Testing throughout the software life...
devinta sari
 
Testing throughout the software life cycle
Testing throughout the software life cycleTesting throughout the software life cycle
Testing throughout the software life cycle
muhamad iqbal
 
Bab ii testing throughout the software life cycle
Bab ii testing throughout the software life cycleBab ii testing throughout the software life cycle
Bab ii testing throughout the software life cycle
Riauly Putra
 
Chapter 3 SOFTWARE TESTING PROCESS
Chapter 3 SOFTWARE TESTING PROCESSChapter 3 SOFTWARE TESTING PROCESS
Chapter 3 SOFTWARE TESTING PROCESS
st. michael
 
02. testing throughout the software life cycle
02. testing throughout the software life cycle02. testing throughout the software life cycle
02. testing throughout the software life cycle
Tricia Karina
 
Istqb lesson1
Istqb lesson1Istqb lesson1
Istqb lesson1
Sunday Ayandele
 
Software testing
Software testingSoftware testing
Software testing
Madhumita Chatterjee
 
Software testing and process
Software testing and processSoftware testing and process
Software testing and process
gouravkalbalia
 
CTFL chapter 06
CTFL chapter 06CTFL chapter 06
CTFL chapter 06
Davis Thomas
 
CTFL Module 02
CTFL Module 02CTFL Module 02
CTFL Module 02
Davis Thomas
 
Testing throughout the software life cycle
Testing throughout the software life cycleTesting throughout the software life cycle
Testing throughout the software life cycle
Emi Rizki Ayunanda
 
Software test life cycle
Software test life cycleSoftware test life cycle
Software testing
Software testingSoftware testing
Software testing
Sengu Msc
 
Testing throughout the software life cycle
Testing throughout the software life cycleTesting throughout the software life cycle
Testing throughout the software life cycle
Yusran5
 
Software testing
Software testingSoftware testing
Software testing
ssusere50573
 
7 stages of unit testing
7 stages of unit testing7 stages of unit testing
7 stages of unit testing
Jorge Ortiz
 
Fundamentals of software testing
Fundamentals of software testingFundamentals of software testing
Fundamentals of software testing
Noha Gamal
 

What's hot (20)

Testing throughout the software life cycle
Testing throughout the software life cycleTesting throughout the software life cycle
Testing throughout the software life cycle
 
Chapter 2 Testing Throughout the Software Life Cycle
Chapter 2 Testing Throughout the Software Life CycleChapter 2 Testing Throughout the Software Life Cycle
Chapter 2 Testing Throughout the Software Life Cycle
 
Materi Testing dan Implementasi Sistem - Testing throughout the software life...
Materi Testing dan Implementasi Sistem - Testing throughout the software life...Materi Testing dan Implementasi Sistem - Testing throughout the software life...
Materi Testing dan Implementasi Sistem - Testing throughout the software life...
 
Testing throughout the software life cycle
Testing throughout the software life cycleTesting throughout the software life cycle
Testing throughout the software life cycle
 
Bab ii testing throughout the software life cycle
Bab ii testing throughout the software life cycleBab ii testing throughout the software life cycle
Bab ii testing throughout the software life cycle
 
Chapter 3 SOFTWARE TESTING PROCESS
Chapter 3 SOFTWARE TESTING PROCESSChapter 3 SOFTWARE TESTING PROCESS
Chapter 3 SOFTWARE TESTING PROCESS
 
02. testing throughout the software life cycle
02. testing throughout the software life cycle02. testing throughout the software life cycle
02. testing throughout the software life cycle
 
Istqb lesson1
Istqb lesson1Istqb lesson1
Istqb lesson1
 
Software testing
Software testingSoftware testing
Software testing
 
Software testing and process
Software testing and processSoftware testing and process
Software testing and process
 
CTFL chapter 06
CTFL chapter 06CTFL chapter 06
CTFL chapter 06
 
CTFL Module 02
CTFL Module 02CTFL Module 02
CTFL Module 02
 
Testing throughout the software life cycle
Testing throughout the software life cycleTesting throughout the software life cycle
Testing throughout the software life cycle
 
Software test life cycle
Software test life cycleSoftware test life cycle
Software test life cycle
 
Software testing
Software testingSoftware testing
Software testing
 
3.software testing
3.software testing3.software testing
3.software testing
 
Testing throughout the software life cycle
Testing throughout the software life cycleTesting throughout the software life cycle
Testing throughout the software life cycle
 
Software testing
Software testingSoftware testing
Software testing
 
7 stages of unit testing
7 stages of unit testing7 stages of unit testing
7 stages of unit testing
 
Fundamentals of software testing
Fundamentals of software testingFundamentals of software testing
Fundamentals of software testing
 

Similar to Testing throughout the software life cycle (test types)

Ppt 2 testing throughout the software life cycle
Ppt 2 testing throughout the software life cyclePpt 2 testing throughout the software life cycle
Ppt 2 testing throughout the software life cycle
santi suryani
 
CHAPTER 15Security Quality Assurance TestingIn this chapter yo
CHAPTER 15Security Quality Assurance TestingIn this chapter yoCHAPTER 15Security Quality Assurance TestingIn this chapter yo
CHAPTER 15Security Quality Assurance TestingIn this chapter yo
JinElias52
 
Testing & implementation system 2-wm
Testing & implementation system 2-wmTesting & implementation system 2-wm
Testing & implementation system 2-wm
Wiwik Muslehatin
 
Testing Types And Models
Testing Types And ModelsTesting Types And Models
Testing Types And Modelsnazeer pasha
 
Object Oriented Testing
Object Oriented TestingObject Oriented Testing
Object Oriented Testing
AMITJain879
 
Interview questions for manual testing technology.
Interview questions for manual testing technology.Interview questions for manual testing technology.
Interview questions for manual testing technology.
Vinay Agnihotri
 
Testing throughout the software life cycle & statistic techniques
Testing throughout the software life cycle & statistic techniquesTesting throughout the software life cycle & statistic techniques
Testing throughout the software life cycle & statistic techniques
YAObbiIkhsan
 
Functional Testing- All you need to know (2).pptx
Functional Testing- All you need to know (2).pptxFunctional Testing- All you need to know (2).pptx
Functional Testing- All you need to know (2).pptx
Jason Roy
 
Software testing & Quality Assurance
Software testing & Quality Assurance Software testing & Quality Assurance
Software testing & Quality Assurance
Webtech Learning
 
unit 4.pptx very needful and important p
unit 4.pptx very needful and important punit 4.pptx very needful and important p
unit 4.pptx very needful and important p
20EC040
 
Lesson 7...Question Part 1
Lesson 7...Question Part 1Lesson 7...Question Part 1
Lesson 7...Question Part 1
bhushan Nehete
 
Bab 2
Bab 2Bab 2
Software testing q as collection by ravi
Software testing q as   collection by raviSoftware testing q as   collection by ravi
Software testing q as collection by raviRavindranath Tagore
 
Testing strategies in Software Engineering
Testing strategies in Software EngineeringTesting strategies in Software Engineering
Testing strategies in Software Engineering
MuhammadTalha436
 
System testing
System testingSystem testing
System testing
Sifat Hossain
 
Introduction to SDET
Introduction to SDETIntroduction to SDET
Introduction to SDET
R Ravi Chandran
 
Testing throughout the software life cycle
Testing throughout the software life cycleTesting throughout the software life cycle
Testing throughout the software life cycle
eva khasana
 
Software testing
Software testingSoftware testing
Software testing
Sengu Msc
 
Testing concept definition
Testing concept definitionTesting concept definition
Testing concept definition
Vivek V
 

Similar to Testing throughout the software life cycle (test types) (20)

Ppt 2 testing throughout the software life cycle
Ppt 2 testing throughout the software life cyclePpt 2 testing throughout the software life cycle
Ppt 2 testing throughout the software life cycle
 
CHAPTER 15Security Quality Assurance TestingIn this chapter yo
CHAPTER 15Security Quality Assurance TestingIn this chapter yoCHAPTER 15Security Quality Assurance TestingIn this chapter yo
CHAPTER 15Security Quality Assurance TestingIn this chapter yo
 
Testing & implementation system 2-wm
Testing & implementation system 2-wmTesting & implementation system 2-wm
Testing & implementation system 2-wm
 
Testing Types And Models
Testing Types And ModelsTesting Types And Models
Testing Types And Models
 
Object Oriented Testing
Object Oriented TestingObject Oriented Testing
Object Oriented Testing
 
Interview questions for manual testing technology.
Interview questions for manual testing technology.Interview questions for manual testing technology.
Interview questions for manual testing technology.
 
Testing throughout the software life cycle & statistic techniques
Testing throughout the software life cycle & statistic techniquesTesting throughout the software life cycle & statistic techniques
Testing throughout the software life cycle & statistic techniques
 
Functional Testing- All you need to know (2).pptx
Functional Testing- All you need to know (2).pptxFunctional Testing- All you need to know (2).pptx
Functional Testing- All you need to know (2).pptx
 
Software testing & Quality Assurance
Software testing & Quality Assurance Software testing & Quality Assurance
Software testing & Quality Assurance
 
unit 4.pptx very needful and important p
unit 4.pptx very needful and important punit 4.pptx very needful and important p
unit 4.pptx very needful and important p
 
Lesson 7...Question Part 1
Lesson 7...Question Part 1Lesson 7...Question Part 1
Lesson 7...Question Part 1
 
Bab 2
Bab 2Bab 2
Bab 2
 
Software testing q as collection by ravi
Software testing q as   collection by raviSoftware testing q as   collection by ravi
Software testing q as collection by ravi
 
Testing strategies in Software Engineering
Testing strategies in Software EngineeringTesting strategies in Software Engineering
Testing strategies in Software Engineering
 
Qa Faqs
Qa FaqsQa Faqs
Qa Faqs
 
System testing
System testingSystem testing
System testing
 
Introduction to SDET
Introduction to SDETIntroduction to SDET
Introduction to SDET
 
Testing throughout the software life cycle
Testing throughout the software life cycleTesting throughout the software life cycle
Testing throughout the software life cycle
 
Software testing
Software testingSoftware testing
Software testing
 
Testing concept definition
Testing concept definitionTesting concept definition
Testing concept definition
 

Recently uploaded

In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...
Juraj Vysvader
 
Quarkus Hidden and Forbidden Extensions
Quarkus Hidden and Forbidden ExtensionsQuarkus Hidden and Forbidden Extensions
Quarkus Hidden and Forbidden Extensions
Max Andersen
 
Globus Compute Introduction - GlobusWorld 2024
Globus Compute Introduction - GlobusWorld 2024Globus Compute Introduction - GlobusWorld 2024
Globus Compute Introduction - GlobusWorld 2024
Globus
 
Advanced Flow Concepts Every Developer Should Know
Advanced Flow Concepts Every Developer Should KnowAdvanced Flow Concepts Every Developer Should Know
Advanced Flow Concepts Every Developer Should Know
Peter Caitens
 
Designing for Privacy in Amazon Web Services
Designing for Privacy in Amazon Web ServicesDesigning for Privacy in Amazon Web Services
Designing for Privacy in Amazon Web Services
KrzysztofKkol1
 
Explore Modern SharePoint Templates for 2024
Explore Modern SharePoint Templates for 2024Explore Modern SharePoint Templates for 2024
Explore Modern SharePoint Templates for 2024
Sharepoint Designs
 
Into the Box 2024 - Keynote Day 2 Slides.pdf
Into the Box 2024 - Keynote Day 2 Slides.pdfInto the Box 2024 - Keynote Day 2 Slides.pdf
Into the Box 2024 - Keynote Day 2 Slides.pdf
Ortus Solutions, Corp
 
Lecture 1 Introduction to games development
Lecture 1 Introduction to games developmentLecture 1 Introduction to games development
Lecture 1 Introduction to games development
abdulrafaychaudhry
 
De mooiste recreatieve routes ontdekken met RouteYou en FME
De mooiste recreatieve routes ontdekken met RouteYou en FMEDe mooiste recreatieve routes ontdekken met RouteYou en FME
De mooiste recreatieve routes ontdekken met RouteYou en FME
Jelle | Nordend
 
Enhancing Research Orchestration Capabilities at ORNL.pdf
Enhancing Research Orchestration Capabilities at ORNL.pdfEnhancing Research Orchestration Capabilities at ORNL.pdf
Enhancing Research Orchestration Capabilities at ORNL.pdf
Globus
 
Multiple Your Crypto Portfolio with the Innovative Features of Advanced Crypt...
Multiple Your Crypto Portfolio with the Innovative Features of Advanced Crypt...Multiple Your Crypto Portfolio with the Innovative Features of Advanced Crypt...
Multiple Your Crypto Portfolio with the Innovative Features of Advanced Crypt...
Hivelance Technology
 
2024 RoOUG Security model for the cloud.pptx
2024 RoOUG Security model for the cloud.pptx2024 RoOUG Security model for the cloud.pptx
2024 RoOUG Security model for the cloud.pptx
Georgi Kodinov
 
WSO2Con2024 - WSO2's IAM Vision: Identity-Led Digital Transformation
WSO2Con2024 - WSO2's IAM Vision: Identity-Led Digital TransformationWSO2Con2024 - WSO2's IAM Vision: Identity-Led Digital Transformation
WSO2Con2024 - WSO2's IAM Vision: Identity-Led Digital Transformation
WSO2
 
Prosigns: Transforming Business with Tailored Technology Solutions
Prosigns: Transforming Business with Tailored Technology SolutionsProsigns: Transforming Business with Tailored Technology Solutions
Prosigns: Transforming Business with Tailored Technology Solutions
Prosigns
 
A Comprehensive Look at Generative AI in Retail App Testing.pdf
A Comprehensive Look at Generative AI in Retail App Testing.pdfA Comprehensive Look at Generative AI in Retail App Testing.pdf
A Comprehensive Look at Generative AI in Retail App Testing.pdf
kalichargn70th171
 
Cracking the code review at SpringIO 2024
Cracking the code review at SpringIO 2024Cracking the code review at SpringIO 2024
Cracking the code review at SpringIO 2024
Paco van Beckhoven
 
Beyond Event Sourcing - Embracing CRUD for Wix Platform - Java.IL
Beyond Event Sourcing - Embracing CRUD for Wix Platform - Java.ILBeyond Event Sourcing - Embracing CRUD for Wix Platform - Java.IL
Beyond Event Sourcing - Embracing CRUD for Wix Platform - Java.IL
Natan Silnitsky
 
GlobusWorld 2024 Opening Keynote session
GlobusWorld 2024 Opening Keynote sessionGlobusWorld 2024 Opening Keynote session
GlobusWorld 2024 Opening Keynote session
Globus
 
Dominate Social Media with TubeTrivia AI’s Addictive Quiz Videos.pdf
Dominate Social Media with TubeTrivia AI’s Addictive Quiz Videos.pdfDominate Social Media with TubeTrivia AI’s Addictive Quiz Videos.pdf
Dominate Social Media with TubeTrivia AI’s Addictive Quiz Videos.pdf
AMB-Review
 
TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERROR
TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERRORTROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERROR
TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERROR
Tier1 app
 

Recently uploaded (20)

In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...
 
Quarkus Hidden and Forbidden Extensions
Quarkus Hidden and Forbidden ExtensionsQuarkus Hidden and Forbidden Extensions
Quarkus Hidden and Forbidden Extensions
 
Globus Compute Introduction - GlobusWorld 2024
Globus Compute Introduction - GlobusWorld 2024Globus Compute Introduction - GlobusWorld 2024
Globus Compute Introduction - GlobusWorld 2024
 
Advanced Flow Concepts Every Developer Should Know
Advanced Flow Concepts Every Developer Should KnowAdvanced Flow Concepts Every Developer Should Know
Advanced Flow Concepts Every Developer Should Know
 
Designing for Privacy in Amazon Web Services
Designing for Privacy in Amazon Web ServicesDesigning for Privacy in Amazon Web Services
Designing for Privacy in Amazon Web Services
 
Explore Modern SharePoint Templates for 2024
Explore Modern SharePoint Templates for 2024Explore Modern SharePoint Templates for 2024
Explore Modern SharePoint Templates for 2024
 
Into the Box 2024 - Keynote Day 2 Slides.pdf
Into the Box 2024 - Keynote Day 2 Slides.pdfInto the Box 2024 - Keynote Day 2 Slides.pdf
Into the Box 2024 - Keynote Day 2 Slides.pdf
 
Lecture 1 Introduction to games development
Lecture 1 Introduction to games developmentLecture 1 Introduction to games development
Lecture 1 Introduction to games development
 
De mooiste recreatieve routes ontdekken met RouteYou en FME
De mooiste recreatieve routes ontdekken met RouteYou en FMEDe mooiste recreatieve routes ontdekken met RouteYou en FME
De mooiste recreatieve routes ontdekken met RouteYou en FME
 
Enhancing Research Orchestration Capabilities at ORNL.pdf
Enhancing Research Orchestration Capabilities at ORNL.pdfEnhancing Research Orchestration Capabilities at ORNL.pdf
Enhancing Research Orchestration Capabilities at ORNL.pdf
 
Multiple Your Crypto Portfolio with the Innovative Features of Advanced Crypt...
Multiple Your Crypto Portfolio with the Innovative Features of Advanced Crypt...Multiple Your Crypto Portfolio with the Innovative Features of Advanced Crypt...
Multiple Your Crypto Portfolio with the Innovative Features of Advanced Crypt...
 
2024 RoOUG Security model for the cloud.pptx
2024 RoOUG Security model for the cloud.pptx2024 RoOUG Security model for the cloud.pptx
2024 RoOUG Security model for the cloud.pptx
 
WSO2Con2024 - WSO2's IAM Vision: Identity-Led Digital Transformation
WSO2Con2024 - WSO2's IAM Vision: Identity-Led Digital TransformationWSO2Con2024 - WSO2's IAM Vision: Identity-Led Digital Transformation
WSO2Con2024 - WSO2's IAM Vision: Identity-Led Digital Transformation
 
Prosigns: Transforming Business with Tailored Technology Solutions
Prosigns: Transforming Business with Tailored Technology SolutionsProsigns: Transforming Business with Tailored Technology Solutions
Prosigns: Transforming Business with Tailored Technology Solutions
 
A Comprehensive Look at Generative AI in Retail App Testing.pdf
A Comprehensive Look at Generative AI in Retail App Testing.pdfA Comprehensive Look at Generative AI in Retail App Testing.pdf
A Comprehensive Look at Generative AI in Retail App Testing.pdf
 
Cracking the code review at SpringIO 2024
Cracking the code review at SpringIO 2024Cracking the code review at SpringIO 2024
Cracking the code review at SpringIO 2024
 
Beyond Event Sourcing - Embracing CRUD for Wix Platform - Java.IL
Beyond Event Sourcing - Embracing CRUD for Wix Platform - Java.ILBeyond Event Sourcing - Embracing CRUD for Wix Platform - Java.IL
Beyond Event Sourcing - Embracing CRUD for Wix Platform - Java.IL
 
GlobusWorld 2024 Opening Keynote session
GlobusWorld 2024 Opening Keynote sessionGlobusWorld 2024 Opening Keynote session
GlobusWorld 2024 Opening Keynote session
 
Dominate Social Media with TubeTrivia AI’s Addictive Quiz Videos.pdf
Dominate Social Media with TubeTrivia AI’s Addictive Quiz Videos.pdfDominate Social Media with TubeTrivia AI’s Addictive Quiz Videos.pdf
Dominate Social Media with TubeTrivia AI’s Addictive Quiz Videos.pdf
 
TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERROR
TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERRORTROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERROR
TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERROR
 

Testing throughout the software life cycle (test types)

  • 1. Testing Throughout The Software Life Cycle Presented by Tyas Setyo Indria 11453201869 ProgramStudiS1 SistemInformasi FakultasSainsDanTeknologi UniversitasIslamSultanSyarif KasimRiau 2017 TEST TYPES: THE TARGETS OF TESTING Reference Graham et.al (2006)
  • 2. Test types are introduced as a means of clearly defining the objective of a certain test level for a programme or project. We need to think about different types of testing because testing the func tionality of the component or system may not be sufficient at each level to meet the overall test objectives. Focusing the testing on a specific test objective and, therefore, selecting the appropria te type of test helps making and communicating decisions against test objectives easier. A test type is focused on a particular test objective, which could be the testing of a function to b e performed by the component or system; a non-functional quality characteristic, such as reliabilit y or usability; the structure or architecture of the component or system; or related to changes, i.e. confirming that defects have been fixed (confirmation testing, or re-testing) and looking for unint ended changes (regression testing). Depending on its objectives, testing will be organized differen tly. For example, component testing aimed at performance would be quite different to componen t testing aimed at achieving decision coverage. Test Type
  • 3. Testing of function (functional testing) Functional testing considers the specified behavior and i s often also referred to as black-box testing. This is not entirely true, since black-box testing also includes non-fu nctional testing The function of a system (or component) is 'what it does'. Th is is typically described in a requirements specification, a fun ctional specification, or in use cases. There may be some fun ctions that are 'assumed' to be provided that are not docum ented that are also part of the requirement for a system, tho ugh it is difficult to test against undocumented and implicit r equirements. Functional tests are based on these functions, d escribed in documents or understood by the testers and may be performed at all test levels (e.g. test for components may be based on a component specification).
  • 4. Testing of function (functional testing) Function (or functionality) testing can, based upon ISO 9126 , be d one focusing on suitability, interoperability, security, accuracy and compliance. Security testing, for example, investigates the functions (e.g. a firewall) relating to detection of threats, such as viruses, from malicious outsiders It has been replaced by ISO/IEC 25010:2011
  • 5. Testing of function (functional testing) Testing functionality can be done from two perspectives: requirements-based or business-process-based.  Requirements-based testing uses a specification of the functional requirements for the system as the basis for designing tests. A good way to start is to use the table of contents of the requirements specification as an initial test inventory or list of items to test (or not to test). We should also prioritize the requirements b ased on risk criteria (if this is not already done in the specification) and use this to prioritize the tests. This will ensure that the most important and most critical tests are included in the testing effort.  Business-process-based testing uses knowledge of the business processes. Busi ness processes describe the scenarios involved in the day-to-day business use of the system. For example, a personnel and payroll system may have a business pr ocess along the lines of: someone joins the company, he or she is paid on a reg ular basis, and he or she finally leaves the company. Use cases originate from ob ject-oriented development, but are nowadays popular in many development life cycles. They also take the business processes as a starting point, although they s tart from tasks to be performed by users. Use cases are a very useful basis for te st cases from a business perspective.
  • 6. Testing of software product characteri stics (non-functional testing) Non-functional testing, as functional testing, is performed at all test levels. Non-fu nctional testing includes, but is not limited to, performance testing, load testing, stress testing, usability testing, maintainability testing, reliability testing and porta bility testing. It is the testing of 'how well' the system works. Many have tried to capture software quality in a collection of characteristics a nd related sub-characteristics. In these models some elementary characteristic s keep on reappearing, although their place in the hierarchy can differ. The Int ernational Organization for Standardization (ISO) has defined a set of quality c haracteristics [ISO/IEC 9126, 2001]. This set reflects a major step towards cons ensus in the IT industry and thereby addresses the general notion of software quality. The ISO 9126 standard defines six quality characteristics and the sub division of each quality characteristic into a number of sub-characteristics. This standard is getting more and more recognition in the industry, enabling devel opment, testing and their stakeholders to use a common terminology for quali ty characteristics and thereby for non-functional testing.
  • 7. Testing of software product chara cteristics (non-functional testing) The characteristics and their sub-characteristics are, respectively:  functionality, which consists of five sub-characteristics: suitability, accuracy, security, interoperability and compliance; this characteristic deals with func tional testing as described in Section 2.3.1;  reliability, which is defined further into the sub-characteristics maturity (ro bustness), fault-tolerance, recoverability and compliance;  usability, which is divided into the sub-characteristics understandability, le arnability, operability, attractiveness and compliance;  efficiency, which is divided into time behavior (performance), resource uti l ization and compliance;  maintainability, which consists of five sub-characteristics: analyzability, cha ngeability, stability, testability and compliance;  portability, which also consists of five sub-characteristics: adaptability, inst allability, co-existence, replaceability and compliance.
  • 8. Testing of software structure/architec ture (structural testing) The third target of testing is the structure of the system or compone nt. If we are talking about the structure of a system, we may call it th e system architecture. Structural testing is often referred to as 'white -box' or 'glass-box' because we are interested in what is happening ' inside the box'. At component level, and to a lesser extent at component integration testing, t here is good tool support to measure code coverage. Coverage measurement tools assess the percentage of executable elements (e.g. statements or decisio n outcomes) that have been exercised (i.e. covered) by a test suite. If coverag e is not 100%, then additional tests may need to be written and run to cover t hose parts that have not yet been exercised. This of course depends on the ex it criteria. The techniques used for structural testing are structure-based techniques, also referred to as white-box techniques. Control flow models are often used to s upport structural testing.
  • 9. Testing related to changes (confirmati on and regression testing) Confirmation testing (re-testing) When a test fails and we determine that the cause of the failure is a software defect, the defect is reported, and we can expect a new version of the softwar e that has had the defect fixed. In this case we will need to execute the test a gain to confirm that the defect has indeed been fixed. This is known as confir mation testing (also known as re-testing). When doing confirmation testing, it is important to ensure that the test is exe cuted in exactly the same way as it was the first time, using the same inputs, data and environment. If the test now passes does this mean that the software is now correct? Well, we now know that at least one part of the software is cor rect where the defect was. But this is not enough. The fix may have introduced or uncovered a different defect elsewhere in the software. The way to detect t hese 'unexpected side-effects' of fixes is to do regression testing.
  • 10. Testing of software structure/architect ure (structural testing) Regression testing The term 'regression testing' is something of a misnomer. It would be better if it w ere called 'anti-regression' testing because we are executing tests with the intent of checking that the system has not regressed (that is, it does not now have more defe cts in it as a result of some change). More specifically, the purpose of regression test ing is to verify that modifications in the software or the environment have not cause d unintended adverse side effects and that the system still meets its requirements. It is common for organizations to have what is usually called a regression test suite or regression test pack. This is a set of test cases that is specifically used for regressi on testing. They are designed to collectively exercise most functions (certainly the m ost important ones) in a system but not test any one in detail. It is appropriate to h ave a regression test suite at every level of testing (component testing, integration t esting, system testing, etc.). All of the test cases in a regression test suite would be executed every time a new version of software is produced and this makes them ide al candidates for automation. If the regression test suite is very large it may be mor e appropriate to select a subset for execution.
  • 11. Backlink Website Kampus UIN Suska Riau JL. H.R Soebrantas No.155 KM.35 Simpang Baru Panam Pe kanbaru-Riau  http://sif.uin-suska.ac.id/  http://fst.uin-suska.ac.id/  http://www.uin-suska.ac.id/