26. Test Reporting

What it does: Generates a single-file HTML report summarizing pass/fail/skip results after a test run.

Types/params:

Pointers: Good baseline reporting with minimal setup. Lacks the richer history-tracking and screenshot/trace attachment support that Allure offers — reach for Allure once a team needs more than a quick pass/fail summary.

• --html=<path> (string, required) — output file location
• --self-contained-html (flag, optional) — embeds CSS/JS directly in the file so it's viewable standalone without needing internet access or separate asset files

pip install pytest-html

allure serve allure-results # opens an interactive report locally

What it does: Writes raw result data (in Allure's format) to a directory during the test run, to be rendered into a report afterward.

Types/params:

Pointers: Requires the separate Allure command-line tool (allure serve / allure

generate) to actually render the raw results into a viewable report — the allure-pytest package alone only produces the raw data.

@allure.step("Log in as test user")

...

@allure.attach(name="screenshot", attachment_type=allure.attachment_type.PNG)

@allure.step(description)

What it does: Marks a function as a named step in the Allure report, so the report shows a readable step-by-step breakdown of what a test did, not just pass/fail.

Types/params:

Pointers: Especially valuable for longer tests/flows — a failed test's Allure report will show exactly which named step failed, rather than requiring someone to read raw code to figure out where things went wrong.

• --alluredir=<path> (string, required) — directory to write raw result files to
• description (string, required) — human-readable label shown in the report

def login(page):

- name: Upload test report

with:

path: report.html

actions/upload-artifact (GitHub Actions built-in action)

What it does: Saves specified files/directories from the CI run so they're downloadable after the workflow finishes, instead of only existing in ephemeral CI logs.

Types/params:

Pointers: if: always() is important here — without it, the upload step is skipped whenever the test step itself fails, which is exactly the case where you most need the report/trace artifacts to debug what went wrong.

• name (string) — artifact name shown in the GitHub UI
• path (string) — file or directory to upload

if: always()