Free iSQI ISTQB Certified Tester Foundation Level CTFL_Syll2018 Exam Questions

Checking that at least 50% of decisions have been exercised by a test case suite is not a valid use of decision coverage, because it does not meet the minimum criterion of decision coverage, which is to exercise all possible outcomes of each decision in the software under test1.Decision coverage is a technique that measures how much of the logic or branching of the software under test has been exercised by the test cases1. The other options are valid uses of decision coverage.Option A is a valid use of decision coverage, because it can check that all decisions have been exercised in a single program1.Option B is a valid use of decision coverage, because it can check that all decisions have been exercised in a business process1.Option C is a valid use of decision coverage, because it can check that all calls from one program module to another have been made correctly1.

Black-box test techniques are test techniques that are based on an analysis of the test basis without reference to the internal structure of the system under test. Decision table testing is a black-box test technique that uses a table showing combinations of inputs and/or stimuli (causes) with their associated outputs and/or actions (effects). Use case testing is a black-box test technique that uses scenarios based on use cases (descriptions of sequences of events that a system performs that yield an observable result of value to a particular actor). State transition testing is a black-box test technique that uses models of the state transitions and events of a system to design test cases.

The correct answer is A, as it provides the best test execution schedule that takes into account the priorities and technical and logical dependencies.A test execution schedule is a plan that defines the order and timing of test cases to be executed based on various factors such as dependencies, risks, priorities, and resources1. In this case, the factors are the priorities and technical and logical dependencies of the test cases.The priorities are the levels of importance or urgency assigned to the test cases, such as low, medium, or high1.The technical dependencies are the relationships between the test cases that require one test case to be executed before another test case can be executed1.The logical dependencies are the relationships between the test cases that make sense to execute one test case after another test case for better understanding or efficiency1. Option A provides the best test execution schedule that takes into account these factors, as it follows these rules:

Execute high priority test cases before medium or low priority test cases

Execute test cases that have technical dependencies in the correct order

Execute test cases that have logical dependencies in a sensible order

The following table shows how option A follows these rules:

Option B does not follow these rules, as it executes TC1 before TC2, which violates the technical dependency. Option C does not follow these rules, as it executes TC5 before TC6, which violates the logical dependency.Option D does not follow these rules, as it executes TC2 before TC3, which violates the technical dependency. Reference:1, Section 2.5

Using a keyword-driven testing approach to separate the actions and data from the tool's script is the best approach to improve the way test automation tools are being used in your company, because it allows for more flexibility, maintainability, and reusability of automated test scripts1.A keyword-driven testing approach uses keywords or commands to represent actions or data in the test scripts, which can be stored in external files or tables and accessed by the tool1. The other options are not good approaches to improve the way test automation tools are being used in your company.Option A is not a good approach, because selecting and automating scripts that test new functionality to find the most defects does not consider the suitability, feasibility, and cost-effectiveness of automation1.Option C is not a good approach, because ensuring that all data, inputs and actions are stored in the tool's script for ease of maintenance makes the test scripts more rigid, complex, and difficult to modify1.Option D is not a good approach, because keeping expected results separate from the automation tool to allow the testers to check the results reduces the efficiency and reliability of automation and increases the manual effort

Effort estimate depends on the budget of the project is the wrong statement about estimation of the test effort, because it confuses the cause and effect relationship between effort estimate and budget. Effort estimate does not depend on the budget of the project, but rather influences it. Effort estimate is an approximation of how much time and resources are needed for testing activities based on various factors such as scope, complexity, risks, quality, etc. . Budget is the amount of money that is allocated or available for testing activities based on the effort estimate . The other options are true statements about estimation of the test effort. Option A is true, because effort estimate can be inaccurate because the quality of the product under test is not known, which affects the number and severity of defects that need to be detected and fixed . Option B is true, because once the test effort is estimated, resources can be identified and a schedule can be drawn up, which are part of test planning . Option C is true, because experience based estimation is one of the estimation techniques that relies on the judgement and expertise of testers or other stakeholders who have previous knowledge or experience with similar projects .

Testing tools can be used by both developers and testers for different purposes and at different stages of the software development life cycle. For example, developers can use tools such as unit testing frameworks, code coverage tools, debugging tools, static analysis tools, etc., to improve the quality of their code and find defects early. Testers can use tools such as test management tools, test design tools, test execution tools, test data preparation tools, performance testing tools, etc., to support their testing activities and increase their efficiency and effectiveness. The use of testing tools does not necessarily imply test automation, which is the use of software to perform or support test activities that would otherwise require manual intervention. Test automation is a complex and costly process that requires careful planning, design, implementation, maintenance, and evaluation. The use of testing tools also does not change the role of the test team, which is still responsible for defining the test strategy, designing the test cases, analyzing the test results, reporting the defects, etc. You can find more information about testing tools and test automation inA Study Guide to the ISTQB Foundation Level 2018 Syllabus, Chapter 61.

The combination of the conditions Valid Card Number (NO) + Purchase Approved (YES) is not feasible, as a purchase cannot be approved with an invalid card number. Therefore, this combination can be ignored in the equivalence partitioning for the different types of credit card. Each type of credit card has two valid equivalence partitions: Valid Card Number (YES) + Purchase Approved (YES) and Valid Card Number (YES) + Purchase Approved (NO). Each type of credit card also has one invalid equivalence partition: Valid Card Number (NO) + Purchase Approved (NO). Therefore, to cover all the combinations of equivalence partitions for the four types of credit card, we need 4 x (2 + 1) = 12 test cases.

