pytest-dev / pytest-dev/pytest-html

Adding multilevel output folding

Open
#417 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement next-gen
Dominant language
Python
Stars
779
Forks
260
PR merge metrics
No merged PRs in 30d

Description

Hello,

In case of hundreds/thousands cases executed in a single run, it is hard to navigate single table with all the output.
Adding ability to collapse/expand not only the whole results table but also smaller groups would be very convenient.
See attached example which is output from PyCharm's "Export test results to the file" command + screenshot of source file structure.
I imagine that in the simplest form an option would cause adding to the result table rows with "Hide all/Show all (level name)" item.
For example for the attached example there would be the following rows added in the relevant global table rows:
"Hide all/Show all (package 1)"
"Hide all/Show all (test_abc)"
"Hide all/Show all (test_abc_1)"
etc.
Source structure:
image
PyCharm report:
Test Results - pytest_in_all_tests.zip

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

Review the attached PyCharm test-results report and source-structure screenshot to understand the requested hierarchy of collapsible result groups. Define the supported nesting levels and verify that the generated result table can hide and show each named group as well as the whole table.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, python
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.