Question 1

You are working on a project to develop an application that allows users to collaborate via bespoke, online whiteboards. The first release, delivering core functionality, highlighted misunderstandings of the user stories between testers, developers and the product owner during sprint development Since that release, the developers have agreed to implement a TDD approach for future software development. Creation of the product backlog for the second release is underway and you have recommended to the project stakeholders that an atdd approach be adopted for the backlog's user stories. What would be a GOOD REASON for making this recommendation? SELECT ONE OPTION

Options :

A : The team wants to start using BDD and therefore atdd must also be used

B : The test strategy states that automation shall be used to minimize effort for execution of acceptance tests

C :

TDD can only work effectively when an ATDD approach is used for the user stories use of attd examples will help address the misunderstandings encountered in release 1

Answer: C

Question 2

The result of a product risk analysis performed on components I, II and III

of the airplane control system shows the following risk matrix:

The project wants to mitigate the risks by defining different types of coverage depending on the risk level of

the components. Which of the following would be a meaningful solution for setting the coverage targets?

Options :

A :

I: Condition determination coverage, II: Decision Coverage, III: Statement coverage

B : I: Condition determination coverage, II: Statement coverage, III: Decision coverage

C : I: Decision coverage, II: Condition determination coverage, III: Statement Coverage

D : I: Multiple condition coverage, II: Decision coverage, III: Condition determination coverage

Answer: A

Question 3

Which of the following statements about fault seeding tools is correct?

Options :

A : Fault seeding tools insert defects into the source code to check the effectiveness of testing.

B :

Fault seeding tools insert defects into the source code to test the input checking capabilities of the software.

C :

Fault seeding tools insert defects into the source code to support the application of specification-based test design techniques.

D :

Fault seeding tools insert defects into the source code to check the level of maintainability of the software.

Answer: A

Question 4

Consider the pseudo code provided below:

Given the following tests, what additional test(s) (if any) would be needed in order to achieve 100% statement coverage, with the minimum number of tests? Test 1: A = 7, B = 7, Expected output: 7 Test 2: A = 7, B = 5, Expected output: 5

Options :

A : A=6, B=12, Expected output: Bingo! and A=7, B=9, Expected output: 7

B : A=6, B=12, Expected output: Bingo!

C : A=7, B=9, Expected output: 7

D : No additional test cases are needed to achieve 100% statement coverage.

Answer: D

Question 5

You have been assigned to perform a review on code provided below:

Which type of defect should you report as part of the code review?

Options :

A : Endless loop

B : Unreachable code

C : Too many nested levels

D : No defects should be reported, code is correct.

Answer: A