Automation

What Is Keyword-Driven Testing?

Keyword-driven testing is a test automation approach where test steps are represented as keywords (action words) in a table, abstracting the underlying automation code so that non-technical testers can design and maintain tests.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

In Depth

In a keyword-driven framework, each keyword maps to a reusable function. A test might read: Open Browser > Navigate To "https://app.com/login" > Enter Text "email_field" "user@test.com" > Click "submit_btn" > Verify Text "Welcome." The keywords are defined once in a library, and tests are composed by combining them in spreadsheets or structured files.

This approach bridges the gap between technical automation engineers and domain-expert testers who may not code. The automation team builds and maintains the keyword library, while QA analysts create test scenarios using familiar vocabulary. Tools like Robot Framework are built around this paradigm.

The trade-off is flexibility versus abstraction. Keyword-driven tests are easy to read and maintain for standard workflows but become awkward for complex logic, conditional branching, or dynamic data. Most mature automation teams use keyword-driven testing for high-level smoke and regression tests while reserving script-based testing for complex scenarios.

Why Interviewers Ask About This

Interviewers ask about keyword-driven testing to evaluate your understanding of framework architectures and your ability to make testing accessible to non-technical team members.

Example Scenario

A QA analyst creates a keyword-driven test for order placement: Open_Browser, Login "admin" "password", Search_Product "Widget A", Add_To_Cart, Checkout, Verify_Order_Confirmation. The analyst writes no code. The SDET maintains the keyword implementations and adds new keywords as features are built.

Interview Tip

Compare keyword-driven testing with data-driven testing and explain when you would choose each. Mentioning Robot Framework as a concrete tool implementation strengthens your answer.