New Year Sale 2026! 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

ASTQB CTFL Exam - Topic 2 Question 74 Discussion

Actual exam question for ASTQB's CTFL exam
Question #: 74
Topic #: 2
[All CTFL Questions]

Boundary value testing:

Show Suggested Answer Hide Answer
Suggested Answer: B

by Hermila at Sep 16, 2024, 05:46 AM

Limited Time Offer

25%

Off

Get Premium CTFL Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Melda
3 months ago
Surprised to see so many mixed opinions on this!
upvoted 0 times
...
Lovetta
3 months ago
I disagree, D doesn't really fit the definition.
upvoted 0 times
...
Kallie
3 months ago
Wait, isn't boundary value testing just for edge cases?
upvoted 0 times
...
Ligia
4 months ago
I thought it was similar to equivalence partitioning too.
upvoted 0 times
...
Peggy
4 months ago
B is definitely the right answer!
upvoted 0 times
...
Erasmo
4 months ago
I’m a bit confused about the white box testing reference in option D; I thought boundary value testing was more for black box testing scenarios.
upvoted 0 times
...
Shantell
4 months ago
I feel like I’ve seen questions about this before, and I think boundary value testing is more about the edges rather than combinations of inputs.
upvoted 0 times
...
Jacki
4 months ago
I remember that boundary value testing focuses on testing just above and below the limits, so I think option B sounds right.
upvoted 0 times
...
Shawna
5 months ago
I think boundary value testing is related to equivalence partitioning, but I'm not sure if they are the same thing.
upvoted 0 times
...
Jerry
5 months ago
Okay, I think I got this. Boundary value testing is about testing the values right at the edges of the input and output ranges, not just the normal valid values in the middle. That's different from equivalence partitioning, which is about testing representative values from each input/output class.
upvoted 0 times
...
Wilburn
5 months ago
Hmm, I'm a bit confused on this one. I know boundary value testing has something to do with checking the limits, but I'm not sure how it compares to equivalence partitioning.
upvoted 0 times
...
Judy
5 months ago
I'm pretty sure boundary value testing is about testing the edges of the input and output ranges, not the same as equivalence partitioning.
upvoted 0 times
...
Alyce
5 months ago
Boundary value testing sounds like a good strategy to make sure the system handles edge cases properly. I'll make sure to review that concept before the exam.
upvoted 0 times
...
Gerald
5 months ago
Regarding option D, I seem to recall our last practice question mentioned that continuity isn't always guaranteed when outsourcing, so that makes me hesitant.
upvoted 0 times
...
Darrel
1 year ago
B is the correct answer. Boundary value testing is the only way to ensure your software can handle all those crazy edge cases without falling off the cliff.
upvoted 0 times
...
Keneth
1 year ago
Option B is the way to go. It's like walking a tightrope - you gotta test the boundaries, not just the middle ground!
upvoted 0 times
Felice
1 year ago
Boundary value testing is all about exploring the extremes of input and output.
upvoted 0 times
...
Fidelia
1 year ago
It's like pushing the limits to see how the system responds.
upvoted 0 times
...
Felix
1 year ago
Definitely, it helps uncover any unexpected behavior that might occur.
upvoted 0 times
...
Vicky
1 year ago
I agree, testing the boundaries is crucial for finding potential issues.
upvoted 0 times
...
...
Anjelica
1 year ago
I'm going with B. Boundary value testing is a key technique for ensuring software handles edge cases properly, which is crucial for quality.
upvoted 0 times
Jacqueline
1 year ago
Yes, B is the way to go. Testing those boundary conditions is essential for robust software.
upvoted 0 times
...
Dorothea
1 year ago
I think B is the best choice too. It helps catch any issues at the edges of input and output.
upvoted 0 times
...
Lenna
1 year ago
I agree, B is the correct answer. It's important to test those boundary conditions.
upvoted 0 times
...
...
Glynda
1 year ago
Definitely B. Boundary value testing is all about verifying the behavior at the limits of valid input and output, not just the same as equivalence partitioning.
upvoted 0 times
Chantell
1 year ago
Boundary value testing helps uncover any issues that may arise at the limits of valid input and output.
upvoted 0 times
...
Gianna
1 year ago
It's important to test both below and above the edges of the equivalence classes to ensure the system behaves correctly.
upvoted 0 times
...
Beata
1 year ago
I agree, boundary value testing focuses on testing the boundaries of input and output.
upvoted 0 times
...
...
Veronica
1 year ago
I believe boundary value testing is important in ensuring the software behaves correctly at the edges of input ranges.
upvoted 0 times
...
Marvel
1 year ago
I agree with Kris, because testing the boundaries can help uncover errors that may not be found with other testing methods.
upvoted 0 times
...
Kris
1 year ago
I think boundary value testing is B) Test boundary conditions on, below and above the edges of input and output equivalence classes.
upvoted 0 times
...
Cheryll
1 year ago
I think B is the correct answer. Boundary value testing focuses on the edges of input and output ranges, which is different from equivalence partitioning.
upvoted 0 times
Thersa
1 year ago
Actually, B is the correct answer. Boundary value testing tests boundary conditions on, below and above the edges of input and output equivalence classes.
upvoted 0 times
...
Daron
1 year ago
I think it's A. Boundary value testing is the same as equivalence partitioning tests.
upvoted 0 times
...
Edna
1 year ago
I agree, B is the correct answer. Boundary value testing does focus on the edges of input and output ranges.
upvoted 0 times
...
...

Save Cancel