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.  

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

A.  

Each layer of the test pyramid groups tests related to a single non-functional quality characteristic

B.  

The higher the layer of the test pyramid, the more production code a single automated test within the layer tends tocover

C.  

The higher the layer of the test pyramid, the more maintainable a single automated test within the layer tends to be

D.  

The higher the layer of the test pyramid, the more isolated a single automated test within the layer tends to be

A.  

This test quadrant contains smoke tests and non-functional tests (except usability tests). These tests are often automated.

B.  

This test quadrant is business-facing and criticizes the system. It contains exploratory testing, usability testing, and user acceptance testing.

C.  

This test quadrant contains functional tests, examples, user story tests, user experience prototypes, API testing, and simulations. These tests check the acceptance criteria and can be manual or automated.

D.  

This test quadrant is technology-facing and supports the team. These tests should be automated and included in the continuous integration (CI) process.

A.  

Black-box testing techniques are based on experience with the test object without knowing the internal structure.

B.  

In black-box testing techniques, test cases are created based on the software's implementation.

C.  

Black-box testing techniques are based on analyzing the test object's specified and implied behavior without knowledge of its internal data structure.

D.  

Black-box testing techniques involve analyzing the specified behavior of the test object without knowledge of its internal structure.

A.  

not usually included in a test plan, and therefore in the given test plan it should not be specified neither within the three sections mentioned, nor within the others

B.  

usually included in a test plan and, in the given test plan, it is more likely to be specified within "Test Scope" rather than in the other two sections mentioned

C.  

usually included in a test plan and, in the given test plan, it is more likely to be specified within "Testing Communication" rather than in the other two sections mentioned

D.  

usually included in a test plan and, in the given test plan, it is more likely to be specified within "Stakeholders" rather than in the other two sections mentioned

A.  

NORMAL MODE → DIAGNOSTIC MODE → NORMAL MODE → EMERGENCY MODE → DIAGNOSTIC MODE → NORMAL MODE

B.  

NORMAL MODE → DIAGNOSTIC MODE → DEGRADED MODE → EMERGENCY MODE → DIAGNOSTIC MODE → NORMAL MODE → DEGRADED MODE

C.  

NORMAL MODE → DIAGNOSTIC MODE → DEGRADED MODE → EMERGENCY MODE → DIAGNOSTIC MODE → NORMAL MODE → DIAGNOSTIC MODE

D.  

NORMAL MODE → DEGRADED MODE → NORMAL MODE → DIAGNOSTIC MODE → DEGRADED MODE → EMERGENCY MODE → DIAGNOSTIC MODE

A.  

750 person-days

B.  

180 person-days

C.  

720 person-days

D.  

270 person-days

A.  

Effectiveness depends on the individual testers' skills

B.  

Usually conducted when there is sufficient time for testing

C.  

Test cases are written once the specifications become available

D.  

Testing without defined time-boxes

A.  

Yes. Spending too much money on test ng will result in an unprofitable product, and having cost as an exit criterion helps avoid this

B.  

No. The financial value of product quality cannot be estimated, so it is incorrect to use cost as an exit criterion

C.  

Yes. Going by cost as an exit criterion constrains the testing project which will hello achieve the desired quality level defined for the project

D.  

No The cost of testing cannot be measured effectively, so it is incorrect to use cost as an exit criterion

A.  

The belief that thoroughly testing all requirements guarantees system success.

B.  

The need for constant system quality assurance and improvements.

C.  

A misconception that software verification is unnecessary

D.  

The idea that fixing defects is NOT important to meeting user needs.

A.  

Statements I, III, and IV

B.  

Statements II, IV, and V

C.  

Statements I, II, and IV

D.  

Statements II, III, and V

A.  

II, IV

B.  

I, II

C.  

IV, V

D.  

II, III, IV

A.  

Where a developer and a tester work together on the same workstation: while the developer actively writes code, the tester explores the code to find defects

B.  

That can be organized into sessions guided by test charters outlining test objectives that will guide the testers' exploration

C.  

Where a team of testers explores all possible test techniques in order to determine the most suitable combination of these techniques to apply for a test project

D.  

That aims at finding defects by designing tests that exercise all possible combinations of input values and preconditions

A.  

Testing if e-commerce website works correctly with a third-party payment gateway

B.  

Testing the system based on specifications using simulator for a sub-system

C.  

Testing an application in development environment which is similar to the production environment

D.  

Testing an application's behaviour to check if it fulfils business needs

A.  

Exploratory tests are generally used for this quadrant

B.  

