iSQI ISTQB Certified Tester Foundation Level CTFL_Syll2018 Exam Questions

Answer : D

Testing support tools are software tools that assist testers in performing testing activities, such as test management, test design, test execution, test evaluation, and defect management1.According to the ISTQB syllabus, some typical targets of testing support tools are to automate activities that require significant resources when done manually, automate activities that cannot be executed manually, and automate repetitive tasks1.Automating repetitive inspections is not a typical target of testing support tools, as inspections are static testing techniques that involve human review and analysis of software artifacts1.

Answer : C

The level of risk is determined by multiplying the impact of an adverse event by the likelihood of that event occurring1.The impact of an adverse event is the degree of harm or loss that would result from the event, such as financial loss, reputation damage, legal consequences, or safety hazards1.The likelihood of an adverse event is the probability or frequency of the event happening, based on historical data, expert judgement, or statistical analysis1. The other options are not correct formulas for calculating risk. Option A confuses the cost of preventing an adverse event with its impact. Option B confuses the cost of possible legal action with its likelihood. Option D uses two synonyms for likelihood (probability and frequency) instead of combining it with impact.

Answer : B

Static testing and dynamic testing are two types of testing that differ in the way they evaluate the software or system under test. Static testing is a type of testing that does not involve executing the software or system under test, but rather analyzing it using various techniques, such as reviews, inspections, walkthroughs, checklists, static analysis tools, etc. Dynamic testing is a type of testing that involves executing the software or system under test using test cases and comparing the actual results with the expected results. Static testing techniques, such as reviews, can be undertaken before dynamic testing, making defects cheaper to remove. This is because static testing can help find defects and improve the quality of any work product at any stage of the software development lifecycle, before they become more costly and difficult to fix during dynamic testing or after deployment.

Answer : D

The test tools that would be classified as test execution tools are D. b and d. Test execution tools are tools that automate the execution of test cases or test scripts, and compare the actual results with the expected results. Test execution tools can also record and replay user actions, generate test data, and report test results. Test harness and test comparators are examples of test execution tools. A test harness is a tool that creates a test environment for a component or system under test, by simulating the required dependencies, such as stubs, drivers, or mock objects. A test comparator is a tool that compares the actual outputs of a component or system under test with the expected outputs, and reports any differences or anomalies. A detailed explanation of test execution tools can be found inA Study Guide to the ISTQB Foundation Level 2018 Syllabus, pages 111-1121.

Answer : B

Test metrics are quantitative measures that are used to monitor, control, and improve the test process and its outcomes. Test metrics can be collected at different levels of testing (test case, test suite, test project, etc.) and can be used for different purposes (planning, estimation, execution, evaluation, etc.). Some examples of common test metrics are:

Percentage of work done in test environment creation: This metric indicates how much effort has been spent on setting up and maintaining the test environment, which includes hardware, software, network, data, tools, etc., that are required for conducting the test activities.

Number of test cases run: This metric indicates how many test cases have been executed during a given period or phase of testing.

Deviation from test milestone dates: This metric indicates how much delay or ahead of schedule the test activities are compared to the planned dates.

Defect density: This metric indicates how many defects have been found per unit of size or functionality of the system under test.

Average number of expected defects per requirement is not a common test metric because it is not easy to estimate or measure how many defects are likely to be found for each requirement. Moreover, this metric does not provide useful information for improving the test process or evaluating the test results. You can find more information about test metrics inA Study Guide to the ISTQB Foundation Level 2018 Syllabus, Chapter 5, Section 5.41.

Answer : A

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.

Answer : B

Equivalence partitioning is a technique to divide a set of possible inputs or outputs into classes that are expected to behave similarly or produce similar results. For each equivalence class, only one test case is required to represent the whole class. In this case, we can identify the following equivalence classes for the input field 'ZIP code':

Valid ZIP code format and valid ZIP code value (e.g., 12345)

Valid ZIP code format and invalid ZIP code value (e.g., 99999)

Invalid ZIP code format and valid ZIP code value (e.g., 1234)

Invalid ZIP code format and invalid ZIP code value (e.g., ABCDE)

Therefore, four test cases are required to test this field using equivalence partitioning.