Which one of the following Keyword-driven input tables provides the BEST test coverage of this enhancement?
As a vehicle driver -
I want to be able to pre-book a car parking space online, selecting a disabled driver's space if needed
So that I can pay in advance and receive confirmation of my parking space number.
The following acceptance criteria have also been written:
Payment can be made via PayPal, Debit or Credit Card.
Confirmation of payment and car parking details should be sent after the booking process is completed.
Driver information is stored in the reservation database.
The database has been built and tested in a previous sprint, but the interface to the different payment methods have yet to be developed.
As a tester in an agile team, you have been asked to review the user story. You have detected some issues with this story:
It needs to cater for different user groups: a driver or disabled driver.
It needs to cater for different vehicle types: a car, 4x4, van or motorbike.
There are no acceptance criteria relating to how quick the booking process should be.
How confirmation is to be sent for payment and space number, and other important details, have not been specified.
A stub will be needed to test the payment method.
Which pair of requirements engineering techniques are you MOST LIKELY to have used to uncover these issues?
As a Purchasing Manager -
I want to see a list of all Purchase Orders placed so far this month with their total value
So that I can control the amount of money being spent.
Which scenario is BOTH written in correct Gherkin format AND is appropriate for this User Story?
Continuous Integration has been implemented and technically it is working well, running several times per day, but each run is taking almost as much time as the team is prepared to allow.
It is clear that after a few more iterations, as the number of tests needed grows with the product, it will be taking too much time.
Which of the four options contains a pair of solutions that will BOTH help to solve this problem?
Only include unit and component integration tests in the automated CI runs.
Schedule low priority tests to be the first ones executed in each run, in order to provide rapid build verification.
Reduce the extent to which the automated tests go through the user interface, using technical interfaces instead.
Reduce the number of CI cycles run each day.
Select a subset of automated tests for the daytime CI runs, and run as many of the other tests as possible in an overnight cycle.
Which statement contains a pair of benefits that can BOTH be expected from service virtualization in this circumstance?