LogoAwesome Skills
  • Search
  • Category
  • Tag
  • Blog
LogoAwesome Skills
LogoAwesome Skills

Discover Open-Source Agent Skills for AI Coding Assistants

Product

  • Search
  • Category
  • Tag
  • Blog

Resources

  • Claude Skill Docs
  • Antigravity Skills Docs

Tools

  • Claude Code
  • OpenCode
  • Cursor
  • Codex
  • Antigravity

Company

  • Privacy Policy
  • Terms of Service
  • Sitemap

Β©2026 Awesome Skills. All rights reserved.

Privacy PolicyTerms
Back to Skills

Real Pytest - No Mocks, Real Tests

Write pytests that test real public interfaces with actual components, no mocking, and precise assertions. MIRA-specific patterns. Use when creating or reviewing tests.

391stars34forksUpdated 2/18/2026
Data Science & MLCode ReviewDocumentationTesting & QA#pytest#documentation#contract-based-testing#testing#code-review#python

Security Assessment

Low Risk(85/100)

Detected risks:

Secret Exposure([SKILL.md] token =)
Security Score85/100

About Real Pytest - No Mocks, Real Tests

The 'Real Pytest - No Mocks, Real Tests' skill provides a rigorous approach to writing tests that focus on real public interfaces with actual components, without relying on mocks. It challenges the common practice of testing implementations directly, instead emphasizing the importance of contract-based testing. This approach ensures that tests validate the intended behavior of a module, ensuring that it meets its guarantees, handles expected failures, and operates within defined boundaries. By focusing on actual interactions and failure modes, this skill helps uncover hidden design flaws and improves the overall robustness of the codebase.

FAQ

How do I write tests using this skill?

Start by analyzing the public interface of the module without looking at the implementation. Document the module's contract, including its purpose, guarantees, expected success scenarios, failure conditions, and dependencies. Then, design tests based on this contract, covering positive, negative, boundary, security, and performance cases.

Is mocking allowed when using this approach?

No, this skill strictly avoids the use of mocks. The tests should interact with actual components to ensure they are testing real functionality, not simulated behavior.

What is the role of the contract-extractor agent?

The contract-extractor agent helps verify your expectations about the module's contract by reading the code and reporting contract facts, without exposing implementation details. This step ensures that the module's implementation aligns with your initial contract analysis.

Can this approach be used for any module?

Yes, this approach is applicable to any module where you need to write tests based on public interfaces. However, the module should have a clearly defined public interface for effective contract analysis.

Are there any environment or dependency requirements?

The tests must be able to run in a functioning environment with all dependencies correctly set up. Skipped tests are not allowed, so either the environment needs to be fixed, or the code must be updated to ensure tests can pass.

Install Real Pytest - No Mocks, Real Tests

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

taylorsatula/mira-OSS

Related Skills

design-control-loop

5,393

rivet-dynamic-apps

40

webgpu-threejs-tsl

1,254

content-quality-auditor

2,997