ISTQB CTFL-Foundation Exam Practice Test Instant Access

Question 1

Incidents would not be raised against

ARequirements

BDocumentation

CTest cases

DImprovements suggested by users

Answer : D

Incidents, or defects, are typically raised against artifacts such as requirements, documentation, and test cases when they do not meet their expected outcomes or contain errors. However, improvements suggested by users are not considered incidents, as they are enhancements or changes that users would like to see, rather than defects in the current functionality or documentation.

Question 2

Test script TransVal 3.1 tests transaction validation via screen TRN 003B. According to the specification (PID ver 1.3 10b iv) the validation screen should not accept future dated transactions. Test script TransVal 3.1 passes. Test script eod 1.4 tests end of day processing and is run after the execution of TransVal 3.1 using data entered during that test

Which of the following is the BEST detail on an incident report? [K3]

ATitle. End of Day failure.. Reproducible. Yes. Description. Script eod 1.4 fails when the first transaction of the day is a future dated transaction. Screen shot of the failure attached.

BTitle. Transaction input screen validation..Reproducible. Yes. Description. Script eod 1..4 fails . Screen shot of the failure attached. Validation of transaction entryon screen TRN-003B should not allow future dated transactions -- see PID ver 1.3 para 10b iv.

CTitle. Screen TRN-003B validation of transaction date.. Reproducible. No. Description. When a future dated transaction is processed by the end of day process, a failure can occur. This does not always happen. Screen shot of the failure attached.

DTitle. Screen TRN-003B validation of transaction date. Reproducible. Yes. Description. Script eod 1.4 fails when the first transaction of the day is a future dated transaction. Screen shot of the failure attached. Validation of transaction entry on screen TRN-003B should not allow future dated transactions -- see PID ver 1.3 para 10b iv.

Answer : D

An effective incident report should provide a clear and detailed description of the issue, including the title, reproducibility, a detailed description of the failure, and any relevant references to specifications. This helps in accurately identifying, reproducing, and resolving the defect. In this case, including the specific reference to the PID and a screenshot helps provide all necessary information for resolving the issue.

Question 3

The four test levels defined for a common V-model testing approach are:

AUnit, integration, system and maintenance.

BFunctional, glass box, incremental and maintenance.

CComponent, integration, system and acceptance.

DUnit, component, functional and alpha/beta.

Answer : C

The four test levels defined for a common V-model testing approach are Component, Integration, System, and Acceptance testing. These levels align with the development stages in the V-model, where each level of testing corresponds to a specific phase in the software development lifecycle, ensuring comprehensive verification and validation of the software.

Question 4

The following statements relate to activities that are part of the fundamental test process.

i. Evaluating the testability of requirements.

ii. Repeating testing activities after changes.

iii. Designing the test environment set-up.

iv. Developing and prioritizing test cases.

v. Verifying the environment is set up correctly.

Which statement below is TRUE?

A(i) and (ii) are part of analysis and design, (iii), (iv) and (v) are part of test implementation and execution.

B(i) and (iii) are part of analysis and design, (ii), (iv) and (v) are part of test implementation and execution.

C(i) and (v) are part of analysis and design, (ii), (iii) and (iv) are part of test implementation and execution.

D(i) and (iv) are part of analysis and design, (ii), (iii) and (v) are part of test implementation and execution.

Answer : D

Evaluating the testability of requirements (i) and developing and prioritizing test cases (iv) are part of the test analysis and design activities. Repeating testing activities after changes (ii), designing the test environment set-up (iii), and verifying the environment is set up correctly (v) are part of the test implementation and execution activities. These distinctions are part of the fundamental test process, which ensures that each phase of testing is appropriately planned and executed. Reference: ISTQB CTFL Syllabus V4.0, Section 1.4.1.

Question 5

Which of the following is true of iterative development?

AIt uses fully defined specifications from the start.

BIt involves the users in the testing throughout.

CChanges to the system do not need to be formally recorded.

DIt is not suitable for developing websites.

Answer : B

Iterative development involves users in the testing throughout the development process. This approach allows for continuous feedback from users, ensuring that the evolving system meets user requirements and expectations. Unlike the traditional waterfall model, iterative development accommodates changes and improvements based on user feedback, making it suitable for dynamic environments like website development. Reference: ISTQB CTFL Syllabus V4.0, Section 2.1.3.

Question 6

What is the main purpose of use case testing?

ATo identify defects in process flows related to typical use of the system.

BTo identify defects in the connections between components.

CTo identify defects in the system related to extreme scenarios.

DTo identify defects in the system related to the use of unapproved programming practices.

Answer : A

The main purpose of use case testing is to identify defects in process flows related to the typical use of the system. Use case testing is a black-box test design technique that is based on use case scenarios. These scenarios help in validating that the system performs correctly for the specific ways in which the users will interact with it. This method is particularly effective in finding issues that users might encounter during real-world usage of the system. Reference: ISTQB CTFL Syllabus V4.0, Section 4.2.4.

Question 7

Before an invoice can be created, an account is required. Before an account can be set up, an account user is required (in order to set up the account). The software is delivered with a master user only, who can only create other types of users. The following test cases have been written to test the high-level structure of the software

a. Create an invoice

b. Amend an invoice

c. Process an invoice (send to customer)

d. Delete an invoice

e. Create an account

f. Create an account user

g. Amend an account user

h. Delete an account user

i. Amend an account

j. Delete an account

Which of the following test procedures would enable all tests to be run? [K3]

Af, g, a, c, b, d, e, i, j, h

Be, i, a, c, b, d, f, g, h, j

Ce, i, f, g, a, c, b, d, h, j

Df, g, e, i, a, b, c, d, j, h

Answer : C

To run all the tests successfully, one must follow the logical sequence dictated by the dependencies between the actions. The process should start with creating the account (e) and setting it up (i), then creating the account user (f) and making any amendments (g). Only after these steps can an invoice be created (a) and processed (c), followed by amending (b) and deleting (d) the invoice. Finally, the sequence concludes with managing the account user and the account itself (h, j). This logical order ensures all dependencies are respected and all functionalities are tested.

ISTQB Certified Tester Foundation Level CTFL-Foundation Exam Practice Test