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

Actual exam question for ISTQB's ISTQB-Agile-Public exam

Question #: 13
Topic #: 1

You have been asked to explain to your client how to define acceptance criteria that are fully testable. Which of the following is the BEST EXAMPLE for testable acceptance criteria?

SELECT ONE OPTION

AAction 'Reopen' must be available only for a user with a specific authorization level.

BThe ID field must accept input value of a length between 2 and 10 characters.

CThe interface to External System shall be specified.

DThe program's icon should be clear and attractive.

Show Suggested 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.

by Eleonora at Jun 02, 2024, 07:53 PM

Limited Time Offer

25%

Off

Get Premium ISTQB-Agile-Public Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Destiny

1 years ago

Wait, I thought this was a user story about calculating tax percentage, not a game of 'Guess the State Machine'! Option B all the way, my friends.

upvoted 0 times

Pansy

1 years ago

Yeah, I think equivalence partitioning is the way to go for this user story.

upvoted 0 times

...

Melita

1 years ago

I agree, option B seems like the most efficient way to test different income levels.

upvoted 0 times

...

Ammie

1 years ago

Option D? State transition testing? What is this, a finite state machine? I think I'll just stick to the good old equivalence partitioning and call it a day.

upvoted 0 times

Isaac

1 years ago

C) Statement testing - test all statements in income calculation.

upvoted 0 times

...

Dylan

1 years ago

Option D does seem a bit complex. I agree, let's go with equivalence partitioning.

upvoted 0 times

...

Hoa

1 years ago

B) Equivalence partitioning - test with low, medium and high income.

upvoted 0 times

...

Royal

1 years ago

A) User story testing - test that the user can enter an income amount and get a result

upvoted 0 times

...

Peggy

1 years ago

I'd have to go with Option B as well. Gotta make sure the tax percentage is accurate no matter how much you're making, am I right? 'Cause who wants to get audited by the IRS, am I right?

upvoted 0 times

Cherri

1 years ago

I'd have to go with Option B as well. Gotta make sure the tax percentage is accurate no matter how much you're making, am I right? 'Cause who wants to get audited by the IRS, am I right?

upvoted 0 times

...

Thurman

1 years ago

B) Equivalence partitioning - test with low, medium and high income.

upvoted 0 times

...

Leah

1 years ago

A) User story testing - test that the user can enter an income amount and get a result

upvoted 0 times

...

Kendra

1 years ago

I agree with Pearlie, testing with different income levels is crucial for accuracy.

upvoted 0 times

...

Domitila

1 years ago

I'm not sure Option C is the best choice here. Statement testing is more for unit testing, and this user story is more about the overall functionality.

upvoted 0 times

...

Beckie

1 years ago

Option B is the way to go! Equivalence partitioning is perfect for testing edge cases and making sure the tax calculation works across different income levels.

upvoted 0 times