Build Rust Test Mocks with Trait Patterns
Rust tests often become slow or fragile when they depend on databases, HTTP services, or real infrastructure. This skill helps Claude, Codex, and Claude Code design trait-based mocks, controlled failures, and fixture helpers.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "mock-strategy-guide" from https://skillstore.io/skills/emillindfors-mock-strategy-guide.md and its manifest at https://skillstore.io/api/skills/emillindfors-mock-strategy-guide/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "mock-strategy-guide". I need to test a service that reads users from a repository.
Expected outcome:
The skill would suggest a trait-backed mock repository, seeded test users, and assertions around successful and missing-user paths.
Using "mock-strategy-guide". I need to verify that registration sends a welcome email.
Expected outcome:
The skill would recommend a mock email service that records sent messages, then checks the recipient count and subject intent.
Using "mock-strategy-guide". My unit tests depend on a real database.
Expected outcome:
The skill would suggest extracting a repository trait and replacing the database with an in-memory implementation for unit tests.
All external command findings are false positives caused by Markdown code fences around Rust test examples, not shell or Ruby execution. The obfuscation heuristic is also a false positive; the file contains plain YAML front matter and Rust-oriented documentation. No prompt injection or malicious semantic intent was found.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/emillindfors-mock-strategy-guide/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/emillindfors-mock-strategy-guide?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/emillindfors-mock-strategy-guide?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/emillindfors-mock-strategy-guide/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/emillindfors-mock-strategy-guide.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>EmilLindfors. (2026). mock-strategy-guide security audit report (audit version 4) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/emillindfors-mock-strategy-guide/audits/4@techreport{emillindfors-emillindfors-mock-strategy-guide-2026,
author = {EmilLindfors},
title = {mock-strategy-guide security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/emillindfors-mock-strategy-guide/audits/4},
note = {Author version 1.0.0}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "mock-strategy-guide security audit report (audit version 4)"
version: "1.0.0"
type: report
authors:
- name: "EmilLindfors"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/emillindfors-mock-strategy-guide/audits/4"
identifiers:
- type: other
value: "skillstore:emillindfors-mock-strategy-guide:audit:4"
description: "Skillstore immutable audit report identifier"
Design a lightweight repository mock for a Rust service that depends on stored user data.
Capture calls to an email or notification service and assert that the service behaved correctly.
Replace database or HTTP dependencies with trait abstractions and in-memory test implementations.
Help me create a simple Rust mock for a trait-based repository. Explain the structure and the test flow.
Show me how to design a mock service that records calls so my Rust test can verify side effects.
Design a Rust mock strategy that can return success, not-found, and database-error outcomes for service tests.
Review this Rust service design and suggest trait boundaries, mock implementations, and fixture helpers for maintainable tests.
Author
EmilLindforsLicense
MIT
Author version
v1.0.0
Skillstore revision
r1
Ref
a06681402992ceae98ba04d54cfd4ab004862696
Maintenance freshness
7/18/2026
Usage
4 downloads · 136 views
File structure
📄 SKILL.md
Simplify Rust If-Let Control Flow
Nested pattern matching can hide the main decision path in Rust code. This skill helps Claude, Codex, and Claude Code suggest let chains for clearer Rust 2024 control flow.
Improve Rust Test Coverage
Missing tests leave Rust error paths and edge cases unprotected. This skill reviews code and tests, then suggests targeted coverage improvements.
Design Rust Port and Adapter Boundaries
External services can leak infrastructure concerns into domain code. This skill helps design Rust traits and adapters that keep dependencies isolated and testable.
Build Rich Rust Domain Models
Weak domain layers scatter business rules and make validation inconsistent. This skill helps Claude, Codex, and Claude Code design expressive Rust domain models.
Optimize Rust AWS Lambda Functions
Rust Lambda functions can waste cost through slow I/O, cold starts, and poor memory settings. This skill reviews handlers and deployment settings, then suggests concrete performance and cost improvements.
Improve Rust Error Handling
Many Rust codebases hide failures behind panics or vague errors. This skill reviews patterns and suggests idiomatic Result, thiserror, and anyhow improvements.
Plan Reliable Tests Across Your Codebase
by 0xDarkMatter
This skill helps teams choose test strategies, mocks, data fixtures, coverage gates, and CI patterns without mixing test scopes. It gives Claude, Codex, and Claude Code structured guidance for unit, integration, end-to-end, TDD, and pipeline testing.
Build Reliable Test Automation
by 89jobrien
Weak tests slow releases and hide regressions. This skill guides test strategy, TDD, automation, coverage review, and Playwright web checks.
Debug Technical Failures Systematically
by Asmayaseen
Quick fixes often hide the real cause and create regressions. This skill structures investigation, hypothesis testing, implementation, and verification around collected evidence.
Build Better Go Tests
by 89jobrien
Go teams need consistent tests across units, integrations, mocks, benchmarks, and coverage. This skill provides practical Go testing patterns that Claude, Codex, and Claude Code can apply during development.
Build Enterprise Go Architecture
by 89jobrien
Large Go systems can lose clear boundaries as teams add features. This skill gives Claude, Codex, and Claude Code structured patterns for clean architecture, DDD, and production service layout.
Enforce Waterfall Phase Gates
by Chemiseblanc
AI coding sessions can skip requirements, design, or testing when pressure rises. This skill keeps work inside a strict waterfall flow with documented gates.