Refactoring of test cases is needed in agile projects for many reasons.
Which of the following statements about the refactoring of test cases is correct?
As a tester on an Agile team you have been given the following user story to analyze
As a medical professional
I want to see the availability of operating rooms
So I can schedule surgeries as needed
You have talked with the product owner and she expressed some concern over the term "medical professional" You have looked into this and found that doctors want to schedule their surgeries but the hospital administrator does not want them to have this ability At this point what should you do to try to resolve this issue?
A developer has implemented a class that calculates if a given date is a leap year. The definition
for the leap year is given:
Every year that is exactly divisible by four is a leap year, except for years that are exactly
divisible by 100, but these centurial years are leap years if they are exactly divisible by 400.
- divisible by 4
- but not by 100
- years divisible by 400 are leap anyway
You have already thought about it and started with the first test class; the test class looks like
(pseudo JavaScript used here):
// LeapYear.spec.js
describe('Leap year calculator', () => {
it('should consider 1996 as leap', () => {
expect(LeapYear.isLeap(1996)).toBe(true);
});
});
What would now be your next step to proceed as efficient as possible, to validate the correctness
of the class above?
Which of the following statements about performing exploratory testing with test charters is
correct?
You have received this BDD test
Given that a customer enters the correct PIN When they request to make a withdrawal And they have enough money in their account Then they will receive the money And a receipt
Which of the following is the user story that best fits this BDD test?
Whose perspective should be used when a user story is created?
You are testing a large e-commerce system for household goods that is being implemented using Agile methodologies You are currently working on deriving tests tor stories that are implementing the following epic.
As a customer I want to use the e-commerce system, so that I can have my purchased goods delivered to my house.
The story you are currently working on is
As a customer I want to be told how many items I need to purchase, so I can receive free shipping
Which of the following is an appropriate test charter for this story?
You have been working to define acceptance tests for a story. You think this will help tailor your testing. You have asked the product owner to be involved as well. You are currently looking at this story:
As a pet owner
I want to purchase food online
So that it can be delivered to my house when I need it
Which of the following is the preferred way to solicit information from the product owner to better understand what will be "acceptable?
An increased proportion of automated test coverage often leads to a greater degree of manual
testing that follows reactive strategies, because:
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?
