Failing integration tests
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 1.4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Originally reported by: jaraco (Bitbucket: jaraco, GitHub: jaraco)
In Github PR 8, Doug Hellmann added some integration tests that fail. Those tests are now included in the test suite but disabled as "expected to fail". This ticket is to track the failure and identify a solution.
Contributor guide
No contributing guide indexed for this repository
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 reviewing the integration tests added in GitHub PR 8 and locating their disabled, expected-to-fail entries in the test suite. Reproduce the failures and investigate the integration behavior described by the issue. Done means identifying a solution and having the affected integration tests pass without being marked expected to fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100