Pytest Development

Workflow

1. Identify behavior - Target a single function/behavior per test
2. Write the test - Plain function (never a class) with AAA structure
3. Run and iterate - Refine for readability and isolation

Best Practices

• Write plain functions, no test classes
• Name tests test_<function>_<behavior> — be specific about inputs and outcomes
• One test per distinct behavior; multiple assertions are fine when verifying one operation's effects
• Use parametr

[Description truncada. Veja o README completo no GitHub.]