skills.rest
sapdev-ai
sapdev-aiOFFICIAL
Explore all skills by this author →
GitHub

sap-gui-screen-check

Replay golden-screen baselines against live SAP GUI sessions to detect drift.

7|1|Updated May 11, 2026
Search Tags:#automation#regression#drift#baseline#sap#sap-gui#screen-check
One-click install
npx skills add https://github.com/sapdev-ai/sap-dev --skill sap-gui-screen-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sap-gui-screen-check
Source: https://github.com/sapdev-ai/sap-dev/tree/main/plugins/sap-dev-core/skills/sap-gui-screen-check
Command: npx skills add https://github.com/sapdev-ai/sap-dev --skill sap-gui-screen-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Live SAP GUI sessions often diverge from stored golden-screen baselines, causing false positives or missed regressions. This skill replays the baseline checks against the current system to surface drift in screen identity and control IDs before release.

Core Features & Use Cases

  • Replays golden-screen baselines against a live SAP GUI session to detect drift in program and dynpro identity and control IDs.
  • Coordinates with a read-only probe and an orchestrator to enumerate baselines, validate checkpoints, and report DRIFT or CAPTURE opportunities.
  • Use Case: QA teams validate a SAP GUI release by ensuring critical screens match their baselines across multiple transaction paths.

Quick Start

Run sap-gui-screen-check in an idle SAP session to compare the live screen against its golden baselines and report any drift.

Frequently Asked Questions about sap-gui-screen-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect SAP GUI screen drift before release?▼

Detect SAP GUI screen drift by replaying golden-screen baselines against a live SAP GUI session. The skill compares program, dynpro identities, and control IDs across multiple checkpoints to report regressions during pre-release validation.

What is a golden-screen baseline for SAP GUI regression testing?▼

A golden-screen baseline is a stored .screens.json file containing expected program, dynpro, and control IDs for SAP GUI screens. It serves as the reference to detect drift when replayed against a live session.

Do I need a live SAP GUI session to run screen checks?▼

Yes, a live SAP GUI session is required to run screen checks. The orchestrator and read-only probe scripts validate live checkpoints against stored baselines to identify any divergence.

How do I capture updated baselines after detecting SAP GUI drift?▼

After detecting drift, you can capture updated baselines using the provided screening scripts. The system reports CAPTURE opportunities alongside DRIFT findings, allowing you to update the .screens.json references.

What scripts are needed to automate SAP GUI control ID validation?▼

You need the sap_screen_check.ps1 orchestrator and sap_screen_check_probe.vbs read-only probe to automate SAP GUI control ID validation. These scripts enumerate baselines, compare live screens, and report drift.

Can I validate multiple transaction paths in SAP GUI for regressions?▼

Yes, you can validate multiple transaction paths by defining multiple checkpoints in your baselines. The orchestrator replays these paths against the live SAP GUI session to verify critical screens match expected identities.

Related Skills

Explore More Software Engineering Skills→
sapdev-aisapdev-ai
7

sap-se51

Automate SAP SE51 screen flow logic and layout element deployment via GUI scripting.

Official
Advanced
sapdev-aisapdev-ai
7

sap-gui-object-details

Inspect active SAP GUI screens and extract component IDs and properties.

Official
Advanced
sapdev-aisapdev-ai
7

sap-gui-skill-scaffold

Compile SAP GUI scenario probes into a mode-dispatched SKILL.md with VBS templates.

Official
Advanced
sapdev-aisapdev-ai
7

sap-gui-probe

Record SAP GUI screen states and generate deterministic VBS replay scripts.

Official
Advanced