Skip to content

Add pytest-glow-report to Reporting - #154

Open
godhiraj-code wants to merge 1 commit into
cleder:mainfrom
godhiraj-code:add-pytest-glow-report
Open

godhiraj-code wants to merge 1 commit into
cleder:mainfrom
godhiraj-code:add-pytest-glow-report

Conversation

@godhiraj-code

@godhiraj-code godhiraj-code commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Submission

  • Project: github.com/godhiraj-code/pytest-glow-report
  • PyPI: pypi.org/project/pytest-glow-report
  • License: MIT
  • Section: Reporting

What it does and why it belongs here

A pytest plugin that is on by default after install and writes report.html, report.json and a SQLite run history to a reports folder. It keeps run history in a local SQLite file in the report folder, with no server or cloud dashboard.

Checklist

  • It is a Python project or a resource about testing Python code.
  • It is open source under an OSI-approved license. It is not a commercial SaaS, a hosted platform, or a client for one.
  • It is maintained, documented, and used by people other than its author.
  • This pull request adds only one entry.
  • The entry is in alphabetical order within its section.
  • The entry has the format - [name](link) - Description., and the description is short and contains no marketing language.
  • I am the author or maintainer of this project: yes

Summary by Sourcery

New Features:

  • Add pytest-glow-report to the Reporting section as a pytest plugin for generating HTML and JSON reports with SQLite run history.

@semanticdiff-com

Copy link
Copy Markdown

Review changes with  SemanticDiff

@sourcery-ai

sourcery-ai Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

Reviewer's Guide

Documentation

Adds pytest-glow-report to the README’s Reporting list with a brief summary of its report outputs and SQLite run history.

  • README.md L178

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Tip of the day
💡 Did you know, you can turn on the rule miner and Qodo learns your standards from review history

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

@qodo-code-review

qodo-code-review Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

PR Summary by Qodo

Add pytest-glow-report to the Reporting resources

📝 Documentation 🕐 Less than 5 minutes

Grey Divider

AI Description

• Add pytest-glow-report to the Reporting section in alphabetical order.
• Describe its HTML and JSON reports and local SQLite run history.
Merge Risk 🟢 Low

Blast radius 🟢 Low 💥 0 capabilities

  • No production behavior changes identified.
Behavioral complexity 🟢 Low 🧩 Assessed behavior

  • No production behavior changes identified.
Potential damage 🟢 Low 🩹 Assessed behavior

  • No production behavior changes identified.
Assessed commit 5f4042c
High-Level Assessment

A single alphabetized README entry follows the existing resource-list format; no architectural alternative is warranted.

Files changed (1) +1 / -0

Documentation (1) +1 / -0
README.mdList pytest-glow-report under Reporting +1/-0

List pytest-glow-report under Reporting

• Adds a link between pytest-cloudreport and pytest-html-plus. The description identifies its HTML and JSON reports and SQLite run history.

README.md

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

@llamapreview llamapreview Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LlamaPReview — Verification needed

Whether the project has documentation, a release, recent activity, and users other than its author. These are stated curation criteria, and the project’s maturity and independent use determine whether the entry qualifies.

Exact-head CI remains unresolved (3 failed, 1 pending); no CI-dependent merge-safety claim is made.

Owner action: Inspect the project repository and verify each of these criteria.

Review details and evidence

Material unknowns

  • Whether the project has documentation, a release, recent activity, and users other than its author. These are stated curation criteria, and the project’s maturity and independent use determine whether the entry qualifies.

LlamaPReview checks

  • Read the complete PR-head file contributing.md.
  • Reviewed changed regions in README.md.

Still coding alone? Open CarbonChat, a chat room right inside Codex.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant