Vai al contenuto
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-testingReport e 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 installazioni+3 in 7 giorni39 StelleMITsincronizzato 10 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

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

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
L1xLi8p/Rc…gAGFd7CQ==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto27219579…d55c1b21
27219579d63d…c755d55c1b219 file · ⁦5.7 KB⁩
ScansioneBasso1 segnalazione
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/AeonDave/malskill/tree/main/coding/python-testing@21cd568

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

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

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellSìSì
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.11.13-21cd56813 nov 202621cd56827219579Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login