iSQI CTFL-AcT Exam With Confidence Using Practice Dumps

Exploratory testing is an unscripted, experience-based testing technique where the tester learns about the system, designs tests, and executes them simultaneously. It is especially effective in Agile environments, where rapid feedback and creative exploration are valuable.

Option D is the least likely action because scripting automated test scripts is a structured activity that typically occurs after exploratory sessions or during more formal test phases. Exploratory testing emphasizes manual exploration, not automation scripting.

Other options:

A is part of the core purpose of exploratory testing — discovering the product.

B is relevant — defining a charter and discussing it with stakeholders (like the Product Owner) helps guide the exploratory session.

C is also relevant — results of exploratory tests should be documented and communicated.

Answer: D. Scripting of the automated test scripts

Comprehensive Detailed Explanation (Approx. 200 words):

Acceptance criteria should focus on business-relevant outcomes that are specific, testable, and observable. In this user story, the goal is to validate that the registration functionality is available and behaves as expected.

Let's analyze each proposition:

i) “A registration form is displayed on the screen.”

→ Valid. It is observable, specific, and directly aligned with the user story.

ii) “The form is written in the Groovy language; the cursor is initially set on the ‘login’ field...”

→ Invalid as acceptance criteria. It contains implementation details (e.g., “Groovy language”) irrelevant to business stakeholders. Also, low-level UI behavior like cursor position is overly technical and not a business-driven criterion.

iii) “I cannot register myself if the login I choose is used by another player.”

→ Valid. It defines system behavior based on a business rule (unique login) and is testable.

iv) “After successful registration process I am informed about it by an e-mail.”

→ Valid. It describes a user-visible outcome after registration, which is observable and testable.

Correct answer: D. only i), iii), and iv) are well-written acceptance criteria.

Exact Reference – ISTQB CTFL Acceptance Testing Syllabus (Section 1.3.2):

“Acceptance criteria must describe the externally visible and verifiable system behavior, excluding implementation details.”

Equivalence Partitioning (EP) is a black-box test design technique that divides input data into valid and invalid partitions, where each partition is expected to exhibit similar behavior. In the context of acceptance testing, EP is especially effective because it helps validate whether a system behaves correctly for representative input ranges defined in the acceptance criteria.

Acceptance testing aims to confirm that the system meets business requirements and handles inputs as expected. EP allows the tester to cover a large input space using fewer test cases while maintaining a high level of effectiveness. It supports efficiency, broad coverage, and relevance to user expectations.

Other options are less suitable:

A. Static code analysis is a white-box technique, more relevant to unit or integration testing.

B. Input validation is an objective or activity, not a test design technique.

D. Defect-based testing is more diagnostic, used after failures or during exploratory testing — less structured for planned acceptance testing.

Exact Reference – ISTQB CTFL Acceptance Testing Syllabus (Section 2.4):

“Black-box techniques such as equivalence partitioning and boundary value analysis are suitable for deriving acceptance tests from user stories or business rules.”