Capture Objects for your Tests

Capturing objects in SimplifyQA is essential for automating test cases. It allows the system to identify and interact with elements like buttons, text fields, dropdowns, etc., during test execution.

Methods to Capture Objects in SimplifyQA

  1. Capturing Objects Using the SimplifyQA Recorder

The SimplifyQA Recorder helps capture UI elements automatically from web or mobile applications.

Steps to Capture Objects:

Opening the Recorder

  • Click on the Recorder button located at the top-right corner of the SimplifyQA interface.

Entering Mandatory Details

  • Fill out the required details:

    • Name: Provide a meaningful name for the recording session.

    • URL: Enter the URL of the web application you want to test.

    • Browser: Select the browser in which you want to record the test.

Starting the Recording

  • Click on Start Recording to initiate the session.

  • The tool will launch the web application in the selected browser.

Capturing Objects while Navigating the Application

  • As you hover over different elements in the application, a blue highlight will appear, indicating the objects being identified by the tool.

  • Any action performed on these objects (click, input text, select, etc.) will be recorded back into the tool, including the captured objects.

Viewing Recorded Steps and Captured Objects

  • Navigate back to the SimplifyQA tool to review the recorded steps.

  • All recorded actions and captured objects will be displayed in the tool.

Viewing Object Details & Attributes

  • Click on any captured object to open its details.

  • The tool captures multiple attributes of each object to ensure smooth execution, even if minor changes are made to the application.

  • The attributes include:

    • XPath

    • CSS Selector

    • ID, Class, Name, Tag, etc.

Editing and Managing Objects

  • Objects can be edited when viewing their details:

    • Rename objects for better clarity.

    • Add new attributes to improve object recognition.

    • Set a default attribute for execution stability.

  1. Manually Adding Objects

Method 1: Adding Objects from a Test Case

You can add objects directly within a test case while defining steps.

Steps to Add an Object from a Test Case:

  • Open the Test Case where you need to add an object.

  • In the Steps section, locate the object field.

  • Click on the "+" icon in the object field

  • A create object popup will appear

  • Fill out the mandatory fields:

    • Name: Provide a unique idntifier for the object.

    • Object Template: Select the type of object (Web, API, Generic, Database, etc.)

    • Technology: Choose the technology (Web, Mobile, Desktop).

    • Xpath: Enter the XPath or other locator details.

  • Click Save to create the object.

  • The object will be added to the Object field and can now be used in the test case.

Method 2: Adding Objects from the Object Repository

Objects can also be created separately in the Object Repository, making them reusable across multiple test cases.

Steps to Add an Object from the Object Repository:

  • Navigate to the User Navigation Panel.

  • Go to Test Management > Object Repository.

  • Click the "+ Object" button.

  • The Create Object popup will appear (similar to Method 1).

  • Enter the required details:

    • Name

    • Object Template (Web, API, Generic, Database, etc.)

    • Technology (Web, Mobile, Desktop)

    • XPath or other locator information

  • Click Save to store the object in the repository.

  • The newly created object can now be used in any test case when needed.

  1. Using Captured Objects in your Test Case

After capturing objects, you can reference them in your test steps.

Example: Login Test Case

STEP

OBJECT NAME

ACTION

PARAMETER

1

username_field

Enter Text

testuser

2

password_field

Enter Text

password123

3

login_button

Click

During execution, SimplifyQA will fetch the object from the repository and interact with the UI accordingly.

Best Practices for Capturing Objects

  • Use Unique Identifiers: Prefer stable locators like ID or Name over dynamic XPath.

  • Group Related Objects: Organise objects by screens (e.g., LoginPage, DashboardPage).

  • Use Descriptive Names: Instead of button1, use submit_button.

  • Verify Objects Before Execution: Ensure objects are captured correctly by testing them before running automation.

Troubleshooting Object Capture Issues

What does the "Object Not Found" error mean?

This error indicates that the system could not locate the specified object on the screen or within the application.

Common reasons include:

  • The locator is incorrect or outdated.

  • The object’s properties have changed due to application updates.

  • The object is dynamic or temporarily invisible at the time of execution.

  • Changes in the application’s structure affecting how elements are identified.

To fix this error:

  • Verify that the locator is correctly defined and accurately points to the intended element.

  • Update the locator if it no longer matches the current element properties.

  • Check for dynamic content, visibility issues, or UI changes in the application that might affect object recognition.

How to handle dynamic elements?

Some elements on a webpage or application may have attributes that change dynamically, such as IDs, class names, or other properties. These elements can be challenging to locate using static locators. To handle such cases, use parameterised XPath expressions or regex-based locators that allow flexibility in identifying elements.

PreviousIntroduction to Object RepositoryNextOrganise your Test Objects

Last updated