QuestionQ40

Agile Testing Methods, Techniques and Tools

Consider an online application that enables registered users to pay annual car tax according to a vehicle’s engine power in kW. Given this user story:

“As a customer, I need the online application to calculate the annual car tax amount I must pay for my car:

  • If the vehicle power is less than 20 kW, the annual car tax is free.
  • If the vehicle power is greater than or equal to 20 kW but less than or equal to 150 kW, the annual car tax is 250 Euros.
  • If the vehicle power is greater than 150 kW, the annual car tax is 750 Euros.”

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

  • A Decision table testing. Test the following conditions:Conditions=registered user logged in; inserted power of the vehicle=20kW;Action=Car tax paid
  • B State transition testing. Test the transitions between the following states: logging in, inserting the power of the vehicle, making payment, logging out.
  • C Equivalence partitioning. Test the annual car tax value for the following partitions:[power of the vehicle<20 kW ; 20 kW ≤power of the vehicles≤150 kW; power of the vehicle>150 kW]
  • D Use case testing -Test the following use case (Actor=registered user):Pre-condition=registered user logged inScenario=registered user inserts the power of the vehicle, making payment and logs outPost-condition=car tax paid and registered user logged out
Explanation

Equivalence partitioning divides the vehicle-power input into classes that are expected to produce the same result: below 20 kW, from 20 kW through 150 kW, and above 150 kW. Testing representative values from these partitions verifies the applicable annual tax for each range.

Community Discussion

No comments yet. Be the first to start the discussion!