pytest-dev / pytest-dev/pytest-html
[Feature Request] Aggregate by exception
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 779
- Forks
- 260
- PR merge metrics
- No merged PRs in 30d
Description
I don't know if this is the right place to do this, but I'd love a way of aggregating failures by exception type, message, or error line. In a large codebase, a small change can generate a cascade of failures that actually are only down to errors in one or two places. It would be really helpful to be able to see that although 50 tests failed, 40 of them were from a db connectivity error and the other 10 arose from the same error in a utility function.
The alternative would be to tackle it at the CLI level, but I like the idea of being able to dynamically aggregate by different views to work out what's going on.
Happy to aid in the development if this would be a welcome feature.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reviewing pytest-html's existing report generation and failure display, then assess whether aggregation belongs in the report or CLI. Done should provide useful grouping by exception type, message, or error line and make cascaded failures easier to interpret.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100