Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISTQB Exam ISTQB-Agile-Public Topic 1 Question 8 Discussion

Actual exam question for ISTQB's ISTQB-Agile-Public exam
Question #: 8
Topic #: 1
[All ISTQB-Agile-Public Questions]

User Story: As a user I want to be able to calculate tax percentage based on amount of income.

What is the best black box test design technique for verifying the accuracy of this user story?

SELECT ONE OPTION

Show Suggested Answer Hide Answer
Suggested Answer: B

Equivalence partitioning is a black box test design technique suitable for verifying the accuracy of user stories like the one described. It involves dividing input data of a software unit into partitions of equivalent data from which test cases can be derived. For a user story involving tax percentage calculation based on income, Equivalence Partitioning allows the creation of test cases for different income ranges (low, medium, high) to ensure that the system accurately calculates tax percentages for each partition, thus covering various scenarios within the application's functionality.


Contribute your Thoughts:

Terrilyn
5 months ago
By testing all statements in the income calculation, we can ensure complete coverage of the functionality.
upvoted 0 times
...
Gussie
6 months ago
Why do you think so, Terrilyn?
upvoted 0 times
...
Terrilyn
6 months ago
I disagree, I think Statement Testing would be more thorough.
upvoted 0 times
...
Crista
6 months ago
Because testing with low, medium, and high income amounts covers a wide range of possible scenarios.
upvoted 0 times
...
Gussie
6 months ago
Why do you think so, Crista?
upvoted 0 times
...
Crista
6 months ago
I think Equivalence Partitioning would be the best technique.
upvoted 0 times
...
Denae
7 months ago
That's a good point, we should consider that as well.
upvoted 0 times
...
Margot
7 months ago
But wouldn't User story testing also be important to make sure the user can actually get the result they expect?
upvoted 0 times
...
Jeff
7 months ago
I agree with we need to test with different income levels to ensure accuracy.
upvoted 0 times
...
Denae
7 months ago
I think Equivalence partitioning would be the best choice for testing this user story.
upvoted 0 times
Deane
7 months ago
That makes sense. It covers a wide range of scenarios.
upvoted 0 times
...
Rima
7 months ago
B) Equivalence partitioning - test with low, medium and high income.
upvoted 0 times
...
...
Lashon
8 months ago
Woah, state transition testing? That sounds a bit overkill for a simple tax calculation feature. I'd stick with the more straightforward approaches like equivalence partitioning or user story testing.
upvoted 0 times
...
Johna
8 months ago
Hmm, statement testing could work, but I'm not sure it's the *best* approach here. I think state transition testing might be more comprehensive, testing all the possible states of the income entry process.
upvoted 0 times
...
Patria
8 months ago
I don't know, you guys. I'm leaning more towards statement testing. We should make sure all the individual statements in the income calculation are working correctly. That feels like a solid approach to me.
upvoted 0 times
...
Princess
8 months ago
I kind of agree with Hayley. User story testing seems more aligned with the actual requirement. Plus, it's more user-centric, which is important for a feature like this.
upvoted 0 times
...
Hayley
8 months ago
I'm not so sure about that. I think user story testing might be a better fit here. We need to verify that the user can actually perform the key task of entering an income amount and getting the result.
upvoted 0 times
...
Asha
8 months ago
Hmm, this question is interesting. I think the best approach here would be equivalence partitioning. Testing with low, medium, and high income levels should cover the key scenarios and ensure the accuracy of the tax calculation.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77