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.  

Identification of the test object and test environment

B.  

A concise title and a short summary of the defect being reported

C.  

Description of the structure of the test team

D.  

Expected results and actual results

A.  

Allows the expected results to be compared with the actual results.

B.  

Allows the tracking of all changes to versions of the testware.

C.  

Includes all activities that direct and control an organisation with regard to quality

D.  

Focuses on configuring static analysis tools to choose the most suitable breadth and depth of analysis.

A.  

3

B.  

2

C.  

1

D.  

4

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.  

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.  

5

B.  

4

C.  

8

D.  

16

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.  

Unlike dynamic testing, which can be also performed manually, static testing cannot be performed without specialized tools

B.  

Static testing is usually much less cost-effective than dynamic testing

C.  

Unlike dynamic testing, which focuses on detecting potential defects, static testing focuses on detecting failures which may be due to actual defects

D.  

Both static testing and dynamic testing can be used to highlight issues associated with non-functional characteristics

A.  

i and ii

B.  

i and iv

C.  

i and iii

D.  

ii and iii

A.  

-100; 100:1000; 1001

B.  

-500; 0; 100; 1000

C.  

-99; 99:101; 1001

D.  

-1000; -100; 100; 1000

A.  

The decision was wrong. Ensuring quality mandates that static testing is performed after performing the dynamic testing.

B.  

The decision was right. Static testing is usually redundant if a product is planned to go through a full-cycle of dynamic testing.

C.  

The decision was right. Most of the bugs are easier to identify during the dynamic testing.

D.  

The decision was wrong. Static testing can find defects early in the development process, reducing the overall cost of testing and development

A.  

Confirmation testing confirms the quality of the test being run while regression testing ensures that the software still works after a change has been made.

B.  

Confirmation testing is an optional activity whilst regression testing is not negotiable.

C.  

Confirmation testing aims to verify that a defect has been resolved and regression testing ensuring that existing functionality still works after a change.

D.  

Testers' involvement is essential whilst running retesting and regression testing.

E.  

TESTER Involvement is essential whilst running retesting and regression testing.

A.  

Configuration management helps maintain consistent versions of software artifacts.

B.  

Configuration management supports the build process, which is essential for delivering a test release into the test environment.

C.  

When testers report defects, they need to reference version-controlled items.

D.  

Version controlled test ware increases the chances of finding defects in the software under test.

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.  

Testers are involved in reviewing work products as soon as the final version of this documentation is available so that this earlier testing and defect detection can support the “shift-left" strategy.

B.  

Test analysis and design for a specific test level begin during the corresponding development phase of the SDLC, allowing testing to follow the principle of late testing.

C.  

For every software development activity, there is a corresponding testing activity, ensuring that all development activities are subject to quality assurance.

D.  

Different test levels have specific and overlapping test objectives, allowing tests to be appropriate to specific test object types while managing redundancy.

A.  

The slowdown is a failure while the memory leak is a defect

B.  

The slowdown is a defect while the memory leak is an error.

C.  

The slowdown is an error; the memory leak is a defect.

D.  

The slowdown is a defect; the memory leak is a failure.

A.  

12

B.  

6

C.  

4

D.  

3

A.  

[ii] and [IV] are product risks; [i] and [iii] are project risks

B.  

[ii]and [iii] are product risks. [I] and [IV] are project risks.

C.  

[i], and [iV] are product risks; [ii] and [iii] are project risks

D.  

[i], [II] and [iii] are product risks, [IV] is a project risk.

A.  

Review leader

B.  

Facilitator.

C.  

Recorder.

D.  

Moderator

A.  

5 decision rules

B.  

6 decision rules

C.  

32 decision rules

D.  

8 decision rules

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.  

Test logs that document the results of test execution.

B.  

Automated test scripts used for test execution.

C.  

A test plan that describes the test strategy and test objectives.

D.  

A list of test conditions prioritized during test analysis.

A.  

Take on the role of developer to meet challenging project deadlines

B.  

Assume leadership aimed at imposing decisions on the rest of the team.

C.  

Use tools to make the execution of repetitive testing tasks more efficient.

D.  

Determine the corrective actions to get a test project on track in case of deviations from the test plan

A.  

Q1

B.  

Q2

C.  

Q3

D.  

Q4

A.  

i and iv

B.  

i and ii

C.  

i and iii

D.  

iii and iv

A.  

User acceptance tests are usually automated and aim to verify the acceptance criteria for user stories

B.  

Acceptance criteria for user stories can include details on data definitions, for example by describing the format, allowed values, and default values for a data item

C.  

Acceptance criteria for user stones should focus on positive scenarios, while negative scenarios should be excluded

D.  

Tests derived from acceptance criteria for user stories are not included in any of the four testing quadrants

A.  

Test execution

B.  

Test design.

C.  

Test analysis.

D.  

Test planning

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.  

The need to temporarily have additional test personnel available for specific test phases and/or test activities

B.  

The conditions that must be met in order for the test execution activities to be considered completed.

C.  

The list of the product risks which have not been fully mitigated at the end of test execution.

D.  

The conditions that must be met for part of all the planned activities to be suspended and resumed.

