Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

iSQI CTFL_Syll_4.0 Exam - Topic 5 Question 19 Discussion

Which of the following statements is CORRECT about error guessing?
D) Error guessing depends on the developers guessing what mistakes testers might make and miss the possible defects
A) While reviewing the test cases, testers have to make guess about the kind of mistakes test cases might contain
B) Error guessing doesn't make use of past failures as past failures are not indicators of correct defects
C) Fault attacks are an example of a technique for implementing error guessing.

iSQI CTFL_Syll_4.0 Exam - Topic 5 Question 19 Discussion

Actual exam question for iSQI's CTFL_Syll_4.0 exam
Question #: 19
Topic #: 5
[All CTFL_Syll_4.0 Questions]

Which of the following statements is CORRECT about error guessing?

Show Suggested Answer Hide Answer
Suggested Answer: D

According to the ISTQB Glossary of Testing Terms, Version 4.0, 2018, page 18, a failure is ''an event in which a component or system does not perform a required function within specified limits''. In this case, the calculator software does not perform the required function of calculating the correct result for 5+6 within the specified limits of accuracy and precision. Therefore, this is an example of a failure.

The other options are incorrect because:

A mistake is ''a human action that produces an incorrect result'' (page 25). A mistake is not an event, but an action, and it may or may not lead to a failure. For example, a mistake could be a typo in the code, a wrong assumption in the design, or a misunderstanding of the requirement.

A fault is ''a defect in a component or system that can cause the component or system to fail to perform its required function'' (page 16). A fault is not an event, but a defect, and it may or may not cause a failure. For example, a fault could be a logical error in the code, a missing specification in the design, or a contradiction in the requirement.

An error is ''the difference between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition'' (page 15). An error is not an event, but a difference, and it may or may not result in a failure. For example, an error could be a rounding error in the calculation, a measurement error in the observation, or a deviation error in the condition.

Reference= ISTQB Glossary of Testing Terms, Version 4.0, 2018, pages 15-18, 25; ISTQB CTFL 4.0 - Sample Exam - Answers, Version 1.1, 2023, Question 96, page 34.


by Ezekiel at Jul 14, 2024, 02:05 AM

Limited Time Offer

25%

Off

Get Premium CTFL_Syll_4.0 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Domingo
9 months ago
Just a reminder, error guessing is all about intuition and experience!
upvoted 0 times
...
Scarlet
9 months ago
D seems off to me. How can developers guess what testers might miss?
upvoted 0 times
...
Sharika
9 months ago
C is interesting, I didn't know fault attacks were linked to error guessing!
upvoted 0 times
...
Hana
10 months ago
I disagree with B. Past failures can definitely guide us in finding new defects.
upvoted 0 times
...
Macy
10 months ago
A is spot on! Testers really need to think about potential mistakes.
upvoted 0 times
...
Britt
10 months ago
D seems off to me; I thought error guessing was more about the testers' perspective rather than what developers might miss.
upvoted 0 times
...
Tatum
10 months ago
I vaguely recall something about fault attacks being related to error guessing, so C could be the right choice.
upvoted 0 times
...
Val
10 months ago
I’m not sure about B; I thought past failures could actually help inform our guesses about where errors might occur.
upvoted 0 times
...
Vicente
11 months ago
I remember that error guessing is about anticipating potential mistakes in test cases, so I think A might be correct.
upvoted 0 times
...
Lamonica
11 months ago
I think the key here is understanding how error guessing works in practice. Option C about fault attacks is throwing me off - I'll need to double-check my notes on that.
upvoted 0 times
...
Carey
11 months ago
Option A sounds right to me. Testers do need to make educated guesses about potential mistakes when reviewing test cases. The other options don't seem to accurately describe error guessing.
upvoted 0 times
...
Gail
11 months ago
This seems like a straightforward question about error guessing. I'll review the options carefully and try to recall the key points about this testing technique.
upvoted 0 times
...
Micah
11 months ago
Hmm, I'm a bit unsure about this one. Error guessing can be tricky, and I want to make sure I understand the differences between the options before selecting an answer.
upvoted 0 times
...
Adela
11 months ago
I'm leaning towards ProductSearchModel.getProductSearchHits() and Category.getProducts() as the most efficient and scalable options here.
upvoted 0 times
...
Sommer
11 months ago
Alright, I've got a strategy for this. I'll start by considering the different options and see if I can eliminate any of them based on my knowledge. Then I'll double-check my reasoning before selecting an answer.
upvoted 0 times
...
Billye
1 year ago
Error guessing? More like error hoping and praying! But hey, at least it's better than error wishful thinking.
upvoted 0 times
Magdalene
1 year ago
C) Fault attacks are an example of a technique for implementing error guessing.
upvoted 0 times
...
Frank
1 year ago
B) Error guessing doesn't make use of past failures as past failures are not indicators of correct defects
upvoted 0 times
...
Leandro
1 year ago
A) While reviewing the test cases, testers have to make guess about the kind of mistakes test cases might contain
upvoted 0 times
...
...
Izetta
1 year ago
Option D is just plain silly. Developers guessing what mistakes testers might make? That's like asking the fox to guard the henhouse!
upvoted 0 times
Nathalie
1 year ago
B) Error guessing doesn't make use of past failures as past failures are not indicators of correct defects
upvoted 0 times
...
Jules
1 year ago
C) Fault attacks are an example of a technique for implementing error guessing.
upvoted 0 times
...
Elroy
1 year ago
A) While reviewing the test cases, testers have to make guess about the kind of mistakes test cases might contain
upvoted 0 times
...
...
Fletcher
1 year ago
Fault attacks, really? I think Option C is a bit of a stretch. Aren't those more related to security testing rather than error guessing?
upvoted 0 times
Verlene
1 year ago
Yeah, I think error guessing is more about testers making educated guesses about potential mistakes in the test cases.
upvoted 0 times
...
Gayla
1 year ago
I agree, fault attacks seem more related to security testing.
upvoted 0 times
...
...
Stevie
1 year ago
I'm not sure about Option B. Aren't past failures often good indicators of the types of defects we should look for? Otherwise, how would we learn from our mistakes?
upvoted 0 times
...
Albina
1 year ago
Option A seems like a reasonable approach. Reviewing test cases and making educated guesses about potential errors is a common practice in error guessing.
upvoted 0 times
...
Marcos
1 year ago
I see your point, Hillary. But I still think it's D because error guessing involves developers guessing the mistakes testers might make.
upvoted 0 times
...
Hillary
1 year ago
I disagree, I believe it's C because fault attacks are a technique used in error guessing.
upvoted 0 times
...
Jeniffer
1 year ago
I think the correct statement about error guessing is A.
upvoted 0 times
...

Save Cancel