ExamGecko
Home / ISTQB / CTFL-2018
Ask Question

ISTQB CTFL-2018 Practice Test - Questions Answers, Page 26

Question list
Search

Question 251

Report
Export
Collapse

Which of the following is a correct reason to apply test automation?

When a new test automation tool is launched
When a new test automation tool is launched
When there are a lot of repetitive testing tasks
When there are a lot of repetitive testing tasks
When it is easy to automate
When it is easy to automate
When it is cheap to buy test automation tools
When it is cheap to buy test automation tools
Suggested answer: B

Explanation:

A correct reason to apply test automation is when there are a lot of repetitive testing tasks, as test automation can reduce the effort and time required to execute them, and improve the consistency and accuracy of the results. The other options are not valid reasons to apply test automation, as they do not consider the benefits and risks of test automation, the suitability of the test object for automation, or the availability of resources and skills for automation.

asked 18/09/2024
Harry Vervelde
40 questions

Question 252

Report
Export
Collapse

Which of the following processes is related to ensuring the integrity of the testware?

Configuration management
Configuration management
Test automation
Test automation
Build release
Build release
Project management
Project management
Suggested answer: A

Explanation:

Configuration management is related to ensuring the integrity of the testware, as it is a process that controls and documents changes to test items, test cases, test data, test scripts, test results, and test documentation throughout the testing lifecycle. The other options are not related to ensuring the integrity of the testware, but to other aspects of testing such as test execution, test environment setup, and test planning.

asked 18/09/2024
RAHULREDDY BIRADAVOLU
42 questions

Question 253

Report
Export
Collapse

Considering the following pseudo-code, calculate the MINIMUM number of test cases required to achieve 100% statement coverage and 100% decision coverage.

ISTQB CTFL-2018 image Question 253 48859 09182024210804000000

Statement coverage: 4, Decision coverage: 5
Statement coverage: 4, Decision coverage: 5
Statement coverage. 3. Decision coverage 4
Statement coverage. 3. Decision coverage 4
Statement coverage 4. Decision coverage 4
Statement coverage 4. Decision coverage 4
Statement coverage: 4. Decision coverage: 3
Statement coverage: 4. Decision coverage: 3
Suggested answer: C

Explanation:

To achieve 100% statement coverage, we need to execute every statement in the code at least once. To achieve 100% decision coverage, we need to execute every possible outcome of every decision in the code at least once. In this case, we can use the following test cases to cover both statement and decision coverage:

A = 5, B = 4, C = 3, D = 2, E = 1

A = 1, B = 2, C = 3, D = 4, E = 5

A = 3, B = 4, C = 5, D = 2, E = 1

A = 3, B = 2, C = 1, D = 4, E = 5

These four test cases will cover all the statements and all the possible outcomes of the decisions in the code. Therefore, the minimum number of test cases required to achieve both statement and decision coverage is four.

asked 18/09/2024
Gerhard Seher
28 questions

Question 254

Report
Export
Collapse

Consider the following Pseudo code:

ISTQB CTFL-2018 image Question 254 48860 09182024210804000000

How many minimum lea cases are required to cover 100% Statement coverage and Decision coverage?

1 for Statement. 5 for Decision
1 for Statement. 5 for Decision
1 for Statement. 2 for Decision
1 for Statement. 2 for Decision
5 for Statement. 1 for Decision
5 for Statement. 1 for Decision
2 for Statement, 5 for Decision
2 for Statement, 5 for Decision
Suggested answer: B

Explanation:

To achieve 100% statement coverage, we need to execute every statement in the code at least once. To achieve 100% decision coverage, we need to execute every possible outcome of every decision in the code at least once. In this case, we can use the following test cases to cover both statement and decision coverage:

A = true, B = true

A = false, B = false

These two test cases will cover all the statements and all the possible outcomes of the decisions in the code. Therefore, the minimum number of test cases required to achieve both statement and decision coverage is two.

asked 18/09/2024
Maurizio Toniato
31 questions

Question 255

Report
Export
Collapse

What is a typical benefit of use case testing?

Finding failures in the possible states transitions
Finding failures in the possible states transitions
Clearer identification of system equivalence partitioning
Clearer identification of system equivalence partitioning
Finding of failures in the business process flows, which highlight system use in the real world
Finding of failures in the business process flows, which highlight system use in the real world
Identification of bugs in the system components.
Identification of bugs in the system components.
Suggested answer: C

Explanation:

Use case testing is a technique that uses scenarios based on use cases to test the functionality and usability of a system from the user's perspective. A use case is a description of how a system interacts with one or more actors (users or other systems) to achieve a specific goal. A typical benefit of use case testing is finding failures in the business process flows, which highlight system use in the real world. This is because use case testing focuses on how the system is used by different actors in different situations, rather than on individual components or features of the system.

asked 18/09/2024
Abdul Majid Pasha
39 questions

Question 256

Report
Export
Collapse

Which of the following statements is the best explanation why software failures can be caused by environmental conditions?

