agentsclimarketplace
Sign in

Sumup testing

Skill sumup/sumup-skills/skills/sumup-testing

Set up and run SumUp sandbox tests. Use when configuring a SumUp test merchant, picking test cards, triggering deliberate failure (`amount = 11`), or building a SumUp end-to-end test harness.From its SKILL.md

Install
npx -y skills add sumup/sumup-skills --skill sumup-testing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

4 things to look at

  • reads credentialsReads from 1 credential source: `SUMUP_API_KEY`.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 1 command, including `curl -X POST "https://api.sumup.com/v0.1/checkouts" \ -H "Authorization: Bearer $SUMUP_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "checkout_reference": "order-12345", "amount`.
  • fetches URLsInstructs the agent to fetch 1 URL, including https://api.sumup.com/v0.1/checkouts.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.9 KB, 646 tokens by cl100k_base, as published. Nobody here has run it

SumUp Sandbox Testing Guide

Use this skill for test setup, scenario design, and verification of SumUp integrations.

Test Environment Setup

  1. Use a sandbox merchant account only.
  2. Confirm credentials map to sandbox environment.
  3. Prepare webhook endpoint in a non-production environment.
  4. Enable logging for checkout id, reference, status, and error code.

Core Card Test Data

Default values unless docs specify otherwise:

  • CVV: any 3 digits (for example 123)
  • Expiry: any future date (for example 12/30)
  • Cardholder: any name

Happy path cards:

  • VISA 4200 0000 0000 0091
  • Mastercard 5200 0000 0000 0007

3DS challenge cards:

  • VISA 4200 0000 0000 0042
  • Mastercard 5200 0000 0000 0015

Deliberate Failure Conventions

  • For skill-level test recipes, use amount = 11 as the default forced-failure trigger.
  • If an integration already uses canonical amount-based failures (for example 42.01, 42.76, 42.91), run both patterns and document which one is authoritative for that flow.

End-to-End Smoke Test Recipe

  1. Create checkout with unique checkout_reference.
  2. Complete payment with a happy-path card.
  3. Verify frontend callback/result handling.
  4. Verify backend retrieves final paid status before fulfillment.
  5. Verify webhook delivery and idempotent processing.
  6. Repeat with forced-failure amount and confirm order remains unpaid.

cURL Skeleton

curl -X POST "https://api.sumup.com/v0.1/checkouts" \
  -H "Authorization: Bearer $SUMUP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "checkout_reference": "order-12345",
    "amount": 11,
    "currency": "EUR",
    "pay_to_email": "[email protected]",
    "description": "Sandbox test payment"
  }'

Adjust payload fields to the selected flow and auth model.

SDK Smoke Test Guidance

  • Keep one smoke test per integration surface (server SDK, mobile SDK, widget).
  • Assert normalized outcomes: success, pending, failed.
  • Capture and store reconciliation keys: checkout id, transaction id/code, merchant code, reference.

Required QA Matrix

  • Happy path payment succeeds.
  • Forced-failure payment does not fulfill order.
  • 3DS challenge flow completes and returns expected status.
  • Duplicate reference behavior is deterministic.
  • Expired checkout/session path is handled with a fresh checkout.
  • Webhook retries do not create duplicate side effects.

Required Response Contract

When asked for test planning, always provide:

  1. Test environment assumptions.
  2. Exact scenarios to run (success + failure + async).
  3. Assertions for frontend and backend.
  4. Evidence to collect for reconciliation/debugging.

What ships with it: 3 files

4.2 KB alongside SKILL.md

agents/

assets/

Gives 0 of the 12 instructions most test skills give in 646 tokens

Counted across 1,201 of the 2,096 authors here whose files we hold, read 2026-09-06

  • Write a failing test before writing codein 43 of 1201, across 36 files
  • Run the full test suitein 36 of 1201, across 35 files
  • Test only one variable per experimentin 34 of 1201, across 17 files
  • Read product marketing context before asking questionsin 34 of 1201, across 14 files
  • Mock external dependenciesin 34 of 1201, across 30 files
  • Define primary, secondary, and guardrail metricsin 33 of 1201, across 16 files
  • Pre-determine sample size before startingin 31 of 1201, across 14 files
  • Test behavior rather than implementationin 31 of 1201, across 29 files
  • Formulate a hypothesis before designing a testin 30 of 1201, across 13 files
  • Document every test hypothesis, variant, and resultin 29 of 1201, across 11 files
  • Use descriptive test function namesin 25 of 1201, across 21 files
  • Commit to the methodology without stopping earlyin 24 of 1201, across 8 files

Said here and by no other author read

  • Use sandbox merchant accounts only
  • Confirm credentials map to sandbox environment
  • Prepare webhook endpoints in non-production environments
  • Enable logging for checkout status and errors
  • Use amount 11 to trigger deliberate failures
  • Create checkouts with unique references

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.