Testlum IDE Recorder - TestlumFramework/Testlum GitHub Wiki

๐ŸŽฅ Using the Web Recorder

The Web Recorder in Testlum IDE helps you build test scenarios by simply interacting with your website.
No need to manually add steps โ€” just click, type, and navigate as a user would, and the recorder will capture everything for you.


โœจ What Is the Web Recorder?

The Web Recorder is a built-in tool that:

  • ๐Ÿ–ฑ๏ธ Records your real-time interactions with a web page
  • ๐Ÿ”ง Converts them into structured test steps inside your current scenario
  • ๐Ÿง  Auto-detects actions, elements, inputs, waits, and assertions
  • ๐Ÿ’พ Saves all steps directly into the Testlum IDE

This allows anyone โ€” even without coding skills โ€” to quickly build reliable test scenarios by example.


๐Ÿš€ How to Start Recording

  1. Click on the special button to launch recorder app

recorder-1.png

!IMPORTANT In opened recorder You would see only scenarios without semantic errors. So make sure that test scenario which You want to see in recorder is valid

  1. Click on Start button in opened app

recorder-2.png

  1. After that recorder will automatically open website from ui.xml settings. So make sure that You provided needed website URL.

recorder-3.png

  1. Choose an existing testing scenario in right window (or create a new one right in the Recorder by clicking on Add button and fill necessary information, such as name, description and location). Click on Record button and start doing interactions with website

recorder-4.png

  1. After that You can verify recorded actions. Make some changes right in recorder and switch back to IDE to verify that all recorded actions were successfully transfered to Your automation test.

  2. Recorder also will generate a list of all possible locators for each web element You interacted with and place them in generated file inside locators/pages folder

  3. Click Stop Recording in the IDE when done

โœ… Your test steps will be automatically added to the open scenario.


๐Ÿ’ก What Gets Captured?

The recorder can capture and generate steps for all web commands in Testlum except:

  • javascript
  • repeat
  • condition

๐Ÿ›  Post-Recording Actions

After recording:

  • You can review, edit, or rearrange the recorded steps
  • Add assertions or variables to validate behavior
  • Parameterize values for reuse or data-driven testing

The recorder gives you a solid starting point, and you can always fine-tune steps in the visual editor.


๐Ÿงช Configuration Tab

From Configuration Tab in the left Recorder window You can:

  • Record such actions as: tab (switch, open, close), navigate (by clicking on Go button). All these steps will be recorded only when recording is enabled from right window of the Recorder
  • Configure automatic wait command adding with configured time to wait after each recorded step
  • Automatic screenshoots capturing after each recorded step with configured match percentage and flexible screen resolution changing

recorder-5.png

โœ… Assertion Mode

Assertion Mode allows you to quickly verify elements, values, and behaviors in your application
without writing code โ€” simply select what you want to validate.

๐Ÿš€ How to Use Assertion Mode

  1. Start recording in the right Recorder window
  2. Click the ๐Ÿ” Assertion Mode button
  3. Hover over any element โ€” youโ€™ll see an outline around it
  4. Click the element to record assetion of web element presence

recorder-6.png

๐Ÿ” Customizing Locators

When recording user actions, our tool automatically generates locator IDs (used to identify elements in your tests). By default, these IDs follow a standard pattern, but you can customize both the format and the storage location.

After recording of particular step You can open generated details of the recorded command and change generated locator id using Locator Id input field.

Or change Locator File to existing file in Your project in IDE from the drop down or input a new file location inside pages folder and we will automatically create file with locator in specified place

Custom locator IDs help:

  • Improve test readability
  • Reduce test fragility
  • Match existing project naming conventions

recorder-7.png