A, B, and D are incorrect answers. A implies that there are two equivalence partitions for each type of credit card, which is not true as there are three. B implies that there is only one equivalence partition for each type of credit card, which is not true as there are two valid ones and one invalid one. D implies that there are four equivalence partitions for each type of credit card, which is not true as there are only three.

According to the syllabus, test design is the activity of deriving and specifying test cases from test conditions to test software. Test design involves processes such as identifying test data, designing test scenarios, creating test procedures, and defining expected results. The answer A is correct because it is an example of a task most associated with the test design activity. Test data, derived from production data, is developed for use during testing. The other answers are incorrect because they are examples of tasks associated with other test activities, such as test planning (B), test implementation , and test monitoring and control (D).

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.

The test execution schedule that meets the test plan requirements and logical dependencies is e, a, d, c, b. This schedule follows the order of re-tests first (e), followed by the highest priority tests (a and d), and then creates test data for subsequent tests (c and b).This schedule also respects the logical dependencies, as test case a creates an admin user, which is necessary for test case d to create a standard user, which is necessary for test cases c and b to perform other actions1.

Equivalence partitioning is a technique that divides the input domain of a system into partitions or classes that are expected to behave similarly or produce similar outputs2.A test case can cover one value from each partition, as it is assumed that all values in the same partition are equivalent for testing purposes2. In this question, the groups of numbers fall into different equivalence classes based on the amount of customs duty to be paid, as shown below:

Group

Equivalence Classes

$20,000 $20,001 $30,001

No duty (up to $2,000), 10% duty ($2,001-$10,000), 12% duty ($10,001-$30,000), 17% duty (above $30,000)

$2,000 $2,001 $10,000

No duty (up to $2,000), 10% duty ($2,001-$10,000), 12% duty ($10,001-$30,000)

$2,000 $8,000 $20,000

No duty (up to $2,000), 10% duty ($2,001-$10,000), 12% duty ($10,001-$30,000)

$1,500 $2,000 $10,000

No duty (up to $2,000), 10% duty ($2,001-$10,000)

According to the user story checklist, the user story must contain the reason for the need, which is usually expressed by using the word ''so that'' or ''because''. For example, the user story could be rewritten as:

User Story US2018 As a bank account customer, I would like to transfer money from one account to another using the mobile banking application by using the drag and drop feature,so that I can easily manage my finances.

This way, the user story provides a clear value proposition and a justification for the need. The reason also helps to define the scope and priority of the user story, as well as to verify the acceptance criteria.

For the code fragment given below, one test case is required for statement coverage and two test cases are required for branch coverage. Statement coverage requires that every executable statement in the code is executed at least once. Branch coverage requires that every possible outcome of each decision point in the code is executed at least once. The following table shows how to achieve statement and branch coverage for the code fragment:

Test Case

Input

Output

Statement Coverage

Branch Coverage

1

x = 3

y = 9

S1, S2, S3

T1 = true

2

x = 5

y = 25

S1, S2

T1 = false

As shown in the table, test case 1 covers all three statements (S1, S2, S3) in the code fragment, achieving 100% statement coverage. Test case 2 covers only two statements (S1, S2) in the code fragment, but it exercises a different outcome of the decision point T1 (if x < 4), achieving 100% branch coverage.

Assigning resources for the planned activities is an activity that is appropriate to the test planning stage, because it involves estimating and allocating the necessary human and physical resources for testing . Test planning is the process of defining the objectives, scope, approach, and resources for testing . The other options are not activities that are appropriate to the test planning stage, but rather to other stages of testing. Option A is an activity that is appropriate to the test analysis stage, because it involves analysing the test basis (such as requirements, design, or code) to identify test conditions . Option C is an activity that is appropriate to the test implementation stage, because it involves designing and preparing the test environments (such as hardware, software, network, or data) for test execution . Option D is an activity that is appropriate to the test execution stage, because it involves writing a test execution schedule that defines the order and dependencies of test cases or procedures .

Use case testing does not find defects caused by interaction of different components is the statement that is false about use case testing. Use case testing is a technique to create test cases based on use cases, which are descriptions of how a system interacts with one or more actors (users or other systems) to achieve a specific goal or function.Use case testing can find defects caused by interaction of different components, as use cases often involve multiple components working together to provide a service or functionality to an actor2explains use case testing as follows:

Use case testing is a technique that helps us identify test cases that exercise the whole system on a transaction by transaction basis from start to finish. It is a functional black box testing technique.

Use cases are prepared by analysts and domain experts who document the functional requirements of a system from an end-user perspective. Each use case typically has a mainstream scenario and may have alternate or exceptional scenarios that describe different paths or outcomes.

Use case testing can help to verify that all the interactions between actors and the system under test work as expected and meet the user requirements. It can also help to detect integration defects between different components or subsystems.

A, B, and D are correct statements about use case testing. Use case generally has a mainstream scenario and may have many alternate or exceptional scenarios (A), as use cases describe different paths or outcomes depending on various conditions or events. A use case can be defined at different levels of abstraction, such as user goal level, summary level, subfunction level, etc., but not at the abstract level detached from the implementation or at the system level describing a set of executed functions (B), as use cases always describe interactions between actors and systems rather than abstract concepts or functions. Each use case has preconditions which need to be met for the use case to work successfully (D), as preconditions specify what must be true before a use case can begin.