databrickslabs / databrickslabs/pytester

[TODO] Investigate and fix this if possible, to avoid breakage in future pytest versions.

Open
#167 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

tech debt
Dominant language
Python
Stars
139
Forks
16
PR merge metrics
No merged PRs in 30d

Description

Contributor guide

Open the contributing guide

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

Start by reading the referenced lines 19–24 in src/databricks/labs/pytester/fixtures/unwrap.py and the linked blame context. Investigate the behavior against relevant pytest versions; done means the potential future compatibility breakage is fixed or its limitation is clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.