Search

Troubleshooting Self-Heal Failures with 'Not Approved for Learning'

Overview

This article addresses scenarios where a test step fails to self-heal. This can occur when a test is copied from a source that has learning disabled ('Not Approved for Learning').

How It Works

Self-healing relies on approved learning data to adapt to UI changes. If learning is disabled or the context is ambiguous due to environmental differences, self-healing may not engage correctly.

Test Copied from a 'Not Approved for Learning' Source

If a test case is copied from a source where the 'Not Approved for Learning' setting is enabled, the new test will inherit this restriction. This prevents the self-healing mechanism from functioning because it cannot access or update learning data.

To resolve this, follow these steps:

  1. In the test settings of the copied test case, temporarily enable the Not Approved for Learning setting.
  2. Manually update the affected test steps using a tool like Quick Select to re-capture the correct elements in the updated UI.
  3. Re-execute the test to verify that it passes with the new element selections.
  4. Once the test passes, approve the learning for the test case. This allows it to build new learning data and enables self-healing for future runs.

Limitations

The 'Not Approved for Learning' setting is a direct blocker to the self-healing feature. If this setting is active, self-healing will not work. While the Self-Heal slider is effective for minor UI differences, significant changes to the application's layout or element structure will likely still require manual updates and re-learning.