Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
aeondave/python-testingInformes y cumplimiento

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 instalaciones+3 en 7 días39 EstrellasMITsincronizado hace 10 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

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

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
L1xLi8p/Rc…gAGFd7CQ==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete27219579…d55c1b21
27219579d63d…c755d55c1b219 archivos · ⁦5.7 KB⁩
EscaneoBajo1 hallazgo
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/AeonDave/malskill/tree/main/coding/python-testing@21cd568

Esta entrada todavía no está escrita en tu idioma, así que aparece en 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

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellSíSí
Usa la redSíSí
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. InfoEnlace · Enlaces a dominios externos

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.11.13-21cd56813 nov 202621cd56827219579Firmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login