It is the quadrant that Non-functional testing such as performance and the tests are created on the basis of user scenarios

C.  

It is the quadrant that component testing.

D.  

It is the quadrant that deals with tests created on the basis of user stories.

A.  

The purpose of confirmation testing is to confirm that the defect giving rise to a failure has been successfully fixed. The regression test aims to ensure that no defects have been introduced or discovered in unmodified areas of the software as a result of the changes made.

B.  

Confirmation testing ensures the entire system functions as expected, whereas regression testing focuses only on modified components.

C.  

Confirmation testing verifies all system requirements, while regression testing ensures that no additional test cases are needed.

D.  

Regression testing and confirmation testing are interchangeable and serve the same purpose.

A.  

Test planning and control, Test analysis and design, Test implementation and execution, Evaluating ex t criteria and reporting. Test closure activities

B.  

Test planning, Test analysis and design. Test implementation and control. Checking test coverage and reporting, Test closure activities

C.  

Test planning and control, Test specification and design. Test implementation and execution, Evaluating test coverage and reporting, Retesting and regression testing, Test closure activities

D.  

Test planning. Test specification and design. Test implementation and execution. Evaluating exit criteria and reporting. Retesting and test closure activities

A.  

The shift-left approach can only be implemented with test automation

B.  

The shift-left approach in testing is compatible with DevOps practices

C.  

The shift-left approach can involve security vulnerabilities

D.  

The shift-left approach can be supported by static analysis tools

A.  

Performing non-functional testing starting at the system test level.

B.  

Conducting non-functional testing exclusively at the acceptance test level.

C.  

Limiting non-functional testing to security testing and performance testing only.

D.  

Ensuring non-functional testing focuses only on user experience and usability.

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.  

Static testing can benefit from using code-related white-box test techniques during code reviews

B.  

White-box testing allows suggesting test cases for increasing coverage levels which are based on objective measures

C.  

Achieving full code coverage for a component or a system ensures that it has been fully tested

D.  

Black-box testing can benefit from using code-related white-box test techniques to increase confidence in the code

A.  

Retirement testing

B.  

System integration testing

C.  

Beta testing

D.  

Maintenance testing

A.  

skill and staff shortages; problems in defining the right requirements, contractual issues.

B.  

skill and staff shortages; software does not perform its intended functions; problems in defining the right requirements.

C.  

problems in defining the right requirements; contractual issues; poor software quality characteristics.

D.  

poor software quality characteristics; software does not perform its intended functions.

A.  

Acceptance criteria 8 has not been fully covered during the above test cycle.

B.  

Acceptance criteria 4 has not been fully covered during the above test cycle.

C.  

All acceptance criteria have been fully covered during the above test cycle.

D.  

Acceptance criteria 6 has not been fully covered during the above test cycle.

A.  

Only developers and testers should be involved in retrospectives, as involving people in other roles is very likely to prevent developers and testers from having open and constructive discussions that really help identify process improvements

B.  

Retrospectives can be very effective in identifying process improvements and can also be very efficient and cost-effective especially since, unlike reviews, they do not require any follow-up activities

C.  

On Agile projects, well-conducted retrospectives at the end of each iteration can help the team reduce and sometimes even eliminate the need for daily stand-up meetings

D.  

During retrospectives, in addition to identifying relevant process improvements, participants should also consider how to implement these improvements and retain them based on the context of the project, such as the software development lifecycle

A.  

Code coverage

B.  

Data flow coverage

C.  

Statement coverage

D.  

Branch Coverage

A.  

run faster than the tests at the top layer of the pyramid

B.  

cover larger pieces of functionalities than the tests at the top layer of the pyramid

C.  

are defined as 'Ul Tests' or 'End-To-End tests' in the different models of the pyramid

D.  

are unscripted tests produced by experience-based test techniques

A.  

Option A

B.  

Option B

C.  

Option C

D.  

Option D

A.  

In statement testing, the coverage items are control flow transfers between branches. The aim is to design test cases to exercise branches in the code until an acceptable level of coverage is achieved, expressed as a percentage.

B.  

In statement testing, the coverage items are decisions and statements. The aim is to design test cases that exercise statements in the code until an acceptable level of coverage is achieved, expressed as a percentage.

C.  

In statement testing, the coverage items are branches, and the aim is to design test cases to exercise branches in the code until an acceptable level of coverage is achieved, expressed as a percentage.

D.  

In statement testing, the coverage items are executable statements. The aim is to design test cases that exercise statements in the code until an acceptable level of coverage is achieved, expressed as a percentage.

