pytest-dev / pytest-dev/pytest-html

pytest --html=report.html, is working locally, but not creating report in GIt repository with help of GitHub Action

Open
#579 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs more info
Dominant language
Python
Stars
779
Forks
260
PR merge metrics
No merged PRs in 30d

Description

pytest --html=report.html, is working locally, but not creating report in GIt repository with help of GitHub Action

in Github action, im expecting report to get created in root directory. but nothing is getting created. can you help?

Following is my yml file 👍
name: Test Execution for OrangeHRM - Demo Environment
on:
schedule:

  • cron: '20 * * * *'

jobs:
build:

runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v3
- name: Set up Python
  uses: actions/setup-python@v3
  with:
    python-version: '3.x'
- name: Install dependencies
  run: |
     python -m pip install --upgrade pip
     pip install setuptools wheel twine
     pip install selenium
     pip install pytest
     pip install PyGithub
     pip install pytest-html
     pip install allure-pytest
     pip install pytest-github-report
     pip install webdriver-manager
     pip install pytest-failed-screenshot
     pip install pytest-metadata
     pip install pytest-cov
- name: Test Execution after 20 mins interval
  run: |
     pytest --html=report.html

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the GitHub Actions workflow shown in the issue and inspect the step running pytest --html=report.html, including its run log and working directory. Determine whether report.html is produced during the job; done means the workflow behavior and expected repository output are explicitly verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, python
Domain
ci-cd, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.