sap-fiori-testing

sap-fiori-testing is a skill for Claude Code, Codex from efeumutaslan/SAP-SKILLS. It costs 93 tokens per session (4,274 once invoked), scanned A, original, MIT.

A guide to testing SAP Fiori and UI5 web applications, including accessibility checks and migration to TypeScript, a typed form of JavaScript.

In plain words
What is it for?
Use it to create QUnit, OPA5, wdi5, and UIVeri5 tests, check WCAG 2.1 accessibility, test navigation and visual behavior, or move UI5 code to TypeScript.
Why use it?
It helps verify both individual code pieces and complete browser-based user flows, while checking that interfaces are usable by people with disabilities.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create QUnit, OPA5, wdi5, and UIVeri5 tests, check WCAG 2.1 accessibility, test navigation and visual behavior, or move UI5 code to TypeScript.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/efeumutaslan/sap-skills/sap-fiori-testing
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add efeumutaslan/SAP-SKILLS --skill sap-fiori-testing
Clone the repo
git clone --depth 1 https://github.com/efeumutaslan/SAP-SKILLS

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sap-fiori-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/efeumutaslan/sap-skills/sap-fiori-testing/github.svg)](https://agentmods.dev/skills/efeumutaslan/sap-skills/sap-fiori-testing)
Your own site
<a href="https://agentmods.dev/skills/efeumutaslan/sap-skills/sap-fiori-testing"><img src="https://agentmods.dev/badge/skills/efeumutaslan/sap-skills/sap-fiori-testing/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sap-fiori-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/efeumutaslan/sap-skills/sap-fiori-testing"><img src="https://agentmods.dev/badge/skills/efeumutaslan/sap-skills/sap-fiori-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,274 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00093 $0.04274
Opus 5 $0.00046 $0.02137
Sonnet 5 $0.00019 $0.00855
Haiku 4.5 $0.00009 $0.00427

Measured 12d ago against content hash 4d1dba8a0f15, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

sap-fiori-testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (templates/wdi5-test-template.ts), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/sap-fiori-testing/SKILL.md · 538 lines

How it starts

The opening of the file, as written. The whole thing — 538 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SAP Fiori Testing, Accessibility & Modern UI

  • sap-testing-quality — Cross-cutting SAP testing strategy
  • sap-devops-cicd — UI test automation in pipelines
  • sap-build-apps — Alternative low-code UI approach

Quick Start

Choose your test framework:

Framework Level Speed Best For
QUnit Unit Fast Controller logic, formatters
OPA5 Integration Medium UI interaction flows, navigation
wdi5 E2E Slow Full app testing, cross-app
UIVeri5 Visual/E2E Slow Visual regression, screenshots

Quick wdi5 setup:

npm init wdi5@latest
# Follow prompts: select UI5 app, choose test runner
# Generates: wdio.conf.js + test structure

Core Concepts

UI5 Test Pyramid

         /\
        /  \     E2E (wdi5/UIVeri5)
       /    \    - Full app in browser
      /------\   - Real backend or mock server
     /        \
    / OPA5     \ Integration
   /   Tests    \ - UI interaction + navigation
  /--------------\ - Mock server for data
 /                \
/ QUnit Unit Tests \ Unit
/                    \ - Pure logic, no DOM
/____________________\

wdi5 Architecture

Test Script ──► wdi5 Bridge ──► UI5 Control API
    │               │               │
 WebdriverIO    Injects JS      sap.ui.test.*
 (Selenium/     into browser    control selectors
  Playwright)

OPA5 Key Concepts

Concept Role Example
Page Object Encapsulates page interactions onTheMainPage.iClickCreate()
Journey Test scenario (sequence of actions) opaTest("Create order", ...)
Arrangement Setup state Given.iStartMyApp()
Action User interaction When.onTheList.iSelectItem("001")
Assertion Verify outcome Then.onTheDetail.iSeeTitle("Order 001")

Common Patterns

Pattern 1: wdi5 Test with UI5 Selectors

// test/e2e/specs/order.test.js
const { wdi5 } = require('wdio-ui5-service');

describe('Order Management', () => {
  before(async () => {
    await browser.url('#/Orders');
    await browser.asControl({
      selector: { controlType: 'sap.m.Page', viewName: 'orders.List' }
    });
  });

  it('should display order list', async () => {
    const table = await browser.asControl({
      selector: {
        controlType: 'sap.m.Table',
        viewName: 'orders.List',
        id: 'orderTable'
      }
    });
    const items = await table.getItems();
    expect(items.length).toBeGreaterThan(0);
  });

  it('should create new order', async () => {
    // Click Create button
    const createBtn = await browser.asControl({
      selector: {
        controlType: 'sap.m.Button',
        viewName: 'orders.List',
        properties: { text: 'Create' }
      }
    });
    await createBtn.press();

    // Fill form
    const customerInput = await browser.asControl({
      selector: {
        controlType: 'sap.m.Input',
        viewName: 'orders.Create',
        id: 'customerInput'
      }
    });
    await customerInput.setValue('CUST001');

    const amountInput = await browser.asControl({
      selector: {
        controlType: 'sap.m.Input',
        viewName: 'orders.Create',
        id: 'amountInput'
      }
    });
    await amountInput.setValue('1500.00');

    // Save
    const saveBtn = await browser.asControl({
      selector: {
        controlType: 'sap.m.Button',
        viewName: 'orders.Create',
        properties: { type: 'Emphasized' }
      }
    });
    await saveBtn.press();

    // Verify success message
    const msgStrip = await browser.asControl({
      selector: {
        controlType: 'sap.m.MessageStrip',
        properties: { type: 'Success' }
      }
    });
    const text = await msgStrip.getText();
    expect(text).toContain('created successfully');
  });
});

Read the full file on GitHub · 538 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 538 lines · 93 tokens per session scan A 4d1dba8a0f15

Subscribe to this mod's changes

sap-fiori-testing is a skill published in the GitHub repository efeumutaslan/SAP-SKILLS (5 stars, last pushed 5mo ago), licensed MIT. It adds 93 tokens to every session and 4,274 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

Playwright E2E Testing

Use this skill when you need high-confidence coverage of user flows (auth, uploads, payments, chat flows) and you want stable, debuggable Playwright tests.

AmariahAK/atlarix-skills · 6 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-optimizer

Optimize what selected Next.js client navigations include before the click under Partial Prefetching. Use after Cache Components and Partial Prefetching are adopted when the user wants selected URL-specific UI to be instant, wants reusable content to wait for navigation, or needs to choose between default, viewport…

vercel/next.js · 82 tokens

screen-reader-testing

Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.

wshobson/agents · 39 tokens

break

Renders a component you choose in every state and scenario on a temporary page and stress tests it.

jakubkrehel/skills · 22 tokens

live-preview

Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.

SethGammon/Citadel · 40 tokens