add-e2e-emulator

Étoiles14

Forks0

Mis à jour11 juillet 2026 à 23:12

Use when adding emulator-backed e2e coverage for a provider — wiring an env-gated emulator seam, a compose.test.yaml service, a mise e2e-<provider> task, and a closed-network CI job. Covers emulator-vs-SDK divergences and coverage upload.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

mpyw

mpyw/suve

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	add-e2e-emulator
description	Use when adding emulator-backed e2e coverage for a provider — wiring an env-gated emulator seam, a compose.test.yaml service, a mise e2e-<provider> task, and a closed-network CI job. Covers emulator-vs-SDK divergences and coverage upload.

Adding emulator-backed e2e

suve runs provider e2e against local emulators: Google Cloud (PR #256), Azure App Configuration (PR #258), and Azure Key Vault (PR #259).

Emulator seam

Add an env-gated seam in the adapter that swaps credentials/TLS into emulator mode when set — e.g. SUVE_AZURE_APPCONFIG_CONNECTION_STRING, SUVE_AZURE_KEYVAULT_ENDPOINT. Document in the code that the variable is for emulator use and must never be pointed at production.

Compose + task + CI

Add a compose.test.yaml service under the provider's compose profile.
Add a mise e2e-<provider> task (AWS is mise e2e-aws; Google Cloud is mise e2e-gcloud; Azure is mise e2e-azure-appconfig / mise e2e-azure-keyvault).
Add a CI job that runs on a closed compose network with no host ports (#468) — the suite runs in-container and tears everything down on exit.
e2e CI jobs must upload coverage.

Vet the emulator against the real SDK

Upstream emulators break real SDKs — vet with the official SDK, not curl:

App Configuration (#258) documents three divergences that the fork ghcr.io/mpyw/azure-app-configuration-emulator fixes: HMAC auth-header parsing, RFC3339 timestamp offset handling, and a missing Sync-Token response header.
Key Vault (#259): lowkey-vault has 1-second-granular timestamps, so space successive writes by 1 second to keep version ordering deterministic; it returns 405 on an empty-version PATCH, so cover tag/untag in unit tests rather than through the emulator.

Document each quirk next to the code that routes around it.

Assertions

Assertions must assert real behavior, not merely "no panic". Weak error-case subtests (#443) were hardened to assert actual outcomes in #517.

Local runs

Keychain-dependent e2e blocks on OS keychain prompts when run locally. Bypass with SUVE_STAGING_KEY, or leave those paths to CI.

Plus depuis ce dépôt

même dépôt

docs-site-pages

mpyw/suve

Use when restructuring the README or the GitHub Pages site generated from it — the left-nav/left-pane, section reorg, or per-provider command docs. Covers the build-docs-site.py split + literate-nav SUMMARY pipeline, its HTML-comment directives and site-only transforms (nav-group, site:skip, hero <h1>, asset ../ prefix, DOC_NAV grouping), the python-markdown gotchas GitHub hides, and the `mise docs-build` strict gate.

2026-07-1614

release-highlights

mpyw/suve

Use when authoring or backfilling the "## Highlights" section of a GitHub release — the human-written summary that prepends the auto-generated notes. Covers when a release earns highlights, the fixed format (bold lead + breaking-change note, `###` subsections, PR-referenced bullets), and the prepend-in-place mechanics.

2026-07-1514

refresh-demo-gifs

mpyw/suve

Use when re-recording the CLI, TUI, or GUI demo GIFs after a UI change or a user-visible output change. Covers the record scripts, robust Playwright selectors, output-drift triggers, frame verification, and Git LFS.

2026-07-1314

collection-idioms

mpyw/suve

Load when writing or reviewing Go that builds or transforms slices/maps. Prefer samber/lo, samber/lo/it, and stdlib slices/maps callback & iterator utilities over hand-rolled make + range + append; keep an explicit loop only where side effects or control flow are genuinely complex.

2026-07-1214

suve-cli-map

mpyw/suve

Load when you need the per-provider capability, versioning, and alias matrix for suve's CLI without reading the full docs/{aws,azure,gcloud}.md option tables. A one-page orientation; link out for per-command detail.

2026-07-1214

provider-seam-invariants

mpyw/suve

Load when adding or modifying a provider adapter, or when touching internal/provider/** or internal/domain/**. Captures the invariants that keep the provider-neutral seam honest: the neutral domain model, opaque version refs, the typed write/delete option pattern, interface segregation, and SDK confinement.

2026-07-1214

Adding emulator-backed e2e

suve runs provider e2e against local emulators: Google Cloud (PR #256), Azure App Configuration (PR #258), and Azure Key Vault (PR #259).

Emulator seam

Add an env-gated seam in the adapter that swaps credentials/TLS into emulator mode when set — e.g. SUVE_AZURE_APPCONFIG_CONNECTION_STRING, SUVE_AZURE_KEYVAULT_ENDPOINT. Document in the code that the variable is for emulator use and must never be pointed at production.

Compose + task + CI

Add a compose.test.yaml service under the provider's compose profile.

Add a mise e2e-<provider> task (AWS is mise e2e-aws; Google Cloud is mise e2e-gcloud; Azure is mise e2e-azure-appconfig / mise e2e-azure-keyvault).

Add a CI job that runs on a closed compose network with no host ports (#468) — the suite runs in-container and tears everything down on exit.

e2e CI jobs must upload coverage.

Vet the emulator against the real SDK

Upstream emulators break real SDKs — vet with the official SDK, not curl:

App Configuration (#258) documents three divergences that the fork ghcr.io/mpyw/azure-app-configuration-emulator fixes: HMAC auth-header parsing, RFC3339 timestamp offset handling, and a missing Sync-Token response header.

Key Vault (#259): lowkey-vault has 1-second-granular timestamps, so space successive writes by 1 second to keep version ordering deterministic; it returns 405 on an empty-version PATCH, so cover tag/untag in unit tests rather than through the emulator.

Document each quirk next to the code that routes around it.

Assertions

Assertions must assert real behavior, not merely "no panic". Weak error-case subtests (#443) were hardened to assert actual outcomes in #517.

Local runs

Keychain-dependent e2e blocks on OS keychain prompts when run locally. Bypass with SUVE_STAGING_KEY, or leave those paths to CI.