iSQI CTFL-AcT Exam With Confidence Using Practice Dumps

In Gherkin syntax (Given-When-Then), the purpose is to describe system behavior in a way that’s understandable to all stakeholders. Test steps should focus on user intentions and observable results — not UI implementation details — to ensure maintainability and abstraction.

Line 3 ("click 'Buy Tickets' button") refers explicitly to a UI element, which should generally be avoided in acceptance tests. Instead, it could say "I request to buy tickets."

Line 7 ("I should provide my personal data") is describing an action the user must take, not an outcome or result. In a Gherkin “Then” step, we expect an observable system response, not further user interaction.

Option C identifies both of these review concerns correctly.

Other options:

A includes an incorrect comment about line 4 ("quantity should not be set") — setting a value is acceptable.

B is false — the test case has reviewable issues.

D might be valid in a different context (e.g., boundary tests), but that’s not a flaw in the existing scenario.

Answer: C. Line 3 refers to an element of the user interface, which is to be avoided and line 7 is an action and not a result

Performance testing assesses how a system behaves under specific conditions, typically focusing on responsiveness, stability, and resource usage. The type of performance test depends on the workload model:

Load testing evaluates performance under expected peak usage.

Stress testing pushes the system beyond its capacity to assess limits.

Endurance/stability testing checks for performance degradation over extended periods.

Option A correctly describes that performance test types are determined by the workload simulation strategy.

Other options:

B confuses performance with security testing — malicious attack robustness is a security focus, not performance.

C is partly correct but less comprehensive than A. While testing should simulate realistic conditions, categorization into stress/load/endurance is better aligned with workload modeling.

D is misleading — performance tests validate systems against performance requirements; they are not primarily used to define them.

Answer: A. Depending on the model used to simulate the workload, performance tests are called load, stress or endurance / stability tests.

Acceptance Test-Driven Development (ATDD) involves early collaboration between stakeholders to define acceptance criteria and tests before development begins. Using business process models in ATDD helps visualize user behavior, align test cases with real workflows, and serve as living documentation.

Option C is the least meaningful argument because:

Business process models abstractly describe workflows and decisions at a business level. While they help clarify requirements and detect requirement-related defects, they do not directly support detecting defects in the application code, which is typically the focus of unit and integration testing, not acceptance testing.

Let’s validate the other options:

A is a strong argument — process models clarify use cases for testers.

B is valid — graphical models help visualize test coverage directly.

D is true — as business process models evolve, they remain valuable artifacts aligned with current system behavior and requirements.

Answer: C. Business process models will make it easier to detect defects in the application code.