agentleFS
Sign inStart free
jovd83jovd83/restassured-skill/virtualization/SKILL.md

restassured-virtualization

Skill3 starsChanged 35 days agoMITView on GitHub

Use when the agent 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.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep real dependencies for the system under test whenever practical.

    line 22
  2. Distinctive:

    Read when-to-mock-vs-real.md before adding stubs.

    line 23
  3. Distinctive:

    Use WireMock for HTTP downstream dependencies.

    line 27
  4. Distinctive:

    Add negative behavior only when the scenario requires it.

    line 29
  5. Distinctive:

    Read wiremock-patterns.md for stub structure.

    line 30
  6. Distinctive:

    Add latency, resets, malformed payloads, and error statuses deliberately.

    line 34
  7. Distinctive:

    Read fault-injection.md before writing resilience tests.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 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 for stub structure.

3. Inject Failure Modes

  1. Add latency, resets, malformed payloads, and error statuses deliberately.
  2. Read 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.
  2. 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.
  2. Problem: Contract drift breaks the stub. Fix: Rebuild the stub from the latest contract or response samples.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free