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

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

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

Consider an online application that allows registered users to pay the annual car tax based on the vehicle's engine power in kW. Given the following user story:

''As a customer I need the online application to calculate the annual car tax amount that I need to pay for my car":

- If the power of the vehicle is less than 20 kW, then the annual car tax is free

- If the power of the vehicle is more or equal than 20 kW but less or equal than 150 kW, then the annual car tax is 250 Euros

- If the power of the vehicle is more than 150 kW, then the annual car tax is 750 Euros"

What is the MOST suitable use of a black-box test design technique for this user story?

SELECT ONE OPTION

Show Suggested Answer Hide Answer
Suggested Answer: C

by Karl at Jun 23, 2024, 12:05 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Paulina
10 months ago
I just hope the online application has a user-friendly interface. Imagine having to input the power of your car in kilowatts - that could get confusing for some people!
upvoted 0 times
...
Lorean
10 months ago
Haha, I wonder if there's a special 'Lamborghini tax' for cars with over 1000 kW of power. That would really put a dent in your wallet!
upvoted 0 times
...
Adelle
10 months ago
I agree with Willodean. Equivalence Partitioning seems like the best option here, as it covers the different scenarios in a straightforward way.
upvoted 0 times
Stacey
9 months ago
D) Equivalence partitioning. Test the annual car tax value for the following partitions: [power of the vehicle<20 kW; 20 kW ?power of the vehicle?! 50 kW; power of the vehicle>150 kW]
upvoted 0 times
...
Kristian
9 months ago
C) Decision table testing. Test the following conditions: Conditions=registered user logged In; inserted power of the vehicle=20kW; Action=Car tax paid
upvoted 0 times
...
Chantell
10 months ago
B) Use case testing. Test the following use case (Actor=registered user): Pre-condition=registered user logged in Scenario=registered user inserts the power of the vehicle, making payment and logs out Post-condition=car tax paid and registered user logged out
upvoted 0 times
...
Amber
10 months ago
A) State transition testing. Test the transitions between the following states: logging In. inserting the power of the vehicle, making payment, logging out
upvoted 0 times
...
...
Margurite
11 months ago
I see your point, Gerald. Decision table testing could provide a clear structure to test the different conditions in the user story.
upvoted 0 times
...
Gerald
11 months ago
I think Decision table testing could also be a good option to test the conditions and actions for the user story.
upvoted 0 times
...
Julie
11 months ago
Decision table testing sounds good too. It would help us cover the different conditions and ensure the correct actions are taken for each case.
upvoted 0 times
...
Willodean
11 months ago
I think the most suitable test design technique would be Equivalence Partitioning. It allows us to test the different ranges of vehicle power and ensure the correct annual car tax is calculated for each one.
upvoted 0 times
Belen
9 months ago
D) Equivalence partitioning. Test the annual car tax value for the following partitions: [power of the vehicle<20 kW; 20 kW ?power of the vehicle?! 50 kW; power of the vehicle>150 kW]
upvoted 0 times
...
Francesco
9 months ago
B) Use case testing. Test the following use case (Actor=registered user): Pre-condition=registered user logged in Scenario=registered user inserts the power of the vehicle, making payment and logs out Post-condition=car tax paid and registered user logged out
upvoted 0 times
...
Eve
9 months ago
A) State transition testing. Test the transitions between the following states: logging In. inserting the power of the vehicle, making payment, logging out
upvoted 0 times
...
Kayleigh
10 months ago
D) Equivalence partitioning. Test the annual car tax value for the following partitions: [power of the vehicle<20 kW; 20 kW ?power of the vehicle?! 50 kW; power of the vehicle>150 kW]
upvoted 0 times
...
Willie
10 months ago
B) Use case testing. Test the following use case (Actor=registered user): Pre-condition=registered user logged in Scenario=registered user inserts the power of the vehicle, making payment and logs out Post-condition=car tax paid and registered user logged out
upvoted 0 times
...
Cherry
10 months ago
A) State transition testing. Test the transitions between the following states: logging In. inserting the power of the vehicle, making payment, logging out
upvoted 0 times
...
...
Sean
11 months ago
I agree with Ronnie. Equivalence partitioning seems like the best option to test the different partitions of power of the vehicle.
upvoted 0 times
...
Ronnie
11 months ago
I think the most suitable use of a black-box test design technique for this user story is Equivalence partitioning.
upvoted 0 times
...

Save Cancel