ISTQB Foundation Level Certification Explained – Chapter 3

In this episode of the series on ISTQB’s Foundation Level certification, we discuss Chapter 3 and talk about static testing and the review process.

ISTQB Foundation Level Certification Explained – Chapter 1:
ISTQB Foundation Level Certification Explained – Chapter 2 (part1):
ISTQB Foundation Level Certification Explained – Chapter 2 (part2):
--
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 #Exactpro #StaticTesting

[tuffcrunch]

Great video, love the pictures and the usage of the "looking for defects" meme at the end haha.

[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?

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

Hi, my answers are

1. Static testing process is about reviewing documentation, specification or code.
2. Buddy checks may also known as informal reviews.
3. Technical review is more formal than walkthrough.

[tatianasergeeva]

My answers for the quiz are:

1. Static testing is used to examine, for example, different kind of specifications, product code, any testware, and so on.
2. This activity is called buddy check, it is a variant of informal review type.
3. Technical review is more formal than walkthrough, because reviewers must go through individual preparation and the scribe should be preferentially performed not by the author. Additional possible benefits of technical review are building confidence in work product, motivating authors to improve and considering alternative implementations.

[svetlanaterekhova]

Hello. Did I understand correctly, that the division by the formality of static testing can also be attributed to dynamic testing?

[tuffcrunch]

Hey guys, I missed the last quiz because I was only following on YouTube lol. I had to visit Instagram to catch up!
My answers for the quizz are :
1- During static testing, we can review the code, specifications and also requirements which allows for detecting detecting errors in conception in an early stage
2-The type of review where we have 2 friends, colleagues reviewing code for each other in an informal way is called informal review
3-A technical review is more formal than walk-trough, because an individual preparation is needed in the former while it isn't needed for the latter. Also a walk-through can sometimes be very informal, it depends on the situation.

[drunkencatface]

according to Syllabus 2018 v3.1 questions about cyclomatic complexity are not part of Foundation Level exam anymore

[ivanpetin]

Hi all, there are quiz answers:

1. There are two "nominal" objects for static testing - work products for reviews (specifications, user stories, acceptance criteria, testware, user guides and also code) and work products for static analysis (first of all, code and some formal documentation or models that can be analyzed by an automated tool).
2. The situation when your work product is estimated by your colleague is called an informal review.
3. The technical review process is more formal than the walkthrough. It is required preparations for its participants, reviewers should be more qualified and review is led by a trained moderator who is NOT the author.

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

1. The static testing focuses on reviewing the software code and requirements. In comparison to dynamic testing, static testing is examined manually or by using different tools.
2. Informal reviews, which can be done by colleagues, are known as buddy checks, pairing or pair reviews.
3. Tecnical review is stricter than walkthrough. Reviewers ought to be technical peers of the author and techical experts in the same or other neighbouring disciplines, whereas walkthrough allows the author to lead the review meeting. Moreover, individual preparation is obligatory in technical reviews while in walkthrough it remains optional. Scribe is mandatory in both types but technical review is better to be scribed not by the author. In addition, technical review aims building confidence in the work product, motivating authors to improve, and considering
alternative implementations as well as finding bugs. Walkthroughs, on the other hand, are more concentrated on exchanging ideas and achieving consensus.

[georginasiaw]

Hello thanks for the video. But you talk way too fast😢