Factors like magnetism, radiation and even pollution can affect electronic devices and the performance of their embedded real time software
Factors like magnetism, radiation and even pollution can affect electronic devices and the performance of their embedded real time software
Environmental conditions only affect the hardware - not the software
Environmental conditions only affect the hardware - not the software
If the hardware on which the software application is running under ambient temperature and humidity, no failures can be linked to environmental conditions
If the hardware on which the software application is running under ambient temperature and humidity, no failures can be linked to environmental conditions
Extreme heat and vibrations exerted on storage media can cause errors in algorithms and program flows
Extreme heat and vibrations exerted on storage media can cause errors in algorithms and program flows
Suggested answer: B

Explanation:

The statement that environmental conditions only affect the hardware - not the software is not a good explanation why software failures can be caused by environmental conditions. Environmental conditions can affect both the hardware and the software, as they can influence the performance, reliability, and functionality of the system. For example, factors like magnetism, radiation, pollution, heat, humidity, vibration, etc. can affect electronic devices and the embedded software that runs on them. Software failures caused by environmental conditions can have serious consequences, especially for safety-critical systems.

Reference:Certified Tester Foundation Level Syllabus, Section 1.2.2

asked 18/09/2024
Kodjo Boessi
33 questions

Question 257

Report
Export
Collapse

Which of the following test types are non-functional tests?

I) Acceptance test

II,) Regression test

II,I) Stress test

IV) Component test

V) Reliability test

I, II,I and V
I, II,I and V
I, II, and IV
I, II, and IV
II, Ill and V
II, Ill and V
II,I and V
II,I and V
Suggested answer: A

Explanation:

Non-functional testing is a type of testing that focuses on the quality attributes of the system or its components, such as performance, reliability, usability, security, etc. Non-functional testing can be done at any test level, depending on the test objectives and scope. In this case, the test types that are non-functional tests are:

Acceptance test: A test level that focuses on verifying whether the system meets the user's needs and expectations, and whether it is acceptable for delivery or deployment.

Stress test: A type of performance testing that evaluates the behavior of the system under extreme or abnormal conditions, such as high load, limited resources, or concurrent access.

Reliability test: A type of testing that evaluates the ability of the system or its components to perform their required functions under stated conditions for a specified period of time.

Therefore, statements I, II,I, and V are correct.

asked 18/09/2024
Jonaid Alam
36 questions

Question 258

Report
Export
Collapse

Which of the following is NOT a test control activity?

Re-prioritize tests because of time pressure
Re-prioritize tests because of time pressure
Change the test schedule due to viability of a test environment
Change the test schedule due to viability of a test environment
Writing test suspension and resumption criteria in the test plan
Writing test suspension and resumption criteria in the test plan
Set an entry criterion requiring fixes to be retested by a developer before accepting them into a build
Set an entry criterion requiring fixes to be retested by a developer before accepting them into a build
Suggested answer: C

Explanation:

Test control is a test management activity that involves making decisions based on information from test monitoring and test progress reporting. Test control activities include:

Re-prioritizing tests because of time pressure

Changing the test schedule due to availability of a test environment

Setting entry and exit criteria for test levels or test activities

Initiating corrective actions to resolve deviations from the test plan

Writing test suspension and resumption criteria in the test plan is not a test control activity, but rather a test planning activity. Test suspension and resumption criteria are used to define when to stop and resume testing in case of unforeseen events or issues that affect the test execution.

asked 18/09/2024
Carole Pie
46 questions

Question 259

Report
Export
Collapse

Which of the following statements about use cases and use case testing is NOT TRUE?

Use cases can be used as test basis for acceptance testing
Use cases can be used as test basis for acceptance testing
Use case testing can find defects in the process flow.
Use case testing can find defects in the process flow.
Use cases can be described at the abstract level or at the system level
Use cases can be described at the abstract level or at the system level
Use cases are normally derived from decision tables
Use cases are normally derived from decision tables
Suggested answer: D

Explanation:

The statement that use cases are normally derived from decision tables is not true. Decision tables are a technique to represent complex logical conditions in a tabular form, where each column represents a possible combination of conditions and actions. Use cases are a technique to describe how a system interacts with one or more actors (users or other systems) to achieve a specific goal. Use cases are not derived from decision tables, but from the requirements and the user's perspective of the system.

asked 18/09/2024
Abel Galleguillos
39 questions

Question 260

Report
Export
Collapse

What is a defect density?

The percentage of defects identified over the total number of test cases
The percentage of defects identified over the total number of test cases
The deviation rate of the system from its expected behavior
The deviation rate of the system from its expected behavior
The ratio of the defects identified in these system over the expected number of total defects
The ratio of the defects identified in these system over the expected number of total defects
The number of defects identified in the system under test divided by the size of the system
The number of defects identified in the system under test divided by the size of the system
Suggested answer: D

Explanation:

Defect density is a metric that measures the number of defects identified in the system under test divided by the size of the system. The size of the system can be measured in different ways, such as lines of code, function points, or modules. Defect density can be used to compare the quality of different systems or different versions of the same system.

asked 18/09/2024
Alpesh Panchal
20 questions
Total 365 questions
Go to page: of 37