Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Added Categories

Open
#919 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
testing-qa

Research direction

Start by tracing the pytest result handling in the Allure Python integration and identify where Passed, Failed, Skipped, and Broken are assigned. Define the additional xfail and xpass categories, then verify that pytest-supported result outcomes are represented distinctly in generated Allure results.

Written by the indexing model from the issue text.

Description

Currently there are 4 categories that a test result can fall into. Passed, Failed, Skipped, Broken. We currently need the ability to separate xfail from skip and also add xpass. The real win would be to have the full list that pytest supports from a result point of view, allure should be able to categorize it.

Dominant language
Python
Stars
817
Forks
262
Avg merge
3h 20m
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from allure-framework/allure-python

All issues in allure-framework/allure-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.