CTAL-ATT Exam Dumps : Certified Tester Advanced Level Agile Technical Tester

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?

You are defining the test approach for an Agile project release which is to develop an improved user interface for a golf club's booking system plus some additional features that will provide more flexible bookings across the three courses The improvements have been primarily driven by customer complaints that the booking system is difficult to follow and restrictive The release will be divided into six two-week sprints

The stakeholders have performed a risk assessment for the release and have determined that whilst the system is not mission critical, customer business could be lost and thus a risk level of High has been agreed. As there is may be a high degree of change to the screen design and functionality across the sprints, a regression-averse strategy is recommended.

Which option in the table below represents the BEST test approach for this release, where the following symbols apply?

♦+ (highly recommended)

♦ (recommended)

o (neutral/optlonal)

• (not recommended)

- (not to be used)

OptionTest AutomationExploratory Testing(manual) Black-box testing

1♦+0♦♦

2-+♦+

3♦+0-

4♦♦♦♦

SELECT ONE OPTION

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?