ISTQB ISTQB-CTFL ISTQB-Foundation Level Exam Online Training

Question #71

Which of the following should be included in a test status report?

I. Estimation details

II. Total number of open and closed defects

III. Actual effort spent

IV. Defect reports

V. Number of executed, failed, blocked tests

A . III, V
B . II, III
C . I, II, IV
D . II, III, V

Reveal Solution Hide Solution

Correct Answer: D
D

Explanation:

The following should be included in a test status report: total number of open and closed defects, actual effort spent, and number of executed, failed, and blocked tests. A test status report is a document that provides information on the results and status of testing activities for a given period or phase. A test status report should include information that is relevant, accurate, and timely for the intended audience and purpose. Some of the information that should be included in a test status report are: total number of open and closed defects, which can indicate the defect trend and defect density of the software product; actual effort spent, which can indicate the productivity and efficiency of the testing process; number of executed, failed, and blocked tests, which can indicate the test progress and test coverage of the software product. The following should not be included in a test status report: estimation details, defect reports, and impact analysis. Estimation details are not part of a test status report, but rather part of a test plan or a test estimation document. Estimation details provide information on the expected time, resources, and costs for testing activities, not on the actual results or status of testing activities. Defect reports are not part of a test status report, but rather separate documents that provide detailed information on individual defects found during testing. Defect reports include information such as defect description, defect severity, defect priority, defect status, defect resolution, etc. Defect reports can be referenced or summarized in a test status report, but not included in full. Impact analysis is not part of a test status report, but rather part of a risk assessment or prioritization process. Impact analysis provides information on the potential effects or consequences of a change or a defect on the software product or project. Impact analysis can be used to evaluate the amount or scope of testing to be performed, but not to report the results or status of testing activities.

Verified Reference: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus – Springer, page 141.

Question #72

In maintenance testing, what is the relationship between impact analysis and regression testing?

A . Impact analysis requires a regression testing for only the tests that have detected faults in previous SW release
B . There is no relationship between impact analysis and regression testing.
C . Impact analysis requires a regression testing for all program elements which were newly integrated (new functionalities).
D . The impact analysis is used to evaluate the amount of regression testing to be performed.

Reveal Solution Hide Solution

Question #73

A software system checks age in order to determine which welcome screen to display. Age groups are:

Group I: 0-12

Group II; 13-18

Group III: over 18

Which of the below represent boundary values?

A . (-1.0.12.13.18,19)
B . (-1.0,11.12.13,14,18.19)
C . (0.12.13.18.19)
D . (4.5.15.20)

Reveal Solution Hide Solution

Question #74

Which of the following is an example of black-box dynamic testing?

A . Functional Testing
B . Code inspection
C . Checking memory leaks for a program by executing it
D . Coverage analysis

Reveal Solution Hide Solution

Correct Answer: A
A

Explanation:

Functional testing is an example of black-box dynamic testing. Black-box testing (also known as specification-based testing) is a type of testing that does not consider the internal structure or implementation of the system under test, but rather its external behavior or functionality. Dynamic testing is a type of testing that involves executing the system under test with various inputs and observing its outputs. Functional testing is a type of black-box dynamic testing that verifies that the system under test performs its intended functions according to its requirements or specifications. Functional testing can be performed at various levels and scopes depending on the objectives and criteria of testing. The other options are not examples of black-box dynamic testing. Code inspection is an example of white-box static testing. White-box testing (also known as structure-based testing) is a type of testing that considers the internal structure or implementation of the system under test. Static testing is a type of testing that does not involve executing the system under test, but rather analyzing it for defects, errors, or violations of standards. Code inspection is a type of white-box static testing that involves examining the source code of the system under test for quality, readability, maintainability, etc. Checking memory leaks for a program by executing it is an example of white-box dynamic testing. Memory leaks are defects that occur when a program fails to release memory that it has allocated but no longer needs. Checking memory leaks for a program by executing it requires knowledge and access to the internal structure or implementation of the program, such as memory allocation and deallocation mechanisms, pointers, references, etc. Coverage analysis is an example of white-box static testing. Coverage analysis is a technique that measures how much of the code or structure of the system under test has been exercised by a test suite. Coverage analysis requires knowledge and access to the internal structure or implementation of the system under test, such as statements, branches, paths, conditions, etc.

