ISTQB-CTFL Dumps with Free 365 Days Update Fast Exam Updates [Q38-Q61]

NO.38 Why should you choose a test technique?

Because you need to match the way you test to the content of the product under test

Because of the time constraints that usually accompany a test project

Because this way you cover the full scope of the product’s functionality

Because choosing a test technique is a common practice in software testing

NO.39 In what way do Configuration Management effects testing?

Without proper configuration management, test planning cannot proceed.

Proper configuration management ensures that testers can uniquely identity the tested item

Configuration management is important for developers, not for testers

There is very little influence of configuration management practices on the test project.

NO.40 Which statement about use case testing is true?

The lest cases are designed to find defects in the data flew.

The test cases are designed to be used by real users, not by professional testers

The test cases are always designed by customers or end users.

The test cases are designed to find defects in the process flow.

NO.41 Which of the following would be the LEAST likely to be used as the basis for a test exit criteria?

Test schedules

Cost of testing performed so far

Confidence of testers in tested code

Number of unfixed defects

NO.42 Which of the following can be considered a VALID exit criterion?
I Estimates of defect density or reliability measures.
II. The completion and publication of an exhaustive Test Report.
III. Accuracy measures, such as code, functionality or risk coverage.
IV Residual risks such as lack of code coverage in certain areas.

I, III, IV

I, II, III

III, IV

II, III, IV

NO.43 Which of the following statements about Experience Based Techniques (EBT) is correct?

EBT use tests derived from the test engineers’ previous experience with similar technologies.

EBT is based on the ability of the test engineer to implement various testing techniques.

EBT is done as a second stage of testing, after non-experienced-based testing took place.

EBT require broad and deep knowledge in testing but not necessarily in the application or technological domain.

NO.44 The following part of a business process flow is specified; REPEAT (book a bill) UNTIL (User presses Cancel). How many test cases are necessary in order to achieve 100% branch coverage of the process flow?

4

1

2

Infinite

NO.45 Which of the following is a function of a dynamic analysis tool?

Provide support for traceability of tests, test results and incidents to source documents

Monitor the allocation, use and de-allocation of memory during run-time of a program

Execute programs step-by-step in order to reproduce failures and find corresponding defects

Provide support for release of baselines consisting of configuration items

NO.46 Which of the following statements about re-testing and regression testing are TRUE?
I Re-testing should be performed after a defect is fixed.
II Regression testing should always be performed after a defect is fixed.
III Re-testing and regression testing may be performed at any test level.
IV Regression testing may include functional, non-functional and structural testing.
V Re-testing should be included in the debugging activity.

I, III. Iv

II, v

I, Ill

II. IV, V

The following statements about re-testing and regression testing are true:
I) Re-testing should be performed after a defect is fixed. Re-testing is a type of testing that verifies that a defect has been successfully resolved by executing a test case that previously failed due to that defect. Re-testing should be performed after a defect is fixed and delivered to ensure that it does not cause any new failures or side effects.
III) Re-testing and regression testing may be performed at any test level. Re-testing and regression testing are not limited to a specific test level, but can be applied at any level depending on the context and objectives. For example, re-testing and regression testing can be performed at unit level, integration level, system level or acceptance level.
IV) Regression testing may include functional, non-functional and structural testing. Regression testing is a type of testing that verifies that previously tested software still performs correctly after changes. Regression testing may include various types of testing depending on the scope and purpose of the changes. For example, regression testing may include functional testing to check if the software meets its requirements, non-functional testing to check if the software meets its quality attributes, or structural testing to check if the software meets its design or code standards. The following statement about re-testing and regression testing is false:
II) Regression testing should always be performed after a defect is fixed. Regression testing is not always necessary after a defect is fixed, as some defects may have a low impact or low likelihood of affecting other parts of the software. Regression testing should be performed after a defect is fixed only if there is a risk of introducing new defects or causing existing defects due to the changes made to fix the defect. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus – Springer, Chapter 2, page 19; Chapter 4, page 45.

NO.47 For a mandatory input field “ZIP code” the following rules are given:
1 – The valid ZIP code format is 5 numeric digits.
2 – The code has to exist in the post office’s official ZIP code list
Using equivalence classes partitioning, how many test cases are required to test this field?

