ISTQB Foundation Level Certification Explained – Chapter 2 (Part 2)

In this episode of the series on ISTQB’s Foundation Level certification we review the second part of Chapter 2 and talk about test levels and types.

ISTQB Foundation Level Certification Explained – Chapter 1
ISTQB Foundation Level Certification Explained – Chapter 2 (part1)

Learn more about Exactpro Passive Testing Tool Shsha by following this link:
Learn more about Exactpro Testing Tool Load Injector by following this link:

--
Exactpro specializes in quality assurance services and related software development with a focus on test automation for financial market infrastructures worldwide. Exactpro tools apply a variety of data analysis and machine learning techniques to improve the resilience and efficiency of automated functional testing executed under load.

Follow us on

#ISTQB #TestLevels #TestTypes

[varelajp]

Hi!
Million dollar questions:
1. Can white-box test technique be used in both static and dynamic testing?
2. Can black-box test technique be used in both static and dynamic testing?

Are the following examples right?
- Dynamic white-box test example could be when running step by step a unit or system and trying to go thru different paths/branches checking inside the code.
- Dynamic black-box test classic example is the execution of a unit or system with entry data to check if the expected results are obtained.
- Static white-box test examples could be reviewing code standards, dry-running a unit or system and trying to go thru different paths/branches inside the code.
- Static black-box test; I'm not sure how black-box would perform without loading up and running the system or a component and seeing how it responds to various stimuli. Some people consider reviews of requirement documents, specification documents, or design documents as static black-box testing. Is it right? Could this be white-box testing?

[МарияСлепченкова-яг]

1. Four levels of testing are: component testing, integration testing, system testing and acceptance testing.
Compoment testing (unit testing) focuses on testing each module separately and can be done in isolation from the rest of the system.
Integration testing concentrates on interactions between components or systems.
System testing aimes at the behavior and capabilities of a whole system.
Acceptance testing asseses system's readiness as an end product.

2. Stubs and drivers are used to replace the missing software and simulate the interface between components. The difference is that a stub is called from the software unit under test, whereas a driver calls on a unit being tested.

3. Black box testing is based on an analysis of the appropriate test basis which may incluse documents, specifications, formal requirements, business processes or other sources. Black box testing concentrates on the inputs and outputs of the test object without reference to its internal structure.

[ИгорьРоманов-ук]

Hi, my quiz answers are:

1. Four test levels are component, integration, system and acceptance testing.

2. Stub and driver helps to imitate missing code, BUT
Stub replaces low level modules in top-down integration testing process;
Driver replaces high level modules in bottom-up integration testing;

3. During black box testing, test cases base on SPECIFICATION and REQUIREMENTS, BUSINESS NEEDS and past EXPERIENCE.

[tatianasergeeva]

My answers for the quiz are:

1. Four test levels are: component (or module or unit) testing, integration testing, system testing and acceptance testing.
2. A stub is called from the software unit under test, whereas a driver calls on the unit under test. They are used in component testing, performed in isolation, in the cases when some component does need to call another one.
3. The goal of the black box testing is to confirm that the software does what it is supposed to do. For this purpose, based on the specification and performance, a number of test cases are created, where both valid and non-valid inputs used to receive the expected outputs which then get analysed.

[ivijulsc]

Thanks for the videos. Wich syllabus is this guide focused on? I cant find any information about "grey box testing" or "ad hoc corrective modifications" in the last syllabus 2018 3.1.1

[ivanpetin]

Hi all,
1. Test levels are component testing, integration testing, system testing and acceptance testing.
2. Stubs and drivers are used in component testing to replace the missing software. A stub is called from the software unit under test, when a driver is called on the unit under test.
3. Black-box test techniques (also called behavioral or behavior-based techniques) are based on formal requirements documents, specifications, use cases,

user stories, or business processes.