Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/python-testingReporting and compliance

python-testing

⁨Python testing with pytest: fixtures, parametrization, mocking, test organization, async tests, Hypothesis, ExceptionGroup, free-threaded caveats, coverage, and CI hygiene. Use when writing or reviewing Python tests to improve correctness and reduce flakiness.⁩

v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/python-testing

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
L1xLi8p/Rc…gAGFd7CQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package27219579…d55c1b21
27219579d63d…c755d55c1b219 files · ⁦5.7 KB⁩
ScanLow1 finding
  • Links to outside domains
See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/coding/python-testing@21cd568

High-signal guidance for writing tests that are deterministic, readable, and maintainable.

When to activate

  • Adding tests (unit/integration) for new or existing code
  • Refactoring tests to reduce flakiness
  • Designing fixtures and test organization
  • Adding coverage, CI checks, or async tests
  • Property tests (Hypothesis) or concurrent/free-threaded suites

Outcome expectations

  • Tests are deterministic and pass reliably in CI.
  • Coverage is meaningful; assertions test behavior, not implementation details.
  • Flaky tests are rare and quickly diagnosed (fixtures, mocking, timing).
  • New developers can understand test intent within 30 seconds of reading.

For new code: Use test-driven-development when implementing test-first; it owns the loop and the entry points for existing code and refactors. Use this skill for pytest mechanics.

For flaky/failing tests:

  1. Check for shared state (mocks, fixtures, filesystem).
  2. Check for timing assumptions (avoid sleep, use synchronization).
  3. Check mock patch targets (patch as used, not where defined).
  4. Isolate to minimal reproduction in separate test.

Core rules

  • Prefer small unit tests for logic; use integration tests for boundaries.
  • Use pytest fixtures to remove duplication, but avoid fixture overengineering.
  • Avoid sleeping in tests; synchronize via conditions/events.
  • Mock at boundaries (network, time, DB), not everywhere.
  • Coverage is a signal: aim for meaningful assertions, not line-hits.
  • Do not add production hooks solely for tests; use real seams or dependency injection.
  • Pair with test-driven-development when implementing persistent code or bug fixes test-first.
  • If mocks, timing, or flakes dominate, pair with testing-reliability; if the root cause is unclear, pair with systematic-debugging.
  • Asyncio-heavy tests: also load python-async-patterns testing.md.
  • CancelledError and ExceptionGroup are not caught by pytest.raises(Exception) / pytest.raises(ValueError) respectively.

Resources

Load on demand:

  • references/tdd-and-structure.md — load when naming and organizing tests; routes test-first work to the shared workflow
  • references/fixtures-parametrize.md — fixtures (scopes, autouse), parametrization patterns
  • references/mocking.md — unittest.mock, patching correctly, async mocks
  • references/async.md — pytest-asyncio loop scope; cancellation/ExceptionGroup pointers
  • references/concurrency.md — load for threads, InterpreterPoolExecutor, free-threaded suites
  • references/property.md — load when example tests miss a space Hypothesis can shrink
  • references/coverage-ci.md — pytest-cov, coverage hygiene, CI tips
  • references/commands.md — common pytest commands and selectors

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd56827219579Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login