Verified Reference: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus – Springer, page 7.

Question #75

What is ‘Component Testing’?

A . Integration Testing
B . Functional testing
C . Experience-based testing
D . A test level

Reveal Solution Hide Solution

Question #76

Which of the following is NOT an objective of testing?

A . Finding defects
B . Providing information for decision-making
C . Gaining confidence about the level of quality of the software
D . Analyzing and removing the cause of failures

Reveal Solution Hide Solution

Question #77

An Incident Management tool implements the following defect states;

Open, Assigned, Solved, Closed Consider the following defect report:

Id T000561

Test Object "Warehouse Management’ application

Tester name; John Bishop

Date: 10th. April 2010

Test Case MRT558I

Status OPEN

Severity Serious

Priority

Problem- After inputting the Total Quantity item = 450 in the SV034 screen, the system shows an unexpected Error message=47

Correction:

Developer name:

Closing date:

Which of the following is a valid criticism of this report?

A . The Priority, the Correction description and the Developer name are missing
B . The version of the application is missing
C . There is no link to the applicable requirement (traceability)
D . The description is not highlighting the source of the problem

Reveal Solution Hide Solution

Correct Answer: B
B

Explanation:

A valid criticism of this report is that the version of the application is missing. The version of the application is an important piece of information that should be included in a defect report, as it helps to identify which release or build of the software product contains the defect. The version of the application can also help to reproduce and debug the defect, as different versions may have different behaviors or features. The other options are not valid criticisms of this report. The priority, the correction description and the developer name are not missing, but rather not applicable for this report. The priority is a measure of how urgently a defect needs to be fixed, which can be assigned by the project manager or the defect tracking system, not by the tester who reports the defect. The correction description and the developer name are information that are added after the defect has been resolved, not when it has been reported. There is no link to the applicable requirement (traceability) is not a valid criticism of this report, because traceability is not a mandatory attribute of a defect report, but rather an optional one. Traceability is a relationship between two or more entities (such as requirements, test cases, defects, etc.) that shows how they are related or dependent on each other. Traceability can help to verify that the requirements are met by the test cases and defects, but it is not essential for reporting a defect. The description is not highlighting the source of the problem is not a valid criticism of this report, because highlighting the source of the problem is not a responsibility of the tester who reports the defect, but rather of the developer who fixes the defect. The description should provide enough information to describe what happened when the defect occurred, such as input values, expected results, actual results, error messages, screenshots, etc., but it does not need to explain why or how it happened.

Verified Reference: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus – Springer, page 140.

Question #78

Which of the following is a key characteristic of informal reviews?

A . Kick-off meeting
B . Low cost
C . Individual preparation
D . Metrics analysis

Reveal Solution Hide Solution

Question #79

Which of the following BEST matches the attributes with a level of testing?

I. Stubs and drivers are often used

II The lest environment should correspond to the production environment

III. Finding defects is not the main focus

IV. Testing can be based on use cases

V. Testing is normally performed by testers

VI. Testing for functional and non-functional characteristics

A . Component – VI
Integration – IV
System – I
Acceptance – III
B . Component – IV
Integration -I
System – VI
Acceptance – V
C . Component – I
Integration – V
System – II
Acceptance – IV
D . Component – V
Integration – II
System – IV
Acceptance – VI

Reveal Solution Hide Solution

Question #80

Which of the following statements is not correct?

A . Looking for defects in a system may require Ignoring system details
B . Identifying defects may be perceived as criticism against product
C . Looking for defects in system requires professional pessimism and curiosity
D . Testing is often seen as a destructive activity instead of constructive activity

Reveal Solution Hide Solution