Free Practice Questions for iSQI CTFL_Syll2018 Exam

2400, 1000, 2301 are test case inputs that each fall into a different equivalence partition1. Equivalence partitioning is a black box test design technique that divides the input domain of a system into partitions of equivalent data2. Each partition should contain data that is expected to be treated the same by the system2. Therefore, only one test case input from each partition is needed to test the system’s behaviour2. In this question, the input domain of the system is the time of travel, which can be divided into three partitions based on the fare rules:

Peak-time tariff: This partition contains all the times between 0600 and 1000 (inclusive), which are subject to a higher fare.

Off-peak tariff: This partition contains all the times between 1001 and 2259 (inclusive), which are subject to a lower fare.

No service: This partition contains all the times between 2300 and 0559 (inclusive), which are not valid for travel.

Therefore, to test the system’s behaviour for each partition, we need to choose one test case input from each partition. Among the options given in this question, only D contains one test case input from each partition. 2400 belongs to the no service partition, 1000 belongs to the peak-time tariff partition, and 2301 belongs to the off-peak tariff partition. Therefore, D is the correct answer.

Test analysis and design is the phase of the test process where test cases and test data are designed and prioritized, based on the test basis and test objectives. Therefore, option C is correct, as it includes tasks I, II, and III. Option A is incorrect, as it includes tasks IV and V, which are part of test implementation and execution phase. Option B is incorrect, as it includes task IV, which is part of test implementation and execution phase. Option D is incorrect, as it does not include task III, which is part of test analysis and design phase.

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

 Wrong business rules are defects that cannot be found by static analysis tools, because they are logical or functional errors that depend on the context and requirements of the software13. A static analysis tool can only detect syntactic or structural errors in the code or design of the software under test, but not whether they match the intended business rules or logic13. The other options are defects that can be found by static analysis tools. Option A is a defect that can be found by a static analysis tool, because it is a structural error that causes the code to loop indefinitely without terminating13. Option C is a defect that can be found by a static analysis tool, because it is a syntactic error that causes the code to fail to compile or run13. Option D is a defect that can be found by a static analysis tool, because it is a structural error that indicates a waste of memory or a possible logic flaw

According to the syllabus, verification is the process of evaluating a product or component to determine whether it satisfies its specified requirements. Validation is the process of evaluating a product or component to determine whether it fulfills its intended use and user expectations. Verification answers the question “Are we building the product right?” while validation answers the question “Are we building the right product?” Both verification and validation involve providing objective evidence, which means factual, unbiased, and observable information that supports the evaluation. The answer D is correct because it best distinguishes the terms “validation” and “verification”. The other answers are incorrect because they either confuse the terms “validation” and “verification” or use subjective evidence, which means personal, biased, or unobservable information that does not support the evaluation.

References: [Certified Tester Foundation Level Syllabus], Section 1.2.1, page 10-11.

A test harness is a test environment comprised of stubs and drivers needed to execute a test, especially when testing components or interfaces. Therefore, option D is correct. Option A is incorrect, as a test harness is not a topic for the final Test Report. Option B is incorrect, as a test harness is not a general name for test data. Option C is incorrect, as a test harness is not a detailed description of a test case.

References: Certified Tester Foundation Level Syllabus, Section 5.3

Work Breakdown Structure (WBS) is a project management technique that decomposes a project into smaller and manageable tasks. It is not a factor that is used as a basis for estimating testing effort, but rather an outcome of the estimation process. The other options are factors that can influence the testing effort, such as the quality of the test basis, the requirements for documentation, and the skills of the test team.

References: Section 2.3, Section 2.4

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.

References: Certified Tester Foundation Level Syllabus, Section 2.4.2 and 2.4.3

 I, III, and IV are part of the ISTQB code of ethics, which can be found in 2:

The Code consists of nine principles related to the behavior of and decisions made by professional software testers, including practitioners, trainers, supervisors, managers, authors, standards makers and employers.

The Code provides an ethical foundation to which individuals within teams and the team as a whole can appeal. The Code helps to define those actions that are ethically improper to request of a software tester or for a software tester to perform.

A distinguishing mark of a profession is acceptance of its responsibility to the public. The Code prescribes these as obligations of anyone claiming to be or aspiring to be a software tester.

Certified software testers shall commit themselves to making the analysis, specification, design, development, testing and maintenance of software a beneficial and respected profession. In accordance with their commitment to the health, safety and welfare of the public, software testers shall adhere to the following Eight Principles:

PUBLIC - Certified software testers shall act consistently with the public interest.

CLIENT AND EMPLOYER - Certified software testers shall act in a manner that is in the best interests of their client and employer consistent with the public interest.

PRODUCT - Certified software testers shall ensure that the deliverables they provide (on the products and systems they test) meet the highest professional standards possible.

JUDGMENT - Certified software testers shall maintain integrity and independence in their professional judgment.

MANAGEMENT - Certified software testing managers and leaders shall subscribe to and promote an ethical approach to the management of software testing.

PROFESSION - Certified software testers shall advance the integrity and reputation of the profession consistent with the public interest.

COLLEAGUES - Certified software testers shall be fair to and supportive of their colleagues.

SELF - Certified software testers shall participate in lifelong learning regarding the practice of their profession and shall promote an ethical approach to the practice of the profession.

II is not part of the code of ethics, as it is not always required or appropriate for certified software testers to sign a NDA (Non Disclosure Agreement) in presence of customer data.

Integration testing is the process of testing the interactions between different components or subsystems of a system. It has the following characteristics:

It can be done in an incremental manner, meaning that components or subsystems are integrated and tested one by one until the whole system is integrated and tested.

It is usually done before system testing, which is the process of testing the system as a whole against its requirements and specifications.

It includes functional tests, which are tests that verify the functionality and behavior of the system or its components.

It includes non-functional tests, which are tests that verify the quality attributes of the system or its components, such as performance, reliability, security, etc.

Therefore, statements I, III, and IV are correct.

References: Certified Tester Foundation Level Syllabus, Section 5.1.2 and 5.2.2