LogoLogo
  • About SimplifyQA
  • Get Started with SimplifyQA
    • Agile & Non-Agile Framework
    • OS Support
    • SimplifyQA Hosting
      • On-premise Installation Guide
        • Pre-requisites
        • Installation Guide
      • Support and Resources
      • Training and Onboarding
    • Explore SimplifyQA for your Application Lifecycle Management
  • SimplifyQA Installation & Setup
    • Setup QAWizard
    • Register QAWizard
    • Setup Android Device
      • How to enable settings in android device?
      • How to register android device?
      • Setup emulators on Android Studio for automation in SimplifyQA
    • Setup iOS Device
      • How to setup iOS device in Apple Developer Account?
      • How to register iOS device?
  • Get to know your Workspace
    • Blueprint of SimplifyQA
    • Key Terminologies
    • Search/Global Search
      • How to use global search?
      • How to use advance search?
      • How to use column sort?
      • How to use column filters?
      • Add or remove columns
    • Rich Text Editor
    • Import & Export
    • Add Attachments
    • Add Linkages
    • Add Comments
    • Manage Cards in board view
    • Configure Watchlist
    • Track Edit History
    • Hierarchy Tree
  • Admin Controls & Configurations
    • Manage Projects & Users
      • Create Project and Invite Users
      • Project Settings
        • Create and Manage Custom Fields
      • Grant Admin Privilege to User
      • Invite/Add Users to Team
      • User Directory and Access Control
      • Configure Page Layout
      • Manage Roles and Privileges
      • Configure Auto-logging of Defects
    • Configure your clients
    • Password settings
  • Release & Sprints
    • Introduction to Releases
    • Create & Manage Release & Sprint
    • Start & Close a Sprint
  • Create and Manage your Requirements
    • Introduction to Requirement Management
    • Create & Manage Epic
    • Create & Manage Features
    • Create & Manage User Stories
  • Introduction to Test Management in SimplifyQA
    • Create a Manual Test Case in SimplifyQA
    • Create an Automation Test Case in SimplifyQA
    • Learn API Testing in SimplifyQA
      • Create an API Test Case in SimplifyQA
      • Quick Test the API
      • Validating API Responses
      • Understanding API Parameterisation
      • Save API Response Data
      • Achieve Data flow for E2E Testing
    • Create Hybrid Test Case in SimplifyQA
    • Leverage Re-usability in your Tests
    • Organise your Test Cases
    • Linking a Test Case to User Story
    • Linking a Test Case to Defect
    • Version Control your Test Case
    • Create a Copy of your Test Case
    • Copy Test Case to different Project
    • Conditional Statements
      • Decision Making Statement
      • Looping Statement
      • BREAK & CONTINUE Statement
    • Supported Actions
    • Utilising Mobile Inspector in SimplifyQA
  • Introduction to Script-less Recording of Test Case
    • Record a Web Test Case in SimplifyQA
    • Record an Android Test Case in SimplifyQA
      • Record an Android Test Case
    • Record Functions in SimplifyQA
    • Understand Object Recognition Mechanism & Self Healing in SimplifyQA
  • Test Data Management
    • Work with the Formulas to Optimise Test Data
    • Import and Export Test Data Sets
  • Introduction to Object Repository
    • Capture Objects for your Tests
    • Organise your Test Objects
    • Parameterise your Test Object Properties
  • Introduction to Parameters
    • Various Types of Parameters
    • Create and Utilise Parameters in your Test Case
    • Understanding Runtime Parameters
  • Defect Management
  • Marketplace
    • Integration with Project Management Tools
      • Integrating SimplifyQA with Jira
        • Configure Web-hooks
        • SimplifyQA Setup for Integration
          • Setup your Account for Jira Integration
          • Configuration in SimplifyQA Admin
          • Steps to Generate a Jira API Token
          • Steps to create SimplifyQA token
          • Steps to get Jira Account ID
          • Synchronisation Functionality Between SimplifyQA and Jira
          • Analyse Logs for Data Synchronisation
        • Mapping Fields for Issue Types
        • Viewing SimplifyQA Test Cases in Jira
  • Legal Documents
    • End-User License Agreement
Powered by GitBook
On this page
  1. Introduction to Script-less Recording of Test Case

Understand Object Recognition Mechanism & Self Healing in SimplifyQA

Self-healing of objects refers to the ability to automatically recover from errors or unexpected conditions related to object identification or interaction. This feature enhances the robustness and reliability of automation scripts, especially in dynamic environments where objects may change frequently.

In this section you'll learn about various challenges faced in automation and how SimplifyQA works with self-healing of objects.

Common Challenges in Object Identification

  • Dynamic Object Attributes: Elements on a web page may have dynamic attributes that change over time, making it difficult for automation scripts to identify them reliably.

  • Object Overlays: Objects may be partially or completely obscured by other elements on the page, interfering with their identification.

  • Page Loading Delays: Automation scripts may encounter delays in page loading, leading to synchronization issues and object identification failures.

Object Recognition & Self-Healing Techniques

  1. Object Attribute Flexibility:

    • Multiple Attributes: Multiple attributes (e.g., ID, class, XPath) would be captured to identify objects, increasing the likelihood of successful identification.

  2. Object Synchronisation:

    • Test scripts waits to ensure that elements are present or visible before attempting to interact with them.

  3. Object Recovery:

    • Alternative Paths: After trying all above techniques, if it failed to recognise the object, then it updates the properties to up-to-date object available on screen.

Benefits of Self-Healing Objects

  • Increased Reliability: Self-healing objects help prevent automation scripts from failing due to unexpected changes in the application under test.

  • Reduced Maintenance: By automatically handling object identification challenges, self-healing can reduce the time and effort required to maintain automation scripts.

  • Improved Efficiency: Self-healing can help automation scripts run more smoothly, reducing the likelihood of manual intervention and improving overall efficiency.

  • Enhanced Robustness: Self-healing objects make automation scripts more resilient to changes in the application's user interface.

PreviousRecord Functions in SimplifyQANextTest Data Management

Last updated 7 months ago