A.  

Detecting and isolating code quality problems early

B.  

Reducing the need of conducting retrospectives

C.  

Making quality everyone’s responsibility

D.  

Eliminating communication problems within the team

A.  

Kanban

B.  

Extreme Programming

C.  

Continuous Integration

D.  

Scrum

A.  

Conversation should include the acceptance criteria discussion.

B.  

The card should contain requirements not the user story.

C.  

Product owner has written a user story and confirmation is not needed.

D.  

The conversation is not required and the team should start developing.

A.  

Teams sometimes over-rely on unit tests and exclude some important system and acceptance tests.

B.  

Testers sometimes have too many builds to test, which reduces the quality of testing.

C.  

Teams no longer have the ability to run manual tests, as all tests must be automated.

D.  

Developer's workload is increased, which can result in a reduction of output.

A.  

Configuration management is a test management task that deals with developing and applying a set of corrective actions to get a test project on track when monitoring shows a deviation from what was planned

B.  

Configuration management represents a method for measuring and managing session-based testing, where a session is an uninterrupted period of testing which could last from 60 to 120 minutes

C.  

Configuration management consists of all of the test design techniques in which test cases are designed to execute all possible discrete combinations of any set of a specified number of configuration elements

D.  

Configuration management aims to identify and document some characteristics of a configuration item, control changes to those characteristics, and record and report change processing and implementation status

A.  

Resilient testing means that the testing process is capable of dealing with rapid changes throughout the development process with test plans being updated during each iteration.

B.  

Credibility means that the tester must share information with the stakeholders about the test process so that they find the selected test strategy and testing activities trustworthy.

C.  

Cross-functional teamwork means that all team members contribute to testing in various ways. For example, involving people with the test strategy, test planning and execution as well as test reporting.

D.  

Co-located teamwork means that all team members, including developers and testers, must sit together in the same office, so they can quickly communicate face-to-face.

A.  

During Agile retrospectives, testers should be encouraged to provide constructive suggestions only on non-testing activities.

B.  

In an Agile retrospective the moderator can encourage and make sure that good practices are kept by the team, by asking what the team is doing well.

C.  

Agile retrospectives should be focused mainly on impediments that are outside the control of the team because these issues are more challenging.

D.  

Unlike working sessions or meetings held in non-Agile projects, Agile retrospectives do not require follow-up activities.

A.  

Testers are fully embedded in each Agile team to perform many of the testing tasks.

B.  

Testers from an independent test team who do not get involved with the Agile team, but are assigned to do System Testing once all sprints are completed.

C.  

Testers from an independent test team are assigned on-demand for the final days of each sprint.

D.  

Testers from an independent test team are assigned to the Agile team at the beginning of the project, returning for re-assignment to a new agile team.

A.  

A way of developing software where the test cases are developed, and often automated, before the software to run those test cases has been written

B.  

A high-level description of the test levels to be performed and the testing within those levels for an organization or programme (one or more projects)

C.  

An approach to software development based on iterative incremental development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams

D.  

A way of testing software where test design and test execution occur at the same time, guided by a test charter during time-boxed testing sessions

A.  

Suggesting improvements in sprint retrospectives

B.  

Coaching other team members in self-organization and cross-functionality

C.  

Removing impediments to the Scrum team’s progress

D.  

Prioritizing the items in the product backlog

A.  

The test pyramid concept is based on the principle of eliminating defects as early as possible in the software lifecycle

B.  

The test pyramid emphasizes having more automated tests at the higher test levels and a decreasing number of them at the lower test levels

C.  

The test pyramid concept states that every software system consists always of four different test levels (unit, integration, system, acceptance)

D.  

The test pyramid consists of four test levels with business-facing tests at the bottom of the pyramid and technology-facing tests at the top

A.  

The build process was slow and this often caused delays waiting for the build to complete.

B.  

For the last sprint the estimated and actual effort were much higher than the team capacity.

C.  

The automation tests failed frequently without any logs to help in debugging the failure reason.

D.  

One of the testers was regarded as being both disruptive and lazy and did not contribute to team success.

A.  

