iSQI CTFL_Syll2018 - ISTQB Certified Tester Foundation Level (Syllabus 2018)

A test completion report for a test level typically includes a summary of all the testing activities that have been performed. It should detail any deviations from the original test schedule, including any changes in the planned duration or effort that were required to complete the test activities. This report serves as a record of what was tested, how it was tested, and any issues that were encountered.

Any software development product can undergo static testing, including requirements specifications, design specifications, code, test cases, test plans, user manuals, etc. 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 help find defects and improve the quality of any software development product at any stage of the software development lifecycle.

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

 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.

The statement that use case testing is designed to find defects in the process flow is true, because use case testing is a technique that tests the end-to-end user interactions and outcomes based on use cases or scenarios that describe how the software under test should be used . Use case testing can help to find defects in the process flow, such as missing steps, incorrect sequences, or invalid transitions . The other options are not true statements about use case testing. Option A is false, because use case testing is not designed to be used by real users, but rather by professional testers who design and execute test cases based on use cases or scenarios . Option C is false, because use case testing is not designed to find defects in the data flow, but rather in the process flow. Data flow testing is a different technique that tests how data values are defined, used, and modified by the software under test . Option D is false, because use case testing is not always designed by customers or end users, but rather by testers who analyse the requirements or specifications of the software under test to identify use cases or scenarios .

Boundary value analysis is a technique to test the values at the boundaries of an equivalence partition. In this case, the age variable has two equivalence partitions: less than 30 and greater than or equal to 30. The boundary values are 29 and 30. The expected result for age 29 is that the premium is increased by 1500, so the final value is 4000. The expected result for age 30 is that the premium remains unchanged at 2500. This is explained in the syllabus under section 4.3, "Black-box Test Techniques"1. References: Certified Tester Foundation Level (CTFL) Syllabus - ASTQB

Gaining confidence about the level of the system’s quality can be a common objective of testing, because testing can provide information about how well the system meets its specified requirements and user expectations, and how many defects have been found and fixed in the system.

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.

Explanation of Correct Answer: A benefit of running tests with a test automation tool is that the time spent on repetitive tasks is reduced, as the tool can execute tests faster and more reliably than humans. Therefore, option D is correct. Option A is incorrect, as test coverage is not increased by using a test automation tool, but by designing more effective test cases. Option B is incorrect, as the number of found bugs is not reduced by using a test automation tool, but by improving the quality of the software under test. Option C is incorrect, as the total cost of the test project does not always decrease by using a test automation tool, as there are costs associated with developing and maintaining the automated tests.

References: Certified Tester Foundation Level Syllabus, Section 6.1

Less than 0, 1 to 80, more than 80 is a valid collection of equivalence classes for the following problem: “An Integer numeric field shall contain values from 1 to 80 both values inclusive”. Equivalence partitioning is a technique to divide the input domain into partitions that are expected to behave similarly or produce the same output. Each partition should have at least one representative value as a test case2 explains equivalence partitioning as follows:

Equivalence Partitioning (or Equivalence Class Partitioning) is an software testing technique that divides the input data of a software unit into partitions of equivalent data from which test cases can be derived. In principle, test cases are designed to cover each partition at least once.

The fundamental concept of Equivalence Partitioning is that you can find more errors in a test case by using a representative value from an equivalence class than by using any other value from the class.

The input domain for this problem can be divided into three partitions: less than 0, 1 to 80, and more than 80. The first and the last partitions are invalid, as they are outside the range of acceptable values for this field. The middle partition is valid, as it is within the range of acceptable values for this field.

A, C, and D are incorrect answers. A does not include 0 as an invalid partition. C does not include 0 as an invalid partition. D does not include 80 as a valid partition.