databrickslabs / databrickslabs/pytester
Test against matrix of dependencies
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 139
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Problem statement
Pytester is intended as a library used by other projects. Therefore, we prefer to keep the dependency version constrain broad so that the projects have more room to choose the versions they desire. Currently we test pytester for differen python versions, but we do not test pytester for different dependency version:
Solution
Use tox to test pytester against a matrix of dependency versions. (Tox is a commonly used tool for this.) For starters, let's test against a matrix of the Databricks Python SDK as that is experimental. The lsql is a good second one as that is probably less stable than pytest itself. Finally we can test against different pytest versions, though, I assume that library to be quite stable, especially for the entrypoints we use (fixture)
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 reading .github/workflows/push.yml around the existing Python-version matrix and pyproject.toml around the dependency constraints. Review the linked tox documentation, then define a tox-based matrix beginning with the Databricks Python SDK, followed by lsql and pytest versions. Done means CI tests pytester across the selected dependency versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100