AgentStack
SKILL verified MIT Self-run

Restassured Virtualization

skill-jovd83-restassured-skill-virtualization · by jovd83

Use when Codex needs to simulate downstream HTTP services for Rest Assured suites with WireMock, stub mappings, latency, retries, fault injection, or isolation from unstable third-party dependencies.

No reviews yet
0 installs
3 views
0.0% view→install

Install

$ agentstack add skill-jovd83-restassured-skill-virtualization

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Restassured Virtualization? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Service Virtualization

1. Decide Whether To Mock

  1. Mock only third-party or unstable dependencies.
  2. Keep real dependencies for the system under test whenever practical.
  3. Read [when-to-mock-vs-real.md](references/when-to-mock-vs-real.md) before adding stubs.

2. Create The Stub Layer

  1. Use WireMock for HTTP downstream dependencies.
  2. Model stable happy-path stubs first.
  3. Add negative behavior only when the scenario requires it.
  4. Read [wiremock-patterns.md](references/wiremock-patterns.md) for stub structure.

3. Inject Failure Modes

  1. Add latency, resets, malformed payloads, and error statuses deliberately.
  2. Read [fault-injection.md](references/fault-injection.md) before writing resilience tests.

4. Verify Intent

  1. Assert that the system under test handled the dependency behavior correctly.
  2. Assert that the stub was called only when interaction verification matters.

5. Examples

  1. Input: Simulate the shipping provider timing out.

Output: Add a WireMock delayed response and assert the API returns the documented fallback error.

  1. Input: Stub the tax provider for local CI.

Output: Add deterministic success and validation-failure stubs, then route the tests to the stub base URL.

6. Troubleshooting

  1. Problem: The suite still calls the live dependency.

Fix: Verify the service under test points to the stubbed base URL.

  1. Problem: Contract drift breaks the stub.

Fix: Rebuild the stub from the latest contract or response samples.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.