A.  

R2. R1, R3. R4. R5, R6. R7, R8.

B.  

R1, R2, R3, R4, R5, R6, R7, R8.

C.  

R2, R4. R8, R5, R1, R6, R3, R7.

D.  

. R2, R1,R3,R7,R6,R5,R4,R8.

A.  

Conclusions, recommendations, and approvals.

B.  

Change history.

C.  

Description of the defect to enable reproduction.

D.  

Status of defect

A.  

R100 000, R100 001, R500 000, R500 001.

B.  

R99 999, R100 000, R499 999, R500 000.

C.  

R100 000. R500 000.

D.  

R99 000, R500 001.

A.  

Test planning.

B.  

Test analysis.

C.  

Test design.

D.  

Test monitoring and control.

A.  

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

B.  

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

C.  

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

D.  

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

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.  

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.  

Checklist-based testing is a technique for managing the review meeting that can be applied in those reviews where the use of checklists is mandatory, as is often the case in formal reviews.

B.  

Checklist-based testing is a review technique that can be used in a formal review process where reviewers, during individual review, try to detect issues within the work product based on a checklist

C.  

In checklist-based testing, using checklists at a high level of detail is more likely to produce test cases that are easier to reproduce than those using checklists at a low level of detail

D.  

Checklists used in checklist-based testing should be reviewed periodically for updates as, over time, test cases designed using the same checklist may become less effective at finding defects.

A.  

Traceability between test basis items and the test cases designed to cover them, makes it possible to determine which test basis items have been covered by the executed test cases.

B.  

Traceability between test basis items and the test cases designed to cover them, enables experience-based test techniques to be applied

C.  

Traceability between test basis items and the test cases designed to cover them, enables identification of which test cases will be affected by changes to the test basis items.

D.  

Traceability can be established and maintained through all the test documentation for a given test level, such as from test conditions through test cases to test scripts.

A.  

1

B.  

2

C.  

3

D.  

4

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.  

Verifying whether specified requirements have been fulfilled

B.  

Triggering failures and finding defects

C.  

Finding errors

D.  

Validating whether the test object is complete and works as expected by the stakeholders

A.  

Product owner, development, and testing

B.  

Business, architecture, and testing

C.  

Business, development, and testing

D.  

Business, development, and acceptance testing

A.  

Each test level should have its own specific test objectives that should be consistent with the software development lifecycle phase or type of activities it addresses.

B.  

Test analysis and design for any test levels should begin as soon as coding is complete, and all system components are available for testing

C.  

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

D.  

All the tests should be automated and run as part of the continuous integration process with every software change

A.  

Black-box test techniques.

B.  

Experience-based test techniques.

C.  

Checklist-based test techniques.

D.  

White-box test techniques.

A.  

Author, Management, Facilitator, Review Leader, Reviewers, Scribe

B.  

Author, Tester. Facilitator. Review Leader. Reviewers. Scribe

C.  

Author, Business analyst. Facilitator, Review Leader. Reviewers. Scribe

D.  

Author. Developer, Facilitator. Review Leader. Reviewers. Scribe

A.  

Mistake

B.  

Fault

C.  

Error

D.  

Failure

A.  

Very low MTBF (Mean Time Between failure)

B.  

Potentially endless loops

C.  

Referencing a variable with an undefined value

D.  

Security vulnerabilities

A.  

{7,8,21,22,29,30}

B.  

{7,8,22,23,29,30}

C.  

{6,7,8,21,22,29,31}

D.  

{6,7,21,22,29,30}

A.  

Defect management

B.  

Configuration management

C.  

Change management

D.  

Risk management

A.  

The support offered by a test data preparation tool is often leveraged by testers to run automated regression test suites

B.  

The support offered by a performance testing tool is often leveraged by testers to run load tests

C.  

The support offered by a bug prediction tool is often used by testers to track the bugs they found

D.  

The support offered by a continuous integration tool is often leveraged by testers to automatically generate test cases from a model

A.  

Decision-based testing.

B.  

Checklist-based testing.

C.  

Error guessing.

D.  

Exploratory testing.

A.  

Tests wear out

B.  

Absence-of-errors fallacy

C.  

Working software over comprehensive documentation.

D.  

Defects cluster together

A.  

Static testing is better suited than dynamic testing for highlighting issues that could indicate inappropriate code modulansation.

B.  

Dynamic testing can only be applied to executable work products, while static testing can only be applied to non-executable work products.

C.  

Both dynamic testing and static testing cause failures, but failures caused by static testing are usually easier and cheaper to analyse.

D.  

Security vulnerabilities can only be detected when the software is being executed, and thus they can only be detected through dynamic testing, not through static testing

A.  

7.

B.  

6.

C.  

5.

D.  

3.

A.  

The test report prepared during a test activity may be referred to as a test progress report, while a test report prepared at the end of a test activity may be referred to as a test summary report.

B.  

The test report prepared during a test activity may be referred to as a test summary report, while a test report prepared at the end of a test activity may be referred to as a test progress report.

C.  

There is no difference between a test progress report and a test summary report.

D.  

Both the test progress report and the test summary report should always be generated via an automated tool.