pytest-dev / pytest-dev/pytest
experiment with the effect of different terminal widths on the test result and testing in general
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
when we took note that certain terminal widths affect the testing, we just configured a default for the full test suite
however this demonstrated that we have a blind spot there
we really need to get a idea what happens to the tests/ux in general when the width is either too small or too big
initial experiments could just vary COLUMNS to identify the areas where things may go south - once pinpointed exact tests an be added
Originally posted by @RonnyPfannschmidt in https://github.com/pytest-dev/pytest/issues/11425#issuecomment-1712886430
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by varying the COLUMNS environment variable while running the full test suite, comparing behavior across terminal widths. Record the areas where tests or user experience go wrong; done means the affected areas are identified clearly enough for exact tests to be added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100