Pytest workflow
Skill planifest/planifest-framework/planifest-framework/external-skills/pytest-workflow
A specification framework for agentic development. Agents build from complete specs - not guesses.
npx -y skills add planifest/planifest-framework --skill pytest-workflowAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Pytest verification workflow for Python changes with deterministic fixtures, explicit case strategy, and CI-ready evidence. Use when Python modules need executable pytest evidence before merge; do not use for browser-level E2E or non-Python test tooling decisions.
SKILL.md
2.2 KB, as published. Nobody here has run it
Pytest Workflow
Overview
Use this skill to design pytest suites that are fast enough for daily feedback and stable enough for CI gates.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Trigger examples:
references/trigger-and-examples.md
- Fixture boundary rules:
references/fixture-boundary-rules.md
- Determinism rules:
references/pytest-determinism-rules.md
Templates And Assets
- Test plan template:
assets/pytest-test-plan-template.md
- Fixture stability checklist:
assets/pytest-fixture-stability-checklist.md
- Command profile template:
assets/pytest-command-profile-template.md
Inputs To Gather
- Python modules and behaviors at risk.
- Fixture graph, dependency seams, and isolation constraints.
- Marker strategy and CI runtime/cost limits.
- Known flaky paths (async timing, shared state, environment coupling).
Deliverables
- Pytest test strategy and case matrix.
- Fixture and parametrization policy.
- Local-fast and CI-full command profiles.
- Residual risk and follow-up actions.
Workflow
- Build case strategy with
assets/pytest-test-plan-template.md. - Apply fixture rules from
references/fixture-boundary-rules.md. - Validate determinism using
references/pytest-determinism-rules.md. - Define execution profiles in
assets/pytest-command-profile-template.md. - Finalize with
assets/pytest-fixture-stability-checklist.md.
Quality Standard
- Fixtures are explicit, scoped, and deterministic.
- Case coverage includes happy/edge/failure paths.
- Command profiles are reproducible across local and CI.
Failure Conditions
- Stop when fixture design causes hidden shared state behavior.
- Stop when test determinism cannot be achieved for critical flows.
- Escalate when runtime cost blocks practical feedback loops.