Skip to content
Skills Library
Programming · Testing

sandbox-testing

/sandbox-testing

Test integrations against provider sandboxes, recorded fixtures, and fakes, knowing what each misses. Use when building or changing an integration.

Repository
AI-SKILLS ↗
Licence
MIT
Last repository change
05.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Test integrations against provider sandboxes, recorded fixtures, and fakes, knowing what each misses. Use when building or changing an integration.

Original author description

Test integrations against provider sandboxes, recorded fixtures, and fakes, knowing what each misses. Use when building or changing an integration.

How it works

  1. Method
  2. Boundaries
Original SKILL.md headings · 37 lines, 227 words
SKILL.md preview
---
name: sandbox-testing
description: Test integrations against provider sandboxes, recorded fixtures, and fakes, knowing what each misses. Use when building or changing an integration.
---

# Sandbox testing

You cannot test against production, and every alternative diverges from
it somewhere. Knowing where each approach lies is what prevents an
integration that passes every test and fails on first contact.

## Method

1. **Use the provider's sandbox for the happy path.** It exercises real
   request and response shapes, which no fake reproduces faithfully.
2. **Know how the sandbox differs.** Sandboxes have different limits,
   simplified validation, and often stale API versions, which is exactly
   where surprises come from.
3. **Record real interactions as fixtures.** Captured responses replayed
   in tests are fast, deterministic, and reflect actual behaviour rather
   than documentation.
4. **Refresh fixtures periodically.** Recorded responses go stale as the
   provider changes, and stale fixtures give false confidence (see
   integration-migration).
5. **Test the failure cases explicitly.** Timeouts, rate limits,
   malformed responses, and authentication failure, which sandboxes
   rarely produce on demand (see integration-resilience).
6. **Keep a small suite against the real API.** Run on a schedule rather
   than per commit, since it is the only thing that detects provider
   drift.
7. **Never let test code reach production credentials.** Environment
   separation is what prevents a test suite charging real cards (see
   api-credential-rotation).

## Boundaries

Sandboxes model the provider's intent rather than their production
behaviour. Fixtures test your code against a snapshot and cannot detect
provider changes. Some providers offer no sandbox, forcing careful use
of real accounts.

Versions

The database has no other skills named sandbox-testing.

Database snapshot: 13.11.2026 · package version 6f7479c04ea2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100bc-testing
    Test BigCommerce integrations — API testing, Stencil theme testing, Cypress/Playwright E2E tests, webhook testing, and sandbox stores. Use when writing tests for BigCommerce apps, themes, or integrations.
  • 100testing-patterns
    Test pyramid, mocking, fixtures and test organization. Use when designing tests, choosing what to mock or reviewing test quality.
  • 100polar-testing
    Guide for testing Polar payment integrations using the sandbox environment. Use this skill when: (1) Setting up the Polar sandbox for development; (2) Testing checkout flows without real payments; (3) Using Stripe test cards with Polar; (4) Writing integration tests for payment…
  • 95qe-n8n-integration-testing-patterns
    API contract testing, authentication flows, rate limit handling, and error scenario coverage for n8n integrations with external services. Use when testing n8n node integrations.
  • 80e2e-fixtures
    liter-llm e2e fixture schema: per-category fixture files, call names, mock provider responses, env and skip, and assertion types. Use when adding or editing a liter-llm e2e fixture.
  • 100python-testing-patterns
    Guide pytest patterns and testing strategies when the user asks about Python testing, fixtures, mocking, or test organization

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.