8

3

6

4

NO.48 Which of the following statements about reviews are TRUE?
I In walkthroughs the review meeting is typically led by the author.
II Inspection is characterized by an open-ended review meeting
III Preparation before the review meeting is part of informal reviews
IV Management rarely participates in technical review meetings

II, Ill

I, II

I, IV

III, IV

NO.49 Why it is essential that defects found in a review be reported objectively?

In order to facilitate easy entry of detected defects in a OTS (Defect Tracking System)

In order to allow the author of reviewed work product(S) to take the feedback positively as an effort at improving the product (S) and not as a personal assault

In order to allow the review moderator to easily understand them, and assign them to the right developer for fixing

In order to allow augmentation of existing checklists used for reviewing the work product (S)

NO.50 Out of the following. what is not needed to specify in defect report?

Test environment details

How to reproduce the defect

How to fix the defect

Seventy and priority

NO.51 Which are the MAIN goals of risk management in a software project?

To increase the success probability for the project regardless of costs.

To increase focus on preventative processes and to increase satisfaction for the testers.

To control contractual problems and minimize the impacts of company policies.

To reduce the probability of undesired situations and to reduce the effect of potential impact.

NO.52 Which of the following is a key characteristic of informal reviews?

Kick-off meeting

Low cost

Individual preparation

Metrics analysis

NO.53 The following sentences refer to the ‘Standard for Software Test Documentation’ specification (IEEE 829).
Which sentence is correct?

Any deviation from this standard should be approved by management, marketing & development

Most test documentation regimes follow this spec to some degree, with changes done to fit a specific situation or organization

The key to high quality test documentation regimes is strict adherence to this standard

This test plan outline is relevant for military projects. For consumer market projects there is a different specification with fewer items.

NO.54 Which of the following tools is most likely to detect defects in functions or methods in source code?

configuration management tool

unit test framework tool

test design tool

monitoring tool

NO.55 For withdrawing money tram an Automated Teller Machine (ATM), the following conditions are required:
– The bank card is valid
– The PIN code is correct
– Money is available in the user’s account
The following are some possible interactions between the user and the ATM:
– The entered card is invalid The card is rejected
– The PIN code is wrong The ATM asks for another PIN code
– The requested amount is more than available in the user’s account: The ATM asks for another amount
– The requested amount is available in the user’s account The ATM dispenses the money Which test design technique should be used to cover all possible combinations of the input conditions?

Use case based testing

Decision table

Boundary value analysis

Equivalence class partitioning

A decision table is a technique that should be used to cover all possible combinations of input conditions for withdrawing money from an Automated Teller Machine (ATM). A decision table shows combinations of inputs and/or stimuli (causes) with their associated outputs and/or actions (effects). A decision table consists of four quadrants: conditions (inputs), actions (outputs), condition entries (values) and action entries (results). A decision table can be used to test components that have multiple inputs and outputs that depend on logical combinations of conditions. For example, for testing the ATM, we can identify three input conditions: the bank card is valid, the PIN code is correct, and money is available in the user’s account. We can also identify four output actions: the card is rejected, the ATM asks for another PIN code, the ATM asks for another amount, and the ATM dispenses the money. A decision table can show all possible combinations of these conditions and actions in a systematic way.
Use case based testing is not a technique that can cover all possible combinations of input conditions for withdrawing money from an ATM. Use case based testing is a technique that verifies that a software product or system meets its specified requirements or user stories by executing realistic scenarios or workflows. Use case based testing can be used to test components that have complex or dynamic interactions with users or other systems. For example, for testing the ATM, we can identify several use cases, such as withdraw money, check balance, transfer money, etc. Each use case can have one or more scenarios that describe the steps and outcomes of the interaction. However, use case based testing may not cover all possible combinations of input conditions, as some scenarios may be omitted or overlooked.
Boundary value analysis is not a technique that can cover all possible combinations of input conditions for withdrawing money from an ATM. Boundary value analysis is a technique that tests boundary values between partitions of equivalent data. Boundary values are values at the edge of an equivalence partition or at the smallest incremental distance on either side of an edge. Boundary value analysis can be used to test components that have input values that can be divided into partitions of equivalent data. For example, for testing the ATM, we can identify boundary values for the input amount, such as the minimum and maximum amount allowed by the system or the user’s account. However, boundary value analysis may not cover all possible combinations of input conditions, as some conditions may not have boundary values or may not be related to input values.
Equivalence class partitioning is not a technique that can cover all possible combinations of input conditions for withdrawing money from an ATM. Equivalence class partitioning is a technique that divides the input data and output results of a software component into partitions of equivalent data. Each partition should contain data that is treated in the same way by the component. Equivalence class partitioning can be used to test components that have input values that can be divided into partitions of equivalent data. For example, for testing the ATM, we can identify equivalence partitions for the input amount, such as valid amount (within the range allowed by the system and the user’s account) and invalid amount (outside the range allowed by the system or the user’s account). However, equivalence class partitioning may not cover all possible combinations of input conditions, as some conditions may not be related to input values or may have more than two partitions. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus – Springer], Chapter 4, page 34-46.

