Courseiva
Test Tools →mediumMultiple Choice

CTFL-v4 Test Tools Practice Question

Which of the following describes a 'Keyword-Driven' testing approach?

⚠ Common exam trap

Candidates often confuse keyword-driven testing with data-driven testing. They mistakenly focus on the data aspect rather than the abstraction of actions into reusable keywords that separate logic from implementation.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Keywords are used to represent actions, separating test logic from implementation.

Keyword-driven testing abstracts the technical details of the test scripts by using a set of predefined keywords that represent specific actions. This allows testers with limited programming knowledge to participate in test creation. It significantly enhances collaboration between technical and business staff, improves test maintainability, and allows for the easy reuse of actions across different test cases, which is highly beneficial for large, evolving software projects with complex functional requirements.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Tests are written entirely in the application's native programming language.

    Why it's wrong here

    That approach is standard scripting, not keyword-driven testing. Keyword-driven testing is designed to separate the action logic from the code, allowing for a more accessible interface for testers who are not developers. Forcing testers to use the application's native language negates the primary benefit of the keyword-driven abstraction layer.

  • ✓

    Keywords are used to represent actions, separating test logic from implementation.

    Why this is correct

    The core of keyword-driven testing is the separation of high-level test steps (represented by keywords) from the low-level implementation logic. This allows testers to define test cases in a readable format, such as a spreadsheet, while the underlying framework handles the execution. This decoupling greatly improves maintainability and reusability of scripts.

  • ✗

    The tool automatically generates test cases based on random user input.

    Why it's wrong here

    This is a description of random/fuzz testing, not keyword-driven testing. Keyword-driven testing requires explicit design of the test steps using keywords. It is a structured, intentional approach to testing, whereas random input generation is a method for stress testing and error discovery, which lacks the predictability of keyword-driven test scenarios.

  • ✗

    The tool executes tests by recording all mouse movements on the screen.

    Why it's wrong here

    This is a description of a standard Capture/Playback tool, not a keyword-driven framework. Capturing mouse movements is a low-level, brittle approach. Keyword-driven testing focuses on logical actions like 'LOGIN' or 'VERIFY_BALANCE' rather than specific cursor coordinates, which makes the tests much more robust to UI layout changes.

About these practice questions

This CTFL-v4 question is part of Courseiva's 144-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official ISTQB exam blueprint

This CTFL-v4 practice question is part of Courseiva's free ISTQB certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CTFL-v4 exam.