Question 1

A unit test should be deterministic. Which option correctly describes the meaning of 'deterministic' as a characteristic of a unit test9 SELECT ONE OPTION

Options :

A : It should be small so that many tests can be run in a short period of time

B : Whenever it is run under the same conditions, it should produce the same results.

C : it should not depend on any other test.

D : It should only test the functionality related to it.

Answer: B

Question 2

Using your knowledge of requirements engineering, which of the following activities would assist the team the most in determining which stories they should commit to in the first sprint?

Options :

A : Create personas for a Business Traveler, a Vacationer, and a Senior Citizen

B : Develop a user story map for this segment of the application

C : Consult with a Usability Expert on the set of colors and fonts to use for this screen

D : Create a state transition diagram and other UML artifacts

Answer: B

Question 3

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 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 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

Confidently Practice Online with Free CTAL-ATT Exam Cram

Buying Options: