iSQI ISTQB Certified Tester Foundation Level (CTFL) v4.0 CTFL_Syll_4.0 Exam Practice Test

Page: 1 / 14
Total 151 questions
Question 1

Consider a program that computes the factorial of a number (n). From the specifications you know that:

* If n < 0, a message "Value out of range" must be issued.

* If 0 < n < 100, the program calculates the factorial and returns the number

* If 100 < n < 200 message "Value out of range" must be issued

Which of the following statements about the equivalence partitions is CORRECT?



Answer : C

Equivalence partitioning involves dividing input data into partitions that are treated the same by the system under test. The given specifications create overlapping partitions:

For n<0n < 0n<0, an error message 'Value out of range' is issued.

For 0<n<1000 < n < 1000<n<100, the factorial is calculated.

For 100<n<200100 < n < 200100<n<200, the same error message 'Value out of range' is issued.

However, the range between 0 and 100 is exclusive of 0 and 100, meaning that the partitions overlap and create ambiguity for the boundary values. Thus, the correct statement is that the requirements are not correct because the partitions are overlapping.


Question 2

Which ONE of the following is a CORRECT example of the purpose of a test plan?



Answer : B

A test plan serves multiple purposes, such as defining the scope, approach, resources, and schedule of the testing activities. It also helps in communicating important information and managing stakeholder expectations. In agile projects, test plans might be concise to align with agile principles of simplicity and flexibility. A one-page test plan can effectively communicate broad activities and strategic decisions, such as not writing detailed test cases due to the project's agile nature. This approach ensures that essential information is conveyed without unnecessary documentation overhead, adhering to the agile manifesto's value of 'working software over comprehensive documentation'.


Question 3

Which of the following is a test task that usually occurs during test implementation?



Answer : A

A test task that usually occurs during test implementation is to make sure the planned test environment is ready to be delivered. The test environment is the hardware and software configuration on which the tests are executed, and it should be as close as possible to the production environment where the software system will operate. The test environment should be planned, prepared, and verified before the test execution, to ensure that the test conditions, the test data, the test tools, and the test interfaces are available and functional. The other options are not test tasks that usually occur during test implementation, but rather test tasks that occur during other test activities, such as:

Find, analyze, and remove the causes of the failures highlighted by the tests: This is a test task that usually occurs during test analysis and design, which is the activity of analyzing the test basis, designing the test cases, and identifying the test data. During this activity, the testers can use techniques such as root cause analysis, defect prevention, or defect analysis, to find, analyze, and remove the causes of the failures highlighted by the previous tests, and to prevent or reduce the occurrence of similar failures in the future tests.

Archive the testware for use in future test projects: This is a test task that usually occurs during test closure, which is the activity of finalizing and reporting the test results, evaluating the test process, and identifying the test improvement actions. During this activity, the testers can archive the testware, which are the test artifacts produced during the testing process, such as the test plan, the test cases, the test data, the test results, the defect reports, etc., for use in future test projects, such as regression testing, maintenance testing, or reuse testing.

Gather the metrics that are used to guide the test project: This is a test task that usually occurs during test monitoring and control, which is the activity of tracking and reviewing the test progress, status, and quality, and taking corrective actions when necessary. During this activity, the testers can gather the metrics, which are the measurements of the testing process, such as the test coverage, the defect density, the test effort, the test duration, etc., that are used to guide the test project, such as planning, estimating, scheduling, reporting, or improving the testing process.Reference: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:

ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.1, Test Planning1

ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.2, Test Monitoring and Control1

ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.3, Test Analysis and Design1

ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.4, Test Implementation1

ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.5, Test Execution1

ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.6, Test Closure1

ISTQB Glossary of Testing Terms v4.0, Test Environment, Test Condition, Test Data, Test Tool, Test Interface, Failure, Root Cause Analysis, Defect Prevention, Defect Analysis, Testware, Regression Testing, Maintenance Testing, Reuse Testing, Test Coverage, Defect Density, Test Effort, Test Duration2


Question 4

A company wants to reward each of its salespeople with an annual bonus that represents the sum of all the bonuses accumulated for every single sale made by that salesperson. The bonus for a single sale can take on the following four values: 3%, 5%, 7% and 10% (the percentage refers to the amount of the single sale). These values are determined on the basis of the type of customer (classified as "Basic" or "Premium") to which such sale was made, and on the amount of such sale classified into the following three groups G1, G2 and G3:

* [G1]: less than 300 euros

