ISTQB CTFL-Foundation Exam Questions Instant Access

Question 1

A deviation from the specified or expected behavior that is visible to end-users is called:

Aan error

Ba fault

Ca failure

Da defect

Answer : C

A deviation from the specified or expected behavior that is visible to end-users is defined as a 'failure.' According to the ISTQB CTFL Syllabus, version 4.0:

An error is a human action that produces an incorrect result.

A fault (also known as a defect or bug) is a flaw in a component or system that can cause the system to fail to perform its required function.

A failure occurs when a fault is executed, leading to a deviation from the expected behavior, and this deviation becomes apparent to the end-users.

Thus, a visible deviation from the specified or expected behavior is termed a failure in the context of software testing.

Question 2

To test a function, the programmer has to write a _________, which calls the function to be tested and passes it test data:

AStub

BDriver

CProxy

DNone of the above

Answer : B

A driver is a piece of code that calls a function or module to be tested and passes it the necessary test data. It is commonly used in bottom-up integration testing to simulate the higher-level modules that invoke the function being tested. Stubs, on the other hand, are used to simulate lower-level modules. Reference: ISTQB CTFL Syllabus V4.0, Section 4.3.1.

Question 3

Refer to the exhibit

The following test cases need to be run, but time is limited, and it is possible that not all will be completed before the end of the test window

The first activity is to run any re-tests, followed by the regression test script. Users have supplied their priority order to tests.

Which of the following gives an appropriate test execution schedule, taking account of the prioritisation and other constraints? [K3]

Ab, c, g, d, e, i, a, f, h

Ba, c, d, b, g, e, i, f, h

Cc, a, d, b, e, g, i, h, f

Dd, c, a, e, b, g, i, f, h

Answer : B

The appropriate test execution schedule considering the prioritization and constraints should start with re-tests, followed by the regression test script. After these, tests should be run based on their priority levels:

a (Re-test defect no 52, Low priority, Re-test)

c (Re-test defect no 26, High priority, Re-test)

d (Run regression test script, Medium priority, Regression)

b (Ability to amend transaction type, High priority)

g (Reprint selected previous sales figures, High priority, Must be run after item e)

e (Print monthly sales figures, Medium priority)

i (Print year-to-date figures, Medium priority)

f (Add special invoice to previous month, Low priority)

h (Account administrator able to amend any previous month's sales figures, Low priority)

This sequence ensures that re-tests and high-priority tasks are completed first, followed by medium-priority tasks, and then low-priority tasks.

Question 4

Which of the following are valid justifications for developers testing their own code during unit testing?

(i) Their lack of independence is mitigated by independent testing during system and acceptance testing.

(ii) A person with a good understanding of the code can find more defects more quickly using white-box techniques.

(iii) Developers have a better understanding of the requirements than testers.

(iv) Testers write unnecessary incident reports because they find minor differences between the way in which the system behaves and the way in which it is specified to work.

A(i) and (ii)

B(i) and (iv)

C(ii) and (iii)

D(iii) and (iv)

Answer : A

It is unlikely that developers will have a better understanding of the requirements than testers, partly because testers work closely with the user community (and may be drawn from it) and partly because developers seldom work with the complete set of requirements in a medium to large development.

Testers may raise incidents related to the difference between user expectations and the specification, but these are not unnecessary. Such issues are more likely to arise at the later stages of testing.

Early testing (unit testing) is usually done most effectively by developers with a good understanding of the code and the development environment; they can be more efficient and more effective at this level. Later independent stages of testing offset any disadvantage from the lack of independence at unit testing level.

Question 5

What content would be in an incident report if that incident report was based on the IEEE 829 Standard for SoftwareTest Documentation?

(i) Identification of configuration items of the software or system.

(ii) Software or system lifecycle process in which the incident was observed.

(iii) Description of the anomaly to enable reproduction of the incident.

(iv) Number of occurrences of the incident.

(v) Classification of the cause of the incident for metrics and for reporting purposes.

Number of correct answers: 1

Ai, ii, iii

Bii, iii

Ci, iii, iv

Di, ii, iii, v

Answer : D

According to the IEEE 829 Standard for Software Test Documentation, an incident report should include the identification of configuration items of the software or system (i), the software or system lifecycle process in which the incident was observed (ii), a description of the anomaly to enable reproduction of the incident (iii), and the classification of the cause of the incident for metrics and reporting purposes (v). The number of occurrences of the incident is not typically included.

Question 6

An input field takes the year of birth between 1900 and 2004. The boundary values for testing this field are:

A0,1900,2004,2005

B1900, 2004

C1899,1900,2004,2005

D1899, 1900, 1901,2003,2004,2005

Answer : C

Boundary value analysis focuses on the values at the edges of equivalence partitions. For an input range of 1900 to 2004, the boundary values are just inside and just outside the range:

Just inside: 1900, 2004

Just outside: 1899, 2005

Therefore, the boundary values are 1899, 1900, 2004, and 2005. Reference: ISTQB CTFL Syllabus V4.0, Section 4.2.1.

Question 7

For which of the following activities in the fundamental test process would an incident management tool be most useful?

ATest planning and control

BTest analysis and design

CTest implementation and execution

DEvaluating exit criteria and reporting

Answer : C

Incident management tools are most useful during test implementation and execution as this is the stage at which the tool is used to raise, manage, retest and close incidents.

The data collected during the defect life cycle can then be manipulated into information that is useful for other activities within the fundamental test process.

Information on numbers of defects outstanding may be useful for evaluating exit criteria (option (D)). This information could also be used for planning future testing and for taking control (option (A)).

Incident management tools can also assist in test analysis and design (option (B)) as information about defects found when testing the previous release of the system could be used when analyzing the type of testing required for the next enhancement.

ISTQB Certified Tester Foundation Level CTFL-Foundation Exam Questions