NO.56 A program got 100% decision coverage in a test. Which of the following statements is then guaranteed to be true?

Every executable statement Is covered.

Every output equivalence class has been tested.

Every input equivalence class has been tested.

The “dead” code has not been covered.

If a program got 100% decision coverage in a test, then it is guaranteed that every executable statement is covered. Decision coverage (also known as branch coverage) is a type of structural coverage (also known as white-box coverage) that measures how many decision outcomes have been exercised by a test suite. A decision outcome is a possible result of a decision point (such as an if-then-else statement) in a program’s code. Decision coverage requires that each decision point has both true and false outcomes executed at least once by a test suite. Decision coverage implies statement coverage, which is another type of structural coverage that measures how many executable statements have been executed by a test suite. Statement coverage requires that each executable statement is executed at least once by a test suite. Therefore, if a program got 100% decision coverage in a test, then it also got 100% statement coverage in a test, which means that every executable statement is covered. The other options are not guaranteed to be true if a program got 100% decision coverage in a test. Every output equivalence class has been tested and every input equivalence class has been tested are not guaranteed to be true if a program got 100% decision coverage in a test, because equivalence classes are based on functional requirements or specifications, not on code structure or logic. Equivalence classes are used in specification-based testing (also known as black-box testing), which is a type of testing that does not consider the internal structure or implementation of the system under test. Decision coverage is used in structure-based testing (also known as white-box testing), which is a type of testing that considers the internal structure or implementation of the system under test. Therefore, achieving 100% decision coverage does not imply achieving 100% equivalence class coverage. The “dead” code has not been covered is not guaranteed to be true if a program got 100% decision coverage in a test, because dead code (also known as unreachable code) is code that can never be executed due to logical errors or design flaws. Dead code can reduce readability and maintainability of the code, as well as increase complexity and size. Decision coverage does not account for dead code, as it only considers the decision outcomes that are possible to execute. Therefore, achieving 100% decision coverage does not imply that the dead code has not been covered. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus – Springer, page 36.

NO.57 A system has valid input numbers ranging between 1000 and 99999 (both inclusive). Which of the following inputs are a result of designing tests for all valid equivalence classes and their boundaries?

999.1000.23232.99999.100000

999.1000.50000.100000.100001

999.100000

1000,50000,99999

NO.58 Which of the following options cover the test types performed during typical system testing phase:
I Usability
II Requirements based scenarios
III Testing parts of the code in isolation
IV Correct order of parameters in API calls

I, Ill

I. II

II. IV

III. IV

NO.59 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?

The Priority, the Correction description and the Developer name are missing

The version of the application is missing

There is no link to the applicable requirement (traceability)

The description is not highlighting the source of the problem

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.

NO.60 Which test approach will best fit a new project, with little documentation and high probability for bugs?

Exploratory testing

Requirements based testing

Metric based approach

Regression testing

NO.61 A software module to be used in a mission critical application incorporates an algorithm for secure transmission of dat a.
Which review type is most appropriate to ensure high quality and technical correctness of the algorithm?

Walkthrough

Informal Review

Technical Review

Management Review

Leave a Reply Cancel reply