* [G2]: between 300 and 2000 euros

* [G3]: greater than 2000 euros

Which of the following is the minimum number of test cases needed to cover the full decision table associated with this scenario?



Answer : B

The minimum number of test cases needed to cover the full decision table associated with this scenario is 6. This is because the decision table has 4 conditions (type of customer and amount of sale) and 4 actions (bonus percentage). The conditions have 2 possible values each (Basic or Premium, and G1, G2 or G3), so the total number of combinations is 2 x 2 x 2 x 2 = 16. However, not all combinations are valid, as some of them are contradictory or impossible. For example, a sale cannot be both less than 300 euros and greater than 2000 euros at the same time. Therefore, we need to eliminate the invalid combinations and keep only the valid ones. The valid combinations are:

Type of customer

Amount of sale

Bonus percentage

Basic

G1

3%

Basic

G2

5%

Basic

G3

7%

Premium

G1

5%

Premium

G2

7%

Premium

G3

10%

These 6 combinations cover all the possible values of the conditions and actions, and they are the minimum number of test cases needed to cover the full decision table.


Question 5

Consider the following user story about an e-commerce website's registration feature that only allows registered users to make purchases:

''As a new user, I want to register to the website, so that I can start shopping online''

The following are some of the acceptance criteria defined for the user story:

[a] The registration form consists of the following fields: username, email address, first name, last name, date of birth, password and repeat password

[b] To submit the registration request, the new user must fill in all the fields of the registration form with valid values and must agree to the terms and conditions

[c] To be valid, the email address must not be provided by free online mail services that allow to create disposable email addresses. A dedicated error message must be presented to inform the new user when an invalid address is entered

[d] To be valid, the first name and last name must contain only alphabetic characters and must be between 2 and 80 characters long. A dedicated error message must be presented to inform the new user when an invalid first name and/or the last name is entered

[e] After submitting the registration request, the new user must receive an e-mail containing the confirmation link to the e-mail address specified in the registration form

Based only on the given information, which of the following ATDD tests is most likely to be written first?



Answer : D

Based on the given user story and acceptance criteria, the ATDD (Acceptance Test-Driven Development) approach focuses on defining acceptance tests before development begins. The first test written typically covers the 'happy path' or the most straightforward scenario to ensure the primary functionality works as expected.

Given Acceptance Criteria:

The registration form must be filled with valid values.

The user must accept terms and conditions.

An email with a confirmation link must be sent after submission.

The most likely first ATDD test would ensure that a new user can successfully register by filling in all fields with valid data and confirming the registration through an email link. This ensures that the basic and most crucial functionality of the registration feature is working correctly before handling edge cases or error conditions.


ISTQB CTFL Syllabus Section 2.3 on acceptance test-driven development (ATDD).

Question 6

Which of the following is a test-first approach, where tests that express a shared understanding from stakeholders of how the application is expected to work, are first written in business-readable language (following the Given/When/Then format), and then made executable to drive development?



Answer : C

This answer is correct because Behavior-Driven Development (BDD) is a test-first approach, where tests that express a shared understanding from stakeholders of how the application is expected to work, are first written in business-readable language (following the Given/When/Then format), and then made executable to drive development. BDD is a collaborative approach that involves testers, developers, business analysts, product owners, and other stakeholders in defining the expected behavior of the application using scenarios that describe the preconditions, actions, and outcomes of the application. BDD scenarios are written using a domain-specific language (DSL) that can be translated into executable test cases using tools such as Cucumber or SpecFlow. BDD aims to improve communication, collaboration, and feedback among the team members, and to deliver software that meets the customer's needs and expectations.Reference: ISTQB Glossary of Testing Terms v4.0, ISTQB Foundation Level Syllabus v4.0, Section 3.1.1.4


Question 7

Which of the following types of tools is best suited for determining source code compliance with the guidelines provided by a coding standard?



Answer : C

A static analysis tool is best suited for determining source code compliance with the guidelines provided by a coding standard. Static analysis tools analyze code without executing it, checking for adherence to coding standards, potential errors, and code quality issues. They are designed to detect deviations from predefined coding standards and ensure that the code conforms to best practices and guidelines.


ISTQB CTFL Syllabus V4.0, Section 3.2.3 on Static Analysis and its applications

The syllabus explains that static analysis tools are used to enforce coding standards and improve code quality by detecting issues early in the development process.

CTFL NEW

Page:    1 / 14   
Total 151 questions