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-testingWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package27219579…d55c1b21
27219579d63d…c755d55c1b219 files · 5.7 KBScanLow1 finding
- Links to outside domains
Sourcegithub.com/AeonDave/malskill/tree/main/coding/python-testing@21cd568
On this page
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.
Recommended triage workflow
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:
- Check for shared state (mocks, fixtures, filesystem).
- Check for timing assumptions (avoid
sleep, use synchronization). - Check mock patch targets (patch as used, not where defined).
- 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-developmentwhen 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 withsystematic-debugging. - Asyncio-heavy tests: also load
python-async-patternstesting.md. CancelledErrorandExceptionGroupare not caught bypytest.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 workflowreferences/fixtures-parametrize.md— fixtures (scopes, autouse), parametrization patternsreferences/mocking.md— unittest.mock, patching correctly, async mocksreferences/async.md— pytest-asyncio loop scope; cancellation/ExceptionGrouppointersreferences/concurrency.md— load for threads,InterpreterPoolExecutor, free-threaded suitesreferences/property.md— load when example tests miss a space Hypothesis can shrinkreferences/coverage-ci.md— pytest-cov, coverage hygiene, CI tipsreferences/commands.md— common pytest commands and selectors
Files in this version
references/89.6 KB
- async.md1.3 KB
- commands.md812 B
- concurrency.md2.1 KB
- coverage-ci.md989 B
- fixtures-parametrize.md1.2 KB
- mocking.md1.4 KB
- property.md952 B
- tdd-and-structure.md971 B
- SKILL.md3.4 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | 27219579 | Signed | – |
More from AeonDave
All from this publisherMore in Reporting and compliance
See the category- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login