Skip to content

pytest-xhtml is a plugin for pytest that generates a HTML report for test results. #1028

Closed

Description

@defnngj

pytest-xhtml is fully compatible with pytest-html. The only difference is a more beautiful UI style.

github:https://github.com/SeldomQA/pytest-xhtml

Image Image

Activity

  1. RonnyPfannschmidt commented on May 24, 2026

    @RonnyPfannschmidt
    Member

    Hi @defnngj,

    We've reviewed pytest-xhtml. The Python source -- plugin.py, basereport.py, report.py, hooks.py, and others -- is a near-verbatim copy of pytest-html with a mechanical s/pytest_html/pytest_xhtml/g rename. The only meaningful original work is a reskinned HTML/CSS template.

    This is disappointing. A template refresh would have been a welcome pull request or issue here. Instead, the entire codebase was copied into a fresh repository with its history scrubbed, the original authors removed, and the result published on PyPI as independent work -- while registering the same pytest11 entry point to force users to choose one or the other.

    The pytest ecosystem thrives on collaboration. Opening an issue, submitting a PR, or even publishing a properly attributed fork are all constructive paths. What happened here fragments the community, misleads users about the origin of the code, and violates the trust open-source contributors place in each other.

    There are also concrete license issues: the source files carry MPL-2.0 headers from pytest-html, but the repository's LICENSE file was replaced with Apache 2.0 and the pyproject.toml claims MPL-2.0 -- a contradictory and non-compliant state.

    Right now this gives the appearance of a intentional hostile fork

  2. henryhu88 commented on May 25, 2026

    @henryhu88

    Sorry, the pytest html style is outdated, I hope it becomes more beautiful. At the same time, retain users' usage habits of pytest html.
    Actually, I don't want to fork a branch to complete this task because it's not just about fixing bugs.
    Posting issues here is indeed full of provocation, please close this issue.

  3. RonnyPfannschmidt commented on May 27, 2026

    @RonnyPfannschmidt
    Member

    meanwhile i created #1030

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions