sumup-testing
Skill from sumup/sumup-skills
Install
npx skills add sumup/sumup-skills --skill sumup-testing
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-official
/plugin install sumup@sumup
This skill is part of the plugin “sumup”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the sumup-testing skill do?
Description from the SKILL.md in the source repository.
Questions about sumup-testing
What does the sumup-testing skill do?
Set up SumUp sandbox merchants, choose online test cards or terminal simulation amounts, test saved-card tokenization, and design or run payment-flow regression checks. Use for requested test setup, scenarios, or verification.
How do I install sumup-testing?
In a terminal: npx skills add sumup/sumup-skills --skill sumup-testing. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use sumup-testing?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is sumup-testing safe to use?
Our automatic check found no risky patterns (piped shell scripts, hidden characters, secret access, prompt overrides). It is not a full audit – read the SKILL.md and any scripts before installing.
More skills from sumup/sumup-skills
Choose a SumUp integration and credential model, or review its payment security. Use for Hosted Checkout vs Card Widget, reader SDK vs Cloud API, API key vs OAuth, and public vs secret key decisions.
Diagnose and fix failing SumUp payment integrations, including checkout errors, callback verification, widget mounting, merchant or currency mismatches, missing scopes, affiliate setup, and uncertain or duplicate payments. MCP connection setup belongs to sumup-mcp.
Configure, authenticate, troubleshoot, or use the SumUp MCP server at mcp.sumup.com. Use for MCP client setup, missing tools, OAuth connection failures, merchant account queries, and SumUp documentation resources.
Implement or modify SumUp payment integrations using Hosted Checkout, Card Widget, Checkouts API, saved cards, React Native Checkout, terminal SDKs, Tap to Pay, or Cloud API. Use for integration code and payment-flow reviews.
Upgrade SumUp server or mobile SDKs, migrate deprecated endpoints, and assess release compatibility. Use for dependency bumps or migrations involving @sumup/sdk, Go, Python, PHP, Java, Rust, .NET, reader SDKs, Tap to Pay, React Native, or Swift Checkout.
Related skills in Testing & QA
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Automate browser interactions, test web pages and work with Playwright tests.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.