​
Overview

The Fill step allows you to input text into form fields, text areas, and other input elements. It supports environment variables, supatest variables from previous steps, and dynamic dummy data generation.

​
Form Fields

Field NameTypeRequiredDescription
LocatorstringYesCSS selector for the input element
Text to Filltext/dropdownConditionalText to enter, or selection from variables declared in previous steps
Use variables ToggletoggleNoUse variables from previous steps instead of manual text
Random Data ToggletoggleNoGenerate random dummy data instead of manual text
Variable NamestringConditionalName to store generated dummy data (required when using random data)

​
Form Configuration

​
Locator Field

  • Text input field for entering CSS selectors
  • Supports element picker for visual selection
  • Shows validation and locator suggestions

​
Text Input Options

The form provides three mutually exclusive input modes:

​
Manual Text Entry (Default)

  • Text to Fill: Standard text input field
  • Supports environment variables using {{VARIABLE_NAME}} syntax
  • Type text character by character during execution

​
Use Variables

  • Use variables Toggle: Enable to show dropdown of available variables that have been declared previously in the test case
  • Text to Fill: Dropdown showing variables from previous steps
  • Available when you have declared variables in previous steps (Extract Text, Run JavaScript, API Request, etc.)

​
Random Dummy Data Generation

  • Random Data Toggle: Enable to show data type selection
  • Text to Fill: Dropdown with categories:
    • Personal: Names, emails, phone numbers, Supatest Email (special testing emails)
    • Address: Streets, cities, postal codes
    • Internet: URLs, usernames, domains
    • Finance: Credit card numbers, currencies
    • Date/Time: Dates, times, timestamps
    • Text: Lorem ipsum, sentences, paragraphs
  • Variable Name: Alphanumeric name to store the generated value for later use
Supatest Email is a special option that generates email addresses specifically for testing with the Check Email step. These emails use the format randomslug@uoz0hbri.mailosaur.net and can receive actual emails during test execution.

​
Examples

​
Basic Text Input

  • Locator: input[name='username']
  • Text to Fill: johndoe
  • Use variables Toggle: Disabled
  • Random Data Toggle: Disabled

​
Using Environment Variables

  • Locator: input[type='password']
  • Text to Fill: {{PASSWORD}}
  • Use variables Toggle: Disabled
  • Random Data Toggle: Disabled

​
Using Variables

  • Locator: input[name='email']
  • Use variables Toggle: Enabled
  • Text to Fill: userEmail (from dropdown of assigned variables)

​
Generating Random Email

  • Locator: input[name='email']
  • Random Data Toggle: Enabled
  • Text to Fill: Internet Email (from Personal category)
  • Variable Name: generatedEmail

​
Generating Random Name

  • Locator: input[name='fullName']
  • Random Data Toggle: Enabled
  • Text to Fill: Person Full Name (from Personal category)
  • Variable Name: customerName

​
Generating Supatest Email for Testing

  • Locator: input[name='email']
  • Random Data Toggle: Enabled
  • Text to Fill: Supatest Email (from Contact category)
  • Variable Name: testEmail
This generates a test email address using the format randomslug@uoz0hbri.mailosaur.net that can be used with the Check Email step to verify emails sent to this address.

​
Best Practices

​
Locator Selection

  • Use specific, stable CSS selectors
  • Prefer data-testid attributes for better test stability
  • Verify input field is enabled and visible

​
Input Strategy

  • Use Manual Text for static, known values
  • Use Environment Variables for sensitive data like passwords
  • Use Use variables Toggle to reuse variables declared in previous steps
  • Use Random Data for realistic test data generation
  • Use Supatest Email when you need to test email functionality with the Check Email step

​
Variable Naming

  • Use descriptive, alphanumeric names for generated data variables
  • Follow consistent naming conventions across your test suite
  • Consider data dependencies when naming variables

​
Common Issues

​
Input Field Issues

  • Verify the input field is visible and enabled
  • Check for input validation requirements (min/max length, format)
  • Handle readonly or disabled states appropriately

​
Environment Variable Problems

  • Ensure environment variables are defined in your test environment
  • Use correct {{VARIABLE_NAME}} syntax with uppercase names
  • Verify variable names match exactly (case-sensitive)

​
Supatest Variables Issues

  • Use variables Toggle only appears when you have declared variables in previous steps
  • Ensure the variable assignment step (Extract Text, Run JavaScript, etc.) executed successfully
  • Check that variable names are unique and properly saved

​
Random Data Generation

  • Variable Name must be alphanumeric only (no spaces or special characters)
  • Each generated variable name should be unique within the test case
  • Consider data format requirements when selecting dummy data types