A.  

a defect is fixed and after other tests do not find any side-effect introduced in the software as a result of such fix

B.  

a failed test, and aims to run that test again to confirm that the same behavior still occurs and thus appears to be reproducible

C.  

the execution of an automated regression test suite to confirm the absence of false positives in the test results

D.  

a defect is fixed, and if such testing is successful then the regression tests that are relevant for such fix can be executed

A.  

are often written in a rule-oriented format using the template referred to as "Given/When/Then"

B.  

are often documented following in rule-oriented format using the following template: "As a [role], I want [feature], so that I can [benefit]"

C.  

can be written in different formats and represent an aspect of a user story referred to as confirmation' of the so called "3 C's"

D.  

must be written in one of the two following formats: scenario-oriented or rule-oriented

A.  

The diagnostic tests fail to start after a system reset

B.  

The diagnostic tests take too much time to execute

C.  

The diagnostic tests that measure the speed of the memory, fail

D.  

The diagnostic tests fail due to incorrect implementation of the test code

A.  

promotes the idea that all team members should have a thorough understanding of test techniques

B.  

is a consensus-based approach that engages the whole team in estimating the user stories

C.  

promotes the idea that all team members should be responsible for the quality of the product

D.  

is mostly adopted in projects aimed at developing safety-critical systems, as it ensures the highest level of testing independence

A.  

The logged-in user enters a wrong current password and views the dedicated error message

B.  

The logged-in user enters the correct current password, enters a valid new password (different from the last 5 passwords), presses the Change Password' button, and finally receives the e-mail confirming that the password has been successfully changed

C.  

The logged-in user enters the correct current password, enters an invalid password, and finally views the dedicated error

D.  

The logged-in user submits a purchase order containing ten items, selects to pay with a Visa credit card, enters credit card information of a valid card, presses the 'Confirm' button, and finally views the dedicated message confirming that the purchase has been successful

A.  

demonstrate the absence of defects

B.  

produce tests that are less subject to human errors

C.  

avoid performing exploratory testing

D.  

increase test process efficiency by facilitating management of defects

A.  

Achieving full statement coverage and full branch coverage for a software product means that such software product has been fully tested and there are no remaining bugs within the code

B.  

Code-related white-box test techniques are not required to measure the actual code coverage achieved by black-box testing, as code coverage can be measured using the coverage criteria associated with black-box test techniques

C.  

Branch coverage is the most thorough code-related white-box test technique, and therefore applicable standards prescribe achieving full branch coverage at the highest safety levels for safety-critical systems

D.  

Code-related white-box test techniques provide an objective measure of coverage and can be used to complement black-box test techniques to increase confidence in the code

A.  

A test leader writes a test summary report

B.  

A project manager asks to a test leader to estimate the test effort

C.  

A tester installs a test ten in the lest environment

D.  

A tester finds a bug which is resolved prior to release

A.  

A defect does not always produce a failure, while a bug always produces a failure

B.  

A defect may cause a failure which, when occurring, always causes an error

C.  

Failures can be caused by defects, but also by environmental conditions

D.  

Bugs are defects found during component testing, while failures are defects found at higher test levels

A.  

Be able to apply test-driven development

B.  

Be able to use test management tools and defect tracking tools

C.  

Be able to communicate defects and failures to developers as objectively as possible

D.  

Possess the necessary social skills that support effective teamwork

A.  

You should open a defect report providing detailed information on which devices and by running which tests you observed the issue

B.  

The issue is related to performance efficiency, not functionality. Thus, as a functional tester, you should not open any defect report as all the functional tests passed

C.  

You should not open any defect report as the problem is most likely due to poor hardware equipment on the devices where you observed the issue

D.  

You should not open any defect report and inform the test manager that the devices on which you observed the issue should no longer be supported so that they will be removed from the requirements specification

A.  

Test design specification

B.  

Project plan

C.  

Requirements specification

D.  

Test plan

A.  

Test monitoring and control

B.  

Test implementation

C.  

Test design

D.  

Test analysis

A.  

S0->S1->S2->S3->S5->S1

B.  

S0->S1->S2->S3->S5->S1->S2->S3

C.  

S0->S1->S2~>S3->S4

D.  

S0->S1 ->S2->S3->S5->S3->S4

A.  

Very low MTBF (Mean Time Between failure)

B.  

Potentially endless loops

C.  

Referencing a variable with an undefined value

D.  

Security vulnerabilities

A.  

The additional effort spent on test execution compared to what was planned

B.  

The unexpected test environment downtime that resulted in slower test execution

C.  

The residual risk level if a risk-based test approach was adopted

D.  

The test procedures of all test cases that have been executed

A.  

TC1 = 81 k€; TC2= 97k€; TC3=111k€; TC4=118k€

B.  

TC1 = 40k€; TC2= 46k€; TC3=51k€; TC4=53k€

C.  

TC1 = 79k€; TC2= 80k€; TC3=81k€; TC4=82k€

D.  

TC1 = 90k€; TC2= 110k€; TC3=125k€: TC4=140k€

A.  

Static techniques can be used before all code is ready for execution

B.  

Static techniques find more detects then dynamic techniques.

C.  

Static techniques can be used by inexperienced users.

D.  

Static techniques are always cheaper than dynamic techniques.

A.  

Get familiar with the functionality and options of the tool

B.  

Check haw the tool fits to the existing test processes

C.  

Train all testers on using the tool

D.  

Decide upon standards for tool implementation

A.  

Test plans

B.  

Source code

C.  

Compiled code

D.  

Formal models

A.  

Determining the people who will be involved in the review

B.  

Recording the anomalies found during the review meeting

C.  

Identifying potential anomalies in the work product under review

D.  

Fixing the anomalies found in the work product under review