Skills tdd-pytest
๐Ÿ“ฆ

tdd-pytest

v1.0.1 Content revision r1 Safe โš™๏ธ External commands

Build Python Tests with pytest TDD

Python teams often need consistent tests, coverage, and reports without losing TDD discipline. This skill provides pytest-focused workflows, examples, and reporting guidance for Claude, Codex, and Claude Code.

Supports: Claude Codex Code(CC)
๐Ÿฅˆ 81 Silver

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "tdd-pytest" from https://skillstore.io/skills/89jobrien-tdd-pytest.md and its manifest at https://skillstore.io/api/skills/89jobrien-tdd-pytest/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "tdd-pytest". A developer asks for tests before adding password validation.

Expected outcome:

The skill proposes failing pytest cases for valid passwords, short passwords, missing characters, and empty input before implementation steps.

Using "tdd-pytest". A maintainer asks whether current tests are useful.

Expected outcome:

The skill returns a quality review covering fixture reuse, assertion strength, parametrization opportunities, and missing edge cases.

Using "tdd-pytest". A team asks for a local testing report after a pytest run.

Expected outcome:

The skill outlines a report with pass and fail counts, coverage by module, audit findings, recommendations, and command evidence.

Security Audit

Safe
v7 โ€ข 7/5/2026 Open versioned report

All static findings were markdown formatting or pytest documentation false positives, not executable Ruby or shell backtick execution. I found no prompt injection, data exfiltration intent, or malicious behavior in SKILL.md.

1
Files scanned
207
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/89jobrien-tdd-pytest/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/89jobrien-tdd-pytest/security.svg)](https://skillstore.io/skills/89jobrien-tdd-pytest?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/89jobrien-tdd-pytest?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/89jobrien-tdd-pytest/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/89jobrien-tdd-pytest.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

Joseph OBrien. (2026). tdd-pytest security audit report (audit version 7) [Author version 1.0.1]. Skillstore. https://skillstore.io/skills/89jobrien-tdd-pytest/audits/7

BibTeX citation

@techreport{joseph-obrien-89jobrien-tdd-pytest-2026, author = {Joseph OBrien}, title = {tdd-pytest security audit report (audit version 7)}, institution = {Skillstore}, year = {2026}, number = {7}, url = {https://skillstore.io/skills/89jobrien-tdd-pytest/audits/7}, note = {Author version 1.0.1} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "tdd-pytest security audit report (audit version 7)" version: "1.0.1" type: report authors: - name: "Joseph OBrien" date-released: "2026-07-05" url: "https://skillstore.io/skills/89jobrien-tdd-pytest/audits/7" identifiers: - type: other value: "skillstore:89jobrien-tdd-pytest:audit:7" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
100
Maintainability
87
Content
71
Community
91
Spec Compliance

What You Can Build

Add tests before implementation

Plan failing pytest cases first, then implement only enough behavior to pass them.

Audit an existing test suite

Review pytest files for naming, fixture quality, coverage evidence, and missing edge cases.

Standardize pytest configuration

Create practical pyproject.toml settings for discovery, markers, warnings, and coverage reporting.

Try These Prompts

Start a TDD cycle
Use the tdd-pytest workflow for this Python feature. First propose the smallest failing pytest case, then describe the minimal implementation needed to pass it.
Write targeted tests
Write pytest tests for this behavior. Include normal cases, edge cases, and one failure case. Keep the tests focused and explain why each test exists.
Audit test quality
Audit these pytest tests for clarity, fixture design, parametrization, missing assertions, and coverage gaps. Return prioritized recommendations with file and line references.
Prepare a test report
Summarize the pytest run, coverage results, failures, skipped tests, and recommended fixes in TESTING_REPORT.local.md format. Include command evidence and priority levels.

Best Practices

  • Write the smallest failing test before changing production code.
  • Run focused tests first, then run the broader suite with coverage.
  • Keep reports local and include clear evidence for each recommendation.

Avoid

  • Writing broad tests that do not verify specific behavior.
  • Changing implementation before confirming the test fails for the right reason.
  • Using shared fixtures that hide setup details or make failures unclear.

Frequently Asked Questions

Does this skill run tests automatically?
It documents pytest commands and workflows. Execution depends on the host agent, user permissions, and repository environment.
Does it require uv?
The examples use uv, but the pytest guidance can be adapted to other Python environment tools.
Can it help with async pytest tests?
Yes. The skill includes async test patterns and pytest configuration guidance for event loop behavior.
Can it generate coverage reports?
It guides coverage command selection and report structure. The actual coverage run requires project dependencies to be installed.
Can it review existing tests?
Yes. It can audit naming, fixtures, assertions, parametrization, coverage evidence, and missing cases.
Is it only for unit tests?
No. It can guide unit and integration tests when the expected behavior and test boundaries are clear.

Developer Details

License

MIT

Author version

v1.0.1

Skillstore revision

r1

Ref

c4037264bbd363c572662d6154a3ab28f5ca4f53

Maintenance freshness

7/18/2026

Usage

10 downloads ยท 238 views

File structure

๐Ÿ“„ SKILL.md

More from Joseph OBrien

View all