iSQI ISTQB Certified Tester Foundation Level CTFL_Syll2018 Exam Practice Test

Answer : D

Testers being involved in reviewing documents as soon as they are approved is not a characteristic of good testing, independent of the development life cycle model.Testers should be involved in reviewing documents as soon as drafts are available, not after they are approved, as this can help to detect defects early, improve communication and collaboration, and reduce rework and costs2states this as follows:

Testers should be involved in reviewing documents such as requirements specifications or user stories as soon as drafts become available in order to provide early feedback on testability aspects such as clarity, consistency, completeness, correctness, unambiguity etc.

Early involvement of testers in reviewing documents can help to prevent defects from being introduced into later phases of development or testing by identifying potential issues or gaps before they become embedded in the system under test.

A, B, and C are characteristics of good testing, independent of the development life cycle model. Each test level having objectives specific for the test level (A) ensures that testing is aligned with the purpose and scope of each level and provides clear criteria for success. Every development activity being matched by a corresponding testing activity (B) ensures that testing is integrated with development and provides continuous feedback on quality and progress. Testers being involved in reviewing documents as soon as drafts are available ensures that testing is performed early and throughout the life cycle and provides input on testability aspects.

Answer : D

Pair programming is a software development technique where two programmers work together on the same code at the same workstation. One programmer, called the driver, writes the code while the other programmer, called the navigator, reviews the code and provides feedback and suggestions. Pair programming is not only a coding technique but also an informal review method because it involves constant communication and collaboration between the programmers who check each other's work and share their knowledge and skills. Pair programming can improve the quality and productivity of software development by reducing defects, increasing code readability, enhancing learning opportunities, and fostering creativity and innovation. Pair programming is usually used in agile methods such as Extreme Programming (XP), Scrum, or Kanban. It is not an alternative term for code inspection, which is a formal review method where a group of reviewers examine a piece of code in a structured and systematic way following predefined rules and roles. It is also not done with developer and tester pairing together because pair programming requires both programmers to have similar levels of expertise and familiarity with the code they are working on. You can find more information about pair programming inA Study Guide to the ISTQB Foundation Level 2018 Syllabus, Chapter 31.

Answer : C

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.

Answer : A

State transition testing is the most suitable test technique for this situation. State transition testing is a technique that uses scenarios based on state diagrams to test the behavior of a system or component that can change its state in response to events or inputs. A state diagram is a graphical representation of the states that a system or component can be in, the events or inputs that can trigger a change of state (transitions), and the actions or outputs that can occur as a result of a change of state. In this case, the vending machine for light drinks can be modeled as a state diagram with states such as ''idle'', ''coins inserted'', ''drink selected'', ''drink dispensed'', ''change returned'', ''sold out'', etc., and transitions triggered by events such as ''button pressed'', ''coins inserted'', ''drink dispensed'', ''change returned'', etc. State transition testing can help design test cases that cover all the possible states and transitions of the vending machine and verify its functionality and usability.

Answer : A

(0, 12, 13,18,19) represent boundary values for the age groups. Boundary value analysis is a technique to test the values at the boundaries of an input domain or equivalence partition. explains this as follows:

Boundary value analysis (BVA) is based on testing the boundary values of valid and invalid partitions. The behavior at the edge of each equivalence partition is more likely to be incorrect than the behavior within the partition, so boundaries are an area where testing is likely to yield defects.

(-1,0,11,12,13,14,18,19) (B) are not boundary values, but include some boundary values and some non-boundary values. (4,5,15,20) are not boundary values at all. (-1.0,12,13,18,19) (D) are not boundary values either, as -1.0 is not an integer value.

Answer : C

The goal of statement testing is to increase the percentage of executable statements that are exercised by a test set.This is also known as statement coverage or line coverage3defines this as follows:

Statement Coverage (also known as Line Coverage) measures how many statements have been executed by your tests. It's calculated by dividing the number of executed statements by total number statements in source code file.

Statement testing does not aim to reduce the number of tests needed to test the system (A), assess the correctness of key statements in each module of the application (B), or assess the number of code statements needed to implement each feature (D).

Answer : D

Mr; Mrs.; Ms; any other input is the correct list of the equivalence classes of the input values for this field. 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 case3explains this 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 field can be divided into four partitions: Mr, Mrs., Ms, and any other input. The first three partitions are valid, as they are the only acceptable values for this field. The last partition is invalid, as it includes any value that is not Mr, Mrs., or Ms, such as Dr, Prof, Miss, etc.