ISTQB FOUNDATION 4.0 | Tutorial 18 | Test Types | Functional Testing | Non-Functional Testing | CTFL
Summary
TLDRThis tutorial delves into the ISTQB Foundation Level certification, focusing on Chapter 2.2, which discusses test types and levels within the software development lifecycle. The session clarifies the distinction between functional and non-functional testing, emphasizing their importance in ensuring the core functionalities and enhancing quality characteristics of a software application. Functional testing is about verifying the basic features, while non-functional testing evaluates attributes like performance, security, and usability. The tutorial promises to cover white box, black box, retesting, and regression in subsequent sessions, aiming to deepen understanding of these critical testing concepts.
Takeaways
- π The tutorial is focused on the ISTQB Foundation Level certification, specifically Chapter 2 about testing throughout the software development life cycle.
- π The segment 2.2.2 discusses different types of testing, emphasizing the distinction between testing levels and types, such as static and dynamic testing.
- π Testing types are categorized into functional and non-functional testing, with functional testing targeting the core features and functionalities of the system.
- π‘ Non-functional testing is about enhancing the system's quality characteristics, such as performance, security, and usability, which are not the core functionalities but are essential for a high-quality product.
- π Functional testing levels include unit, integration, system, acceptance, component integration, and system integration, which are considered the standard levels for testing the core functionalities.
- π Non-functional testing levels are extensive and include performance, security, portability, usability, accessibility, recovery, and more, focusing on how the system works beyond its basic features.
- π The tutorial aims to clarify the confusion between testing types and levels, explaining that static and dynamic are methods of testing, whereas functional and non-functional are categories of what is being tested.
- π¬ The script uses examples like Google Pay and flight booking applications to illustrate the concept of core functionalities and how functional testing ensures they work as expected.
- π οΈ Non-functional testing is described as optional but important for defining the quality of a product, addressing aspects like performance under load and security against unauthorized access.
- π The tutorial mentions that there are over 50 levels of testing, highlighting the comprehensive nature of software testing to cover all aspects of a system's performance and quality.
- π The script reassures that while there are many non-functional testing levels, the syllabus does not require memorizing all of them for the ISTQB exam, focusing instead on understanding the concepts.
Q & A
What is the main focus of Chapter 2 in the ISTQB Foundation level certification tutorial?
-The main focus of Chapter 2 is on testing throughout the software development life cycle, specifically discussing test levels and types in segment 2.2.
What is the difference between 'testing levels' and 'testing types'?
-Testing levels refer to the stages in the software development process where testing is conducted, such as unit, integration, and system testing. Testing types, on the other hand, refer to the different approaches to testing, such as functional, non-functional, white box, and black box testing.
What are the two main categories of testing levels mentioned in the script?
-The two main categories of testing levels are functional and non-functional testing.
What is functional testing?
-Functional testing is about testing the core features and functionalities of the system, ensuring that the system performs the tasks it is expected to do.
Can you give an example of a core functionality in an application?
-An example of a core functionality is the ability of Google Pay to transfer money from one account to another, including features like bill payment and QR code scanning for payments.
What are some common functional testing levels?
-Common functional testing levels include unit, integration, system, acceptance, component integration, and system integration.
What is non-functional testing?
-Non-functional testing is about enhancing the quality characteristics of the system, such as performance, security, usability, and accessibility.
Why is non-functional testing important?
-Non-functional testing is important because it ensures that the application not only has the necessary core functionalities but also performs well under various conditions, such as handling high loads or securing sensitive data.
What are some examples of non-functional testing types?
-Examples of non-functional testing types include performance testing, security testing, usability testing, accessibility testing, portability testing, and interoperability testing.
How many levels of testing are mentioned in the script?
-The script mentions that there are over 50 levels of testing, including both functional and non-functional levels.
What is the purpose of the tutorial's next session?
-The purpose of the next session is to discuss white box, black box, retesting, and regression testing, providing further understanding of these testing types.
Outlines
π Introduction to Testing Types in Software Development
This paragraph introduces the topic of testing types within the context of the ISTQB Foundation Level certification, focusing on Chapter 2.2.2. The speaker clarifies the distinction between test levels and test types, emphasizing that while static and dynamic testing refer to methods of testing, functional and non-functional testing categorize the types of tests based on their focus. Functional testing is about verifying the core features and functionalities of an application, ensuring that it performs its intended tasks. Examples such as Google Pay and flight booking applications are used to illustrate the concept of core functionalities. The paragraph also mentions various levels of testing, including unit, integration, system, acceptance, and component integration, which are all categorized under functional testing.
π οΈ Understanding Non-functional Testing and Its Importance
In this paragraph, the focus shifts to non-functional testing, which is concerned with enhancing the quality characteristics of a system. Non-functional testing ensures that an application is not only functional but also performs well under various conditions such as high user load (performance testing), secure against unauthorized access (security testing), and user-friendly (usability testing). The speaker explains that non-functional testing is essential for an application to be successful in the market, as it addresses aspects like performance, security, usability, accessibility, portability, and more. The paragraph also lists several non-functional testing levels, such as performance, stress, load, usability, maintainability, reliability, and portability testing, and clarifies that while there are over 50 levels of testing, the syllabus does not require memorizing all of them for the examination.
Mindmap
Keywords
π‘ISTQB Foundation Level Certification
π‘Software Development Life Cycle (SDLC)
π‘Testing Levels
π‘Test Types
π‘Static Testing
π‘Dynamic Testing
π‘Functional Testing
π‘Non-functional Testing
π‘White Box Testing
π‘Black Box Testing
π‘Regression Testing
π‘Performance Testing
Highlights
Introduction to ISTQB Foundation Level certification tutorial focusing on testing in the software development life cycle.
Exploration of test levels and types in Chapter 2, specifically segment 2.2.
Differentiation between testing types such as functional, non-functional, white box, black box, and retesting, and regression testing.
Clarification of the distinction between static and dynamic testing methods.
Functional testing defined as the process of verifying the core features and functionalities of an application.
Example given of Google Pay to illustrate the concept of core functionalities in functional testing.
Functional testing levels including unit, integration, system, and acceptance testing.
Introduction to non-functional testing, which focuses on enhancing the quality characteristics of a system.
Non-functional testing includes performance, security, usability, accessibility, and other quality attributes.
Importance of non-functional testing in defining the overall quality of a product.
Explanation of how non-functional testing is not mandatory but adds value to product quality.
Listing of various non-functional testing levels such as performance, stress, load, usability, maintainability, reliability, and portability.
Note on the absence of non-functional testing levels in the ISTQB syllabus for the exam.
Upcoming tutorial sessions to cover white box, black box, retesting, and regression testing.
Invitation for viewers to comment with questions and engage with the tutorial content.
Closing remarks encouraging continuous learning and exploration in the field of software testing.
Transcripts
Hello friends and greetings for the day
welcome back to another tutorial on
istqb Foundation level certification we
are in Chapter 2 talking about testing
throughout the software development life
cycle and continuing ahead with our same
segment that is 2.2 test levels and test
type and as a part of today's tutorial
we'll be jumping on to the next segment
which is
2.2.2 that is test types and here we'll
be understanding a lot of interesting
facts and figures about testing so let
let's look into
that so when it comes to the first test
types to talk about of course here we
are talking about the various different
testing types like what exactly are the
different approaches which we can use
throughout the testing in order to test
our different parts of the application
now of course how this is different from
the testing levels people do get
confused or when we say types of testing
like static and dynamic are different
from this of course the way we pronounce
it it may look quite similar to each
other for example types of testing is
static and dynamic but when it comes to
testing types we talk about functional
non-functional white box black box and
you know what not like retesting
regression testing Etc so of course they
do look similar to each other but of
course they are categorized differently
static and dynamic testing are two
different ways to test uh different
parts of the application like static is
more of review of documentation and
dynamic is more of execution but when it
comes to execution we have further
testing types that is white box and
black box and then our levels of testing
can be categorized into functional and
non-functional so today in this
particular tutorial we are talking about
functional and nonfunctional and all we
are trying to talk about is that how
they are different from each other the
very first and foremost important thing
here is that these two are the
categories of levels of testing I do
have a number of different levels of
testing that is if you just keep account
probably we'll get around 50 plus levels
of testing inclusive of very common
levels which we know like unit
integration system acceptance system
integration component integration and
then if you jump onto the non-functional
side we do have performance security
portability usability accessibility
recovery you know fail over and what not
there are so many ways by which I can
test Dynamic testing so the only thing
what we want to convey from this
particular topic is that these levels of
testing can be categorized into two
categories functional and non-functional
now to talk about how do you
differentiate between functional and
non-functional this topic will address
all those query related to that so let's
look at the functional first when it
comes to the functional functional
testing is all about testing the the
core features of the testing and the
functions are what the system does I
think uh this is pretty much very very
easy to correlate that when you talk
about any particular product the base
functionality the core functionality
what you have to offer people for
example if I talk about Google pay
Google pay is an application which
allows you to transfer money from one
account to another account no matter
you're making a bill payment recharging
your cell phone or you're just trying to
scan a QR code and making a payment for
any of your shopping right altogether
all you're trying to do is transferring
money from one account to another
account Now features are offered here
like you know bill payment recharges and
all other Etc and those are what we call
it as the core functionalities of a
product similarly if I talk about
booking a flight or things like
booking.com making my trip yatra.com
these applications based functionality
or core functionality ities to allow
people to search flight book a flight
cancel a flight modify a flight web
checkin so all that menu option what you
see is the base functionality as far as
I'm able to complete this I can talk and
say that my system is functionally ready
makes sense right but when it comes to
you know testing them I just call it as
functional testing so testing the core
functionalities what the system is
expected to do the word what means the
base features the core functionalities
of the product without which it is not
at all an application is what I call it
as the functional functionality of the
product and testing that is called as
functionality so some of the common
functional levels are very standard and
specific functional levels are unit
integration system and acceptance and as
a subp part of that you have component
integration and system integration for
your kind information these are the only
functional levels and everything else
other than this what you know are called
as nonfunctional level so let's talk
quickly about the non-functional levels
also and try to understand what exactly
nonfunctionality on other side is so
when it comes to non-functional testing
of course nonfunctional testing is about
enhancing the quality characteristics of
the system and here the non functions
are how the system works now that's a
very common thing to understand there is
other part of the application of course
an application does not succeed in the
mark maret just with the base core
features that is functionality I need to
certainly top it up with lot of lot of
quality characteristics like performance
security usability and whatnot on a very
high level if I talk about a product
being built and can be used only by one
person it does not make any sense today
right but of course my customer may
demand that hey this product will be
used by 10,000 people at the same time
so in that context I'll go and conduct
performance testing to make sure that
when 10,000 people are working
simultaneously it does not crash and the
response time Remains the Same same way
if the customer says hey I also want to
make sure that this product is highly
secure when it comes to the sensitive
information or the pii that is personal
identification information like phone
number email ID and address Etc then I
need to conduct security testing however
security is not limited to that even
protecting against hacking and
unauthorized accesses of data is also
called a security testing so but this is
a topup without security also the
product will function well same way
without performance testing also a user
can go ahead and use the product so
these are add-ons it's not necessary and
mandatory to conduct for every single
application but if you conduct today you
are defining quality by doing
non-functional testing right so that's
the reason the alternative name for
nonfunctional testing is also quality
characteristics or quality
characteristics testing so this
similarly there are many other level
like user friendliness if you want to
test you have usability if you want to
make sure that this product is
accessible to differently able user like
color blindness and readability the font
Etc you put it into accessibility If the
product can be ported to different
platform you talk about portability
testing If the product can be integrated
to another product interoperability
testing so similarly there are different
levels levels we have which we conduct
here and some of them have been listed
on the screen so we have uh some of them
included as performance testing stress
and load as a part of performance itself
then usability maintainability
reliability and portability testing but
that's not the whole thing however we I
told you we have 50 plus levels so there
are many non-functional levels for
different quality characteristics at the
same time you do not have any
non-functional testing levels in our
syllabus so you don't have to even worry
about their naming conventions or
definitions to remember or answer them
in the examination so just ignore that
and that is all enough to take care of
it so today we just covered functional
and nonfunctional in the next session we
will try to talk about the other two
topics that is white box black box and
retesting regression but I'll just try
to see if it takes longer I'll take more
time to give you separately so that you
have a good understanding and knowledge
all about it so that's all from this
particular tutorial team should you have
anything else feel free to comment below
I'm always there to address your queries
and answer them well till then keep
learning keep exploring keep
understanding the context thanks for
watching the video team and happy
[Music]
learning
Browse More Related Video
ISTQB FOUNDATION 4.0 | Tutorial 13 | 2.2.1 Test Levels & Test Types | Component Testing | CTFL
ISTQB FOUNDATION 4.0 | Tutorial 36 | Value of White Box Test Techniques | CTFL Tutorials | TM SQUARE
CH02. L02. Test-types
Software Testing Tutorial #16 - Types of Software Testing
Manual QA: Testing for Beginners - Types of QA Testing - Part 9
Types of Testing in Software Engineering | Levels of Testing
5.0 / 5 (0 votes)