Robot Framework Test Templates

A Complete Guide to Writing Reusable Tests in Robot Framework

As test automation projects grow, maintaining hundreds or thousands of test cases becomes challenging. Repeating the same test steps across multiple test cases increases maintenance effort and makes automation suites harder to manage. Robot Framework Test Templates provide an effective solution by allowing testers to define a common workflow once and execute it with different test data. This approach improves test readability, reduces duplication, and supports data-driven testing in the Robot Framework.

What Are Robot Test Templates in Robot Framework?

A Robot Test Template is a feature in Robot Framework that allows a single keyword to act as the main structure of a test case. Instead of writing the same sequence of keywords repeatedly, you define the workflow once and provide different arguments for each test case.

Templates are commonly used for:

• Data-driven testing
• Repetitive workflows
• Multiple input validation scenarios
• Login testing
• Form submission testing
• API testing with different request data

With templates, the test case becomes a collection of test data rather than a collection of repeated automation steps.

Why Use Robot Test Templates?

Using test templates provides several advantages:

1. Reduces Test Code Duplication

Without templates, multiple test cases may contain identical steps.

Example:

*** Test Cases ***
Valid Login Test
    Open Browser
    Enter Username
    Enter Password
    Click Login Button
    Verify Dashboard
Invalid Login Test
    Open Browser
    Enter Username
    Enter Password
    Click Login Button
    Verify Error Message

The login workflow is repeated, making future changes difficult.

With templates, the workflow can be reused.

2. Supports Data-Driven Testing

Templates allow you to separate test logic from test data.

Instead of creating separate test cases for every input combination, you can provide different values.

Example:

*** Test Cases ***
Login With Different Users
    [Template]    Login Test
    user1    password1
    user2    password2
    user3    password3

The same keyword runs multiple times with different arguments.

3. Improves Test Readability

A well-designed template makes test cases easier to understand. Testers can focus on scenarios and expected results instead of implementation details.

Creating a Robot Test Template

A template can be defined at the test case level using the [Template] setting.

Basic Template Example

*** Settings ***
Library    SeleniumLibrary
*** Test Cases ***
Login Test With Multiple Users
    [Template]    Verify Login
    admin    admin123
    tester   test123
*** Keywords ***
Verify Login
    [Arguments]    ${username}    ${password}
    Open Browser    https://example.com    Chrome
    Input Text      username_field    ${username}
    Input Password  password_field     ${password}
    Click Button    login_button
    Page Should Contain    Welcome

Here:

• Verify Login is the template keyword.
• Each row provides different test data.
• Robot Framework executes the keyword once for every data row.

Using Templates with Arguments

Templates become powerful when keywords accept arguments.

Example:

*** Test Cases ***
Search Products
    [Template]    Search Product
    Laptop
    Mobile Phone
    Headphones
*** Keywords ***
Search Product
    [Arguments]    ${product}
    Open Browser    https://shop.example.com    Chrome
    Input Text      search_box    ${product}
    Click Button    search_button
    Page Should Contain    ${product}

Each test iteration receives a different product name.

Test Templates with Multiple Arguments

Robot Framework templates support multiple parameters.

Example:

*** Test Cases ***
User Registration Tests
    [Template]    Register User
    John    john@test.com    Password123
    Mary    mary@test.com    Password456
*** Keywords ***
Register User
    [Arguments]    ${name}    ${email}    ${password}
    Input Text    name_field      ${name}
    Input Text    email_field     ${email}
    Input Text    password_field  ${password}
    Click Button  submit_button

This structure is useful for testing multiple combinations.

Template at Suite Level

Instead of defining templates for individual tests, you can define a default template for an entire test suite.

Example:

*** Settings ***
Test Template    Validate User Login

All test cases in that suite will automatically use the specified keyword as their template.

This is useful when an entire test file follows the same execution pattern.

Difference Between Normal Tests and Template Tests

Best Practices for Robot Test Templates

1. Keep Template Keywords Simple

A template keyword should represent one clear business action.

Good:

Verify Login
Submit Registration Form
Validate API Response

Avoid creating large keywords that perform unrelated activities.

2. Use Meaningful Argument Names

Poor:

[Arguments]    ${a}    ${b}

Better:

[Arguments]    ${username}    ${password}

Clear names improve maintainability.

3. Combine Templates with External Test Data

For large test suites, store data separately using:

• CSV files
• Excel files
• JSON files
• Database tables

This keeps test logic separate from test data.

4. Avoid Overusing Templates

Templates are useful for repetitive scenarios, but not every test requires them.

Use normal test cases when:

• The workflow is unique
• The steps vary significantly
• Debugging readability is more important

Common Mistakes When Using Robot Test Templates

Mistake 1: Putting Too Much Logic Inside Templates

A template keyword should not become a complete automation framework. Keep business logic inside reusable keywords.

Mistake 2: Using Templates for Unrelated Tests

If scenarios have different workflows, forcing them into one template can reduce readability.

Mistake 3: Ignoring Test Documentation

Even template-based tests should contain clear descriptions.

Example:

*** Test Cases ***
Invalid Password Login
    [Documentation]    Verify login failure with incorrect password
    [Template]    Login Validation
    admin    wrongpassword    Invalid credentials

Robot Test Templates in Real Automation Projects

In enterprise automation frameworks, templates are commonly used for:

• Authentication testing
• API parameter validation
• Form testing
• Database validation
• Cross-browser testing
• Role-based access testing

They are especially valuable when hundreds of similar scenarios need execution with different input combinations.

Frequently Asked Questions (FAQ)

What is a Robot Framework test template?

A Robot Framework test template allows a keyword to define the execution flow while individual test cases provide different input data.

Are Robot Test Templates useful for data-driven testing?

Yes. Templates are one of the primary ways to implement data-driven testing in Robot Framework.

Can Robot templates have multiple arguments?

Yes. Template keywords can accept multiple arguments, allowing complex test scenarios with different input combinations.

Should every Robot Framework test use templates?

No. Templates should be used when multiple tests share the same workflow. Unique scenarios are usually better written as normal test cases.

Conclusion

Robot Test Templates are a powerful feature for creating clean, scalable, and maintainable automation suites. By separating test logic from test data, templates help teams reduce duplication and implement efficient data-driven testing.

When used correctly, Robot Test Templates make automation frameworks easier to maintain and allow testers to create large test suites without unnecessary complexity.

In the next articles of this Robot Framework Test Automation series, we will explore advanced topics such as custom keywords, test data management, libraries, and framework design patterns.

Related Articles

• What is Robot Framework?
• Framework Architecture
• Installation
• Installing Browser Library
• Browser Library vs SeleniumLibrary
• Writing Your First Browser Test
• Sections in Robot Test File
• Robot Resource Files