iSQI Related Exams
CTAL-ATT Exam
The following user story has been written for a new application being developed to pre-book a space at a National Car Park.
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 l 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:
1.it needs to cater for different user groups: a driver or disabled driver
2.it needs to cater for different vehicle types: a car. 4x4. van or motorbike
3.There are no acceptance criteria relating to how quick the booking process should be
4.How confirmation is to be sent for payment and space number, and other important details, have not been specified
5.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’
SELECT ONE OPTION
You have been working as a tester in an Agile team You have found that the user stories are being defined by the team but it is still unclear what will be a successful outcome Even after story elaboration you are still unclear as to what a story should do As a result, you're not really sure what to test or to know when you'll be done with testing This problem is becoming worse as completed stories are showcased but the product owner is unhappy with the results
You've looked into the matter further and the comments from the product owner indicate that features are missing from the stories. The story is functioning correctly within the limited definition of the story but the product owner is expecting more functionality, such as error handling that isn't being defined in the story
What technique should you implement that would help to further define the product owner's expectations and alleviate the issues that are arising during the show cases?
When using a process-compliant approach to testing a safety-critical project, what is an important aspect of test automation?