Capture and Validate Tooltips in Scenario Editor

Problem

Last reviewed: September 29, 2026

IUse cannotthis capturearticle thewhen toola tipScenario textEditor whiletest creatingneeds anto Asserttrigger, orcapture, Validationand validate tooltip text.

ReasonWhat changed in this article

Tool tips are difficult to capture using the traditional

• Replaced Test Designer IDE Checkpoint recording method

  Resolution

  Standard tool tips alwayswording with similarScenario characteristicsEditor terminology.

• Added guidance to thedistinguish following:native title tooltips, ARIA/toolkit tooltips, and custom DOM tooltip components.
• Added timing and hover/focus validation checks so flaky tooltip assertions are easier to diagnose.

Validation workflow

1. Identify

1. Reside within a DIV

Contain the class cdk-overlay-container

By replacing the Click action (on the element wherewhether the tooltip resides)appears withon ahover, Mousefocus, Overor action,click and whether it is native or custom HTML.

Capture the tooltip displays. Then asserttext or verifyattribute after the div(“cdk-overlay-container”)UI containshas displayed it.Replay the anticipatedstep with timing checks and confirm the assertion fails when expected text as illustrated below:
changes.

Review note: Modernized the tooltip workflow and added custom component handling for current web apps.