Question 1

What is the characteristic of a unit test that makes it “atomic”?

Options :

A : If it is run with the same conditions, it will get the same result each time

B : It tests the details of the code, including verifying all the possible areas of data handling

C : It tests only the targeted piece of functionality

D : It runs very fast, allowing many tests to be run quickly

Answer: C

Question 2

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?

Options :

A : TDD by the developers before they begin coding

B : BDD by the developers when unit tests are being created

C : ATDD by the team to better define the requirements

D : A combination of TDD and BDD by the team to improve the pre-build testing

Answer: C

Question 3

What are the characteristics of a unit test that are defined with the acronym FIRST?

Options :

A : Fast, Iterative, Replaceable, Stable, Tolerant

B : Fast, Isolated, Repeatable, Self-validating, Thorough

C : Fast, Implemented, Recorded, Source-controlled, Tactical

D : Fast, Immediate, Relevant, Standardized, Transparent

Answer: B

Question 4

Which of the following is an expected benefit of using storyboards to help analyze user stories and epics?

Options :

A : They help to identify the different types of users who will use that piece of functionality

B : They help to ensure adequate user group coverage in testing

C : They help to expose stakeholders or groups of stakeholders who might have been forgotten

D : They help to visualize stories to help categorize them into areas of functionality

Answer: D

Question 5

You are an experienced tester on an Agile team that is producing a new application. The product backlog has been refined sufficiently to begin development for the first release. This stories in this backlog contain a mixture of functional and non-functional requirements, as well as some technical stories that will provide elements of the application's infrastructure The developers have decided to use TDD as a deveiopment approach but automation of the acceptance tests is not yet planned. You have been asked to recommend whether or not the team should take an atdd approach as well as TDD. what would be the BEST recommendation in these circumstances? SELECT ONE OPTION

Options :

A :

YES. use attd, but for the functional requirements only because it cannot be applied to non-functional or technical requirements

B :

YES. use attd, but for the functional requirements only because it cannot be applied to non-functional or technical requirements

C : NO. do not use ATDD, because it will not work when the acceptance tests are not automated

D :

NO. do not use atdd. because it is not compatible with the developers' TDD approach.

Answer: B

Confidently Practice Online with Free CTAL-ATT Exam Cram

Buying Options: