본문으로 건너뛰기
cccskills
무료GitHub에 공개

payment-gateway-sandboxes

Wraps the vendor-generic payment-gateway sandbox pattern - test credentials, sandbox base URLs / environment switches, deterministic test-card matrices, and gateway-native webhook simulators - with per-gateway references for Adyen test mode, PayPal Sandbox, and Braintree sandbox. Use when testing code integrated with Adyen, PayPal, or Braintree; for Stripe use stripe-test-cards-and-webhooks (one-time payments) or stripe-subscription-billing-test-author (recurring billing).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

testland/qa스타 13(GitHub 13 + cccskills 0)
연동 도구Stripe

실행 점수 미검증

설치 방법 보기

포함된 파일(5)

  • SKILL.md5.3 KB
  • .tessl-plugin/plugin.json618 B
  • references/adyen.md6.1 KB
  • references/braintree.md5.9 KB
  • references/paypal.md5.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

payment-gateway-sandboxes

Overview

Every major payment gateway ships the same four sandbox primitives, each under a different name:

  1. Test credentials - a sandbox API key / merchant account that can never move real money.
  2. An environment switch - a sandbox base URL or an SDK environment flag that routes calls to the test stack.
  3. A deterministic test-card matrix - specific PANs (or amounts) that trigger specific outcomes: success, decline, 3DS challenge.
  4. A webhook simulator / resend surface - a way to fire or replay asynchronous events at your handler on demand.

This skill is the single entry point for the non-Stripe gateways. The body covers the shared pattern; the per-gateway mechanics live in references/.

Routing table

GatewayReferenceDistinctive sandbox trait
Adyenreferences/adyen.mdExplicit sync-API / async-notification duality; HMAC-validated notifications
PayPalreferences/paypal.mdSandbox Business + Personal accounts; dashboard + API webhook simulator
Braintreereferences/braintree.mdAmount-based magic values; sandbox-only gateway.testing.settle
Stripestripe-test-cards-and-webhooksStripe CLI (stripe listen / stripe trigger); test clocks in stripe-subscription-billing-test-author

When to use

  • Authoring tests for code integrated with Adyen, PayPal, or Braintree.
  • Wiring a gateway sandbox into CI (credentials, env switch, webhook secrets).
  • Porting an existing single-gateway suite to a second gateway.

The shared sandbox test pattern

Regardless of gateway, a payment integration suite has the same skeleton:

  1. Initialize the SDK against the sandbox environment - never a prod key; the environment switch is an env var, not a hardcode.
  2. Drive each documented test-card outcome - one test per outcome row (success, decline variants, 3DS frictionless, 3DS challenge), asserting the gateway's own result-code vocabulary.
  3. Verify webhook signatures - every gateway signs its events (HMAC-SHA256 for Adyen, SHA256-with-RSA for PayPal, bt_signature parsing for Braintree); the suite must reject unsigned and wrong-secret payloads.
  4. Prove handler idempotency under redelivery - all three gateways redeliver unacknowledged events; process-exactly-once is the contract. The full replay workflow is payment-flow-test-author.
  5. Map the state machine - each gateway names the same lifecycle differently; translate via payment-flow-states-reference before asserting on states.

CI integration

Sandbox credentials are secrets like any other:

jobs:
  gateway-tests:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - uses: actions/setup-node@v4
      - run: npm ci && npm test
        env:
          ADYEN_TEST_API_KEY: ${{ secrets.ADYEN_TEST_API_KEY }}
          PAYPAL_SANDBOX_CLIENT_ID: ${{ secrets.PAYPAL_SANDBOX_CLIENT_ID }}
          BT_SANDBOX_MERCHANT_ID: ${{ secrets.BT_SANDBOX_MERCHANT_ID }}

Per-gateway variable lists are in each reference.

Anti-patterns

Anti-patternWhy it failsFix
Prod credentials in testsReal settlement / real chargesSandbox-only keys, per-env config
Skip webhook signature validationSpoofed events trigger fulfillmentVerify per the gateway's scheme
Treat the sync API return as finalAll three gateways finalize asyncWebhook-driven state, per payment-flow-states-reference
One happy-path testDecline / 3DS / fraud paths untestedOne test per documented outcome row
Hardcoded merchant/account IDsPer-env accounts driftEnv vars
One suite for all gatewaysResult-code vocabularies differPer-gateway test directory

Limitations

  • Sandbox fidelity varies. Braintree settles synchronously via a test-only API; prod settles overnight. PayPal sandbox webhooks can lag.
  • Client-side surfaces need a browser. Drop-in / Hosted Fields / PayPal-button flows require Playwright against the sandbox UI.
  • Region-specific payment methods (iDEAL, Sofort, etc.) have separate test flows not covered here.

References

  • Adyen test mode, test cards, result codes, HMAC notifications: references/adyen.md.
  • PayPal Sandbox accounts, Orders v2, webhook simulator: references/paypal.md.
  • Braintree sandbox, amount-based magic values, webhook parser: references/braintree.md.
  • Companion catalog: payment-flow-states-reference (state machines + 3DS flows).
  • Flow suites on top of the sandboxes: payment-flow-test-author.
  • Stripe: stripe-test-cards-and-webhooks, stripe-subscription-billing-test-author.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

a11y-violation-gate

무료

Builds a CI gate that fails the build on **new** WCAG / a11y violations introduced by a PR while grandfathering pre-existing violations on a per-rule / per-page baseline. Aggregates verdicts from axe-core / pa11y / Lighthouse a11y / WAVE / IBM Equal Access scans. Use when a project has accumulated a11y debt and a strict "zero violations" gate would block every PR - the ratchet pattern lets the team ship while preventing regressions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

testland/qa132026년 10월 20일 업데이트

ab-test-validity-checklist

무료

Workflow skill that builds an A/B-test validity checklist from an experiment proposal, walking the canonical design-correctness gates - pre-registered OEC/power/guardrails, randomization unit + SRM check, assignment integrity, telemetry, peeking discipline, novelty/primacy, post-experiment SRM re-check - into a per-experiment checklist + sign-off form. Use when launching, auditing, or governing an experiment. For pitfall mechanics (guardrails, peeking) see experiment-results-interpreter's references; to read an already-valid result use experiment-results-interpreter; for per-SDK harness tests use experiment-sdk-testing - this gates DESIGN, not SDK code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

testland/qa132026년 10월 20일 업데이트

add-to-homescreen-flow-tests

무료

The single install-flow skill: the reference contract for the PWA install flow (installability gate fields, `beforeinstallprompt` handshake, per-platform paths - Android WebAPK / iOS Share menu / Firefox no-op - and the `display-mode` post-install signal, in references/install-flow-reference.md) plus the build-an-X workflow that emits the Add-to-Home-Screen suite. Walks the four-stage timeline, emitting one test per gate cell per [web.dev/articles/install-criteria][install-criteria], the deferred-prompt → `prompt()` → `userChoice` chain per [web.dev/articles/customize-install][customize-install], the iOS Safari manual-metadata branch (`apple-touch-icon`) per [web.dev/learn/pwa/installation][learn-pwa], and the post-install `(display-mode: standalone)` MQ assertion. Output: a Playwright spec with per-stage cells plus a coverage matrix. Use when a PWA's manifest, icons, or install handler change, when install conversion drops at an unknown stage, or when triaging a flaky install assertion.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

testland/qa132026년 10월 20일 업데이트

ai-spec-coverage-mapper

무료

Build-an-X workflow that uses an LLM to map existing tests to spec sections - given a spec doc + the test suite, the LLM identifies which tests cover which sections, surfaces uncovered sections (gap), and recommends specific tests to add. Output is a coverage matrix per spec ID. Scope is mapping tests that already exist and naming the gaps, not authoring tests for new acceptance criteria. Use when a spec doc and a test suite both exist but nobody can say which requirements are actually covered - before a release sign-off, an audit, or a decision about where to spend the next round of test effort.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

testland/qa132026년 10월 20일 업데이트

ai-test-generator

무료

Generates tests from natural-language specs (acceptance criteria, user stories, requirements) using an LLM, with confidence scoring per test case (LLM self-assessment plus heuristics: assertion quality, naming, completeness), batching uncertain cases for human review, and integration with the team's existing test framework. Use when the user asks to generate unit tests from acceptance criteria, convert user stories to test cases, automate test creation from requirements, or augment a spec-driven test suite with AI-generated stubs that are then curated before merge.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

testland/qa132026년 10월 20일 업데이트

allure-reports

무료

Configures Allure Report (test-runner adapter install, `allure-results` directory wiring, `categories.json` for failure classification, `history-trend.json` retention via the copy-history-between-runs pattern), runs the Allure CLI to convert `allure-results` to a static HTML site, and uploads the report as a CI artifact. Use when the team needs richer test reporting than JUnit XML - step-level attachments, per-test history, retry tracking, and severity / epic / feature labeling across framework-agnostic adapters (pytest, Jest, JUnit, TestNG, NUnit, Mocha). As a rich static HTML report generator, it is the open-source alternative to the sunset ExtentReports (JVM/.NET per-test HTML narrative); for hosted cross-run flakiness analytics rather than a static per-run report use currents-integration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

testland/qa132026년 10월 20일 업데이트

testland의 스킬 모두 보기

이 스킬의 문제 신고