open-telemetry / open-telemetry/opentelemetry-python
Run tests in random order
Open
Nobody has claimed this yet.
bug
tests
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
Actually, this reminds me that we should run tests in random order.
Originally posted by @ocelotl in https://github.com/open-telemetry/opentelemetry-python/pull/2757#discussion_r896099799
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 checking the repository's test configuration and pytest setup, then review the pytest-random-order documentation linked in the issue. Done means the test suite runs in randomized order through the project's normal test command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100