Each of the four testing quadrants (Q1, Q2, Q3, and Q4) represents a different test level (Q1 = Unit, Q2 = Integration, Q3 = System, and Q4 = Acceptance) and describes the different test types that shall be performed by Agile teams in that test level for an Agile project

B.  

Each of the four testing quadrants (Q1, Q2, Q3, and Q4) contains different test types and test levels, and these quadrants are numbered to describe the order in which the associated test types and test levels shall be performed in an Agile project (Q1 first, Q4 last)

C.  

Each of the four testing quadrants (Q1, Q2, Q3, and Q4) contains different test types and test levels, and these quadrants can be used by Agile teams and other stakeholders to ensure that all important test types and test levels are included in an Agile project

D.  

Each of the four testing quadrants (Q1, Q2, Q3, and Q4) contains different test types and test levels, and these quadrants are numbered to describe the risk level associated with the test types (Q1 = least risky, Q4 = most risky)

A.  

It provides detailed visual representation of the whole team's status.

B.  

It is updated once at the end of each iteration.

C.  

Only “in progress” tasks are shown on the task board.

D.  

It is a detailed visual representation of the status of testing.

A.  

Communication, simplicity, feedback, courage, and respect are the five fundamental values of Kanban to guide development

B.  

Scrum does not provide guidance on how development has to be done in a Scrum project but prescribes the adoption of specific testing techniques

C.  

In Kanban, transparency of content and progress of tasks is usually done with the visualization of the active tasks, for example on a public whiteboard

D.  

Scrum is an Agile management framework that defines three roles: the Scrum Owner, the Product Master, and the Development Team

A.  

Tests to check that payments with insufficient credit charged on the smartcard are successful

B.  

Tests to check that payments with sufficient credit charged on the smartcard are given five percent discount are successful

C.  

Tests to check that payments with expired credit cards of supported credit card types are unsuccessful

D.  

Tests to check that payments with no credit charged on the smartcard will be unsuccessful

A.  

Team B estimates that the user story can be "done" with significantly less effort in absolute terms than what was estimated by Team A

B.  

Team A has a better estimation process than Team B because at the end of the last round, all five team members’ estimates are an exact match

C.  

In the estimation process, Team B, unlike Team A, can take advantage of the discussions that represent an important benefit of using Planning Poker

D.  

Both Team A and B have an ineffective estimation process because the best estimate is the average of the results of the first round of estimation

A.  

Enables reduction in test duplication as the testers and test engineers function as a single team.

B.  

Enables testers to execute their responsibility for quality for the combined team.

C.  

Enables the team to focus on solely their separate areas of expertise and responsibility.

D.  

Enables the various skill sets within the team to be leveraged to the benefit of the project.

A.  

Tools that generate data to populate an application’s database

B.  

Continuous integration and build distribution tools

C.  

Application lifecycle management (ALM) and task management tools

D.  

Tools that capture and log activities performed on an application during its use

A.  

3, 4

B.  

2, 5

C.  

1, 3

D.  

2, 3

A.  

The solution shall support business processes.

B.  

The system shall be easy to use.

C.  

The response time to confirm a customer submission must not exceed 5 seconds.

D.  

The tools for testing are tested before use and are meeting the requirements.

A.  

Design-Driven Development

B.  

Behavior-Driven Development

C.  

Test-Driven Development

D.  

Acceptance Test-Driven Development

A.  

Test-driven development means that existing functionality is not considered.

B.  

Test automation can cause regression of software in the test environment.

C.  

Regression is built into software as a safeguard against unexpected failures.

D.  

There is code churn due to change in business needs over several sprints.

A.  

Decision table testing. Test the following conditions:

Conditions=registered user logged in; inserted power of the vehicle=20kW;

Action=Car tax paid

B.  

State transition testing. Test the transitions between the following states:

logging in, inserting the power of the vehicle, making payment, logging out.

C.  

Equivalence partitioning. Test the annual car tax value for the following partitions:

[power of the vehicle<20 kW ; 20 kW ≤power of the vehicles≤150 kW; power of the vehicle>150 kW]

D.  

Use case testing

Test the following use case (Actor=registered user):

Pre-condition=registered user logged in

Scenario=registered user inserts the power of the vehicle, making payment and logs out

Post-condition=car tax paid and registered user logged out