The ## Why Not pytest? section (README) is a head-to-head pytest-vs-apte
table. It reads as a challenge to replace pytest, which invites the wrong
framing ("apte wants to kill pytest", "benchmark of sleep", ecosystem
arguments) and puts apte on the defensive.
apte's actual position is complementary: async-first engine + native evals.
That's a niche, not a pytest replacement.
Proposed:
- Remove the comparison table.
- Keep the honest one-liner that already follows it ("pytest has a large
ecosystem; apte is an alternative if you ...") and lead with what apte is
for (async-native tests + evals in one place), not what pytest isn't.
Context: surfaced while writing up a benchmark. Performance numbers are good,
but presenting them next to a "vs pytest" table makes a clean result read as a
turf claim.
The
## Why Not pytest?section (README) is a head-to-head pytest-vs-aptetable. It reads as a challenge to replace pytest, which invites the wrong
framing ("apte wants to kill pytest", "benchmark of sleep", ecosystem
arguments) and puts apte on the defensive.
apte's actual position is complementary: async-first engine + native evals.
That's a niche, not a pytest replacement.
Proposed:
ecosystem; apte is an alternative if you ...") and lead with what apte is
for (async-native tests + evals in one place), not what pytest isn't.
Context: surfaced while writing up a benchmark. Performance numbers are good,
but presenting them next to a "vs pytest" table makes a clean result read as a
turf claim.