A.  

i, ii and iii are characteristics of sequential models; iv and v are characteristicsof iterativeandincrementalmodels

B.  

i and iv are characteristics of sequential models;ii, iii and varecharacteristicsof iterativeandincrementalmodels

C.  

ii and iv are characteristics of sequential models;i, iii and varecharacteristicsof iterativeandincrementalmodels

D.  

iii and iv are characteristics of sequential modelsand i, ii and v are characteristics of iterative and incremental models

A.  

Review leader

B.  

Facilitator

C.  

Recorder

D.  

Moderator

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.  

It helps avoid the risk of tasks associated with a user story not moving through the Agile task board at an acceptable rate during an iteration

B.  

It helps team members understand the current status of an iteration by visualizing the amount of work left to do compared to the time allotted for the iteration

C.  

It helps the whole team be more effective in test case design by requiring all team members to master all types of test techniques

D.  

It helps team members develop better relationships with each other and make their collaboration more effective for the benefit of the project

A.  

All participants to the review will be evaluated based on the defects they will find

B.  

The author of the work product to be reviewed leads the review meeting

C.  

All participants to the review are trained to deal with the review type and its objectives

D.  

Review metrics must be collected to improve the review process

A.  

Confirmation testing aims to confirm that the observed failure is not a false positive. The regression test aims to ensure that no defects have been introduced or discovered in unmodified areas of the software as a result of the changes made.

B.  

The purpose of confirmation testing is to confirm that the defect giving rise to a failure has been successfully fixed. The regression test aims to ensure that no defects have been introduced or discovered in unmodified areas of the software as a result of the changes made.

C.  

The purpose of confirmation testing is to confirm that the defect giving rise to a failure has been satisfactorily fixed. The regression test aims to ensure that no defects have been introduced or discovered in modified areas of the software as a result of the changes made.

D.  

The purpose of regression testing is to confirm that the defect giving rise to a failure has been satisfactorily resolved. The purpose of the confirmation testing is to ensure that no defects have been introduced or discovered in unmodified areas of the software as a result of the changes made.

A.  

Column 7 represents an impossible situation and thus can be deleted

B.  

Columns 1 and 3 can be merged into a single column

C.  

Columns 2, 4. 6 and 8 can be merged into a single column

D.  

Columns 5 and 7 can be merged into a single column

A.  

Q1

B.  

Q2

C.  

Q3

D.  

Q4

A.  

Reduced test execution times

B.  

More objective assessment

C.  

Prevention of simple human errors

D.  

Eliminating completely the need for manual testing

A.  

Experience-based test techniques rely on the experience of testers to identify the root causes of defects found by black-box test techniques

B.  

Some of the most common test basis used by white-box test techniques include user stories, use cases and business processes

C.  

Experience-based test techniques are often useful to detect hidden defects that have not been targeted by black-box test techniques

D.  

The primary goal of experience-based test techniques is to design test cases that can be easily automated using a GUI-based test automation tool

A.  

Determining the test strategy

B.  

Participating in the detailed risk analysis of user stories and determining their testability

C.  

Planning the testing for the release

D.  

Writing testable user stories and acceptance criteria

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.  

test design

B.  

test analysis

C.  

test implementation

D.  

test monitoring and control

A.  

test execution

B.  

test design

C.  

test analysis

D.  

test planning

A.  

The budget and schedule for the test project.

B.  

A detailed analysis of the defects found and their causes.

C.  

A detailed report on the test results after the test project is completed.

D.  

A list of test logs from the test execution.

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.  

It is a product risk since any risk associated with development timeline is a product risk.

B.  

It is no longer a risk for the Test Manager since an independent party (the sub-contractor) is now managing it

C.  

It is a object risk since successful completion of the object depends on successful and timely completion of the tests

D.  

It is a product risk since default on part of the sub-contractor may lead to delay in release of the product

A.  

Traceability between test basis items and thetest casesdesigned tocover them,makes it possible to determine which test basis items have been covered by the executedtest cases

B.  

Traceability between test basis items and thetest casesdesigned tocover them,enablesexperience-based test techniques to be applied

C.  

Traceability between test basis items and thetest casesdesigned tocover them,enablesidentification of which test cases will be affected by changes to the test basisitems

D.  

Traceability can be established and maintained throughall test documentation for a giventest level, such as from test conditions through test cases to test scripts

A.  

NORMAL MODE → DIAGNOSTIC MODE → DEGRADED MODE → EMERGENCY MODE → DIAGNOSTIC MODE → NORMAL MODE → DIAGNOSTIC MODE

B.  

NORMAL MODE → DEGRADED MODE → NORMAL MODE → DIAGNOSTIC MODE → DEGRADED MODE → EMERGENCY MODE → DIAGNOSTIC MODE

C.  

NORMAL MODE → DIAGNOSTIC MODE → DEGRADED MODE → EMERGENCY MODE → DIAGNOSTIC MODE → NORMAL MODE → DEGRADED MODE

D.  

NORMAL MODE → DIAGNOSTIC MODE → NORMAL MODE → DIAGNOSTIC MODE → EMERGENCY MODE → DIAGNOSTIC MODE → NORMAL MODE

A.  

20

B.  

180

C.  

197

D.  

120

A.  

Testing the software under test (SUT) based on the design is black-box testing whereas testing the input-output behaviour is experience based testing.

B.  

Testing the software under test (SUT) is possible only after implementation in white-box testing whereas testing the software even before implementation is possible in exploratory testing.

C.  

Testing the software under test (SUT) using knowledge of the tester is experience based testing whereas testing the specification based behaviour without pre-written test cases is using black-box testing techniques.

D.  

Testing based on the structure of the software under test (SUT) is white-box testing whereas testing the input-output behaviour without pre-written test cases is experience based testing.

A.  

TC4, TC3, TC2, TC6, TC5. TC1

B.  

TC4, TC6, TC3, TC2, TC5, TC1

C.  

TC3, TC5, TC6, TC1, TC4, TC3

D.  

TC4, TC3, TC2, TC6, TC1, TC5

A.  

Shift-left in testing can be implemented only in Agile/DevOps frameworks, as it relies completely on automated testing activities performed within a continuous integration process

B.  

Performance testing performed during component testing, is a form of shift-left in testing that avoids planning and executing costly end-to-end testing at the system test level in a production-like environment

C.  

Shift-left in testing can be implemented in several ways to find functional defects early in the lifecycle, but it cannot be relied upon to find defects associated with non-functional characteristics

D.  

Continuous integration supports shift-left in testing as it can reduce the time between the introduction of a defect and its detection, thereby reducing the cost to fix it

A.  

Test design

B.  

Test analysis

C.  

Test implementation

D.  

Test execution

A.  

Acceptance criteria 8 has not been fully covered during the above test cycle.

B.  

Acceptance criteria 6 has not been fully covered during the above test cycle.

C.  

Acceptance criteria 4 has not been fully covered during the above test cycle.

D.  

All acceptance criteria have been fully covered during the above test cycle.

A.  

Product owner, development, and testing

B.  

Business, architecture, and testing

C.  

Business, development, and testing

D.  

Business, development, and acceptance testing

A.  

Team bonding and learning

B.  

Increased test effectiveness/efficiency

C.  

Improved quality of the test basis

D.  

Better cooperation between development and testing

... and the list of possible characteristics of retrospectives (1 to 4) that enable achieving these benefits:

The possibility of implementing suggestions for process improvement

The opportunity to raise problems and propose points for improvement

The regular review and optimization of the collaboration between team members

The possibility of addressing and solv

E.  

A1 - B4 - C3 - D2

F.  

A2 - B1 - C4 - D3

G.  

A4 - B3 - C2 - D1

A.  

Accuracy and usability of a new Navigation system compared with previous system

B.  

A billing system used to calculate monthly charge based or large number of subscribers parameters

C.  

The ability of an Anti virus package to detect and quarantine a new threat

D.  

Suitability and performance of a Multi media (audio video based) system to a new operating system

A.  

Testing triggers a failure that is caused by a defect in the software, whereas debugging is concerned with finding the causes of this failure (defects), analyzing these causes, and eliminating them.

B.  

Testing triggers a failure that is caused by a defect in the software, whereas debugging is concerned with finding the causes of this failure (defects), analyzing these causes, and reproducing them.

C.  

Testing identifies a defect that is caused by an error in the software, whereas debugging is concerned with finding the causes of this defect, analyzing these causes, and eliminating them.

D.  

Testing triggers a defect that is caused by an error in the software, whereas debugging is concerned with finding the causes of this defect, analyzing these causes, and eliminating them.

A.  

Checklists should primarily consist of automated test cases to maximize efficiency.

B.  

Checklists should be used exclusively for functional testing, as they are unsuitable for non-functional testing.

C.  

Checklists should contain specific test conditions that can be individually and directly checked.

D.  

Checklists should contain general guidelines to ensure that all aspects of the software are covered.