Your Path to Success: How to Pass the iSQI CTFL_Syll2018 ISTQB Certified Tester Foundation Level (Syllabus 2018) Exam

Static testing is testing of a component or system at a specification or implementation level without execution of that software. Requirements review is an example of static testing, because it involves checking the quality and completeness of the requirements specification document without executing the software.

Data-driven is the type of automation test design that is used in the example below. Data-driven testing is a technique to separate the test data from the test scripts and store them in external sources, such as text files, databases, spreadsheets, etc. Data-driven testing allows the test scripts to read the test data from these sources during test execution, which makes the test scripts more reusable and maintainable1 explains data-driven testing as follows:

Data-driven testing is a software testing methodology that is used in the automation testing framework to store the test data in a table or spreadsheet format. This allows automation engineers to have a single test script that can execute tests for all the test data in the table.

Data-driven testing helps to increase the efficiency of automated testing by reducing the number of test scripts required for different scenarios. It also helps to improve the quality of testing by covering more variations of input data and expected results.

A, C, and D are incorrect answers. Dynamic test design, keyword-driven, and data coverage analysis are not types of automation test design that are used in the example below. Dynamic test design is a technique to generate test cases based on dynamic analysis of the system behavior or output during test execution. Keyword-driven testing is a technique to create test scripts using keywords that represent actions or commands that can be executed by an automation tool. Data coverage analysis is a technique to measure and evaluate how much of the input domain or data set has been covered by the test cases.

The correct answer is A, as it describes error guessing. Error guessing is an experience-based test technique that involves designing tests based on experience, defect data, or common knowledge about why software fails1. Error guessing can be used to complement other more formal test techniques by focusing on areas that are more likely to contain defects1. Option B is incorrect, as error guessing does not involve building test cases based on the various experiences of developers, architects, users, and other stakeholders on project teams, but based on the tester’s own experience and knowledge1. Option C is incorrect, as error guessing is not a suitable test technique that can be used effectively in place of more formal techniques, but a supplementary technique that can be used in addition to more formal techniques1. Option D is incorrect, as error guessing is not a valid and useful white-box test technique due to its high degree of statement coverage, but an experience-based test technique that does not rely on the structure of the software1. References: 1, Section 4.2.6

Test implementation and execution is the stage of the Fundamental Test Process where testers write detailed steps for executing each test case (test procedures), prepare and prioritize test cases for execution, execute test cases and record results, compare actual results with expected results and report discrepancies as incidents.

The correct answer is B, as it defines risk level correctly. Risk level is determined by the likelihood of an event happening and the impact or harm from that event4. Likelihood is the probability or frequency of the event occurring4. Impact is the severity or consequence of the event occurring4. Risk level can be calculated by multiplying likelihood and impact, or by using a risk matrix that assigns risk levels based on different combinations of likelihood and impact4. Option A is incorrect, as it does not define risk level correctly. Risk level is not calculated by adding the probabilities of all planned risks to a project, but by assessing the likelihood and impact of each individual risk4. Option C is incorrect, as it does not define risk level correctly. Risk level is not calculated by dividing the sum of all known risks by the sum of all unknown risks, but by assessing the likelihood and impact of each individual risk4. Option D is incorrect, as it does not define risk level correctly. Risk level is not determined by calculating the absolute value of the sum of all potential issues that may occur on the project, but by assessing the likelihood and impact of each individual risk4. References: 4, Section 2.8

The general principles of testing state that testing can show the presence of defects, but not their absence. Running the same test set more often will not increase the likelihood of finding new defects, unless the system or its environment changes. Therefore, statement A contradicts the general principles of testing. Statement B is true, as testing is context-dependent and should be tailored to the specific situation of a project. Statement C is also true, as early testing can help prevent defects and reduce rework. Statement D is true, as it reflects the Pareto principle or the 80/20 rule, which states that most defects are found in a small subset of a system’s modules.

References: ISTQB Certified Tester Foundation Level Syllabus 2018, Section 1.2

Reviewing tests developed by others would not typically be performed by a tester, but rather by a test leader or a peer reviewer1 . Reviewing tests developed by others is an activity that involves checking the quality and completeness of the test cases or procedures and providing feedback or suggestions for improvement1 . The other options are tasks that would typically be performed by a tester. Option A is a task that would typically be performed by a tester, because it involves preparing and acquiring the test data that are needed for executing the test cases or procedures1 . Option B is a task that would typically be performed by a tester, because it involves setting up and checking the test environment that supports the execution of the test cases or procedures1 . Option C is a task that would typically be performed by a tester, because it involves writing test summary reports that document the results and outcomes of the test execution1 .

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.

References: [Certified Tester Foundation Level Syllabus], Section 8.3.1

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.

References: Section 6.3.1, Section 6.3.2

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. Static testing can be applied to any work product that participants know how to read and understand, such as requirements specifications, design specifications, code, test cases, test plans, user manuals, etc. Static testing can help find defects and improve the quality of any work product at any stage of the software development lifecycle.

References: Certified Tester Foundation Level Syllabus, Section 3.1 and 3.2