posit-dev / posit-dev/positron
e2e Testing: Add method to track versions used of dependencies
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 206
Description
We occasionally have tests that fail due to 3rd party dependencies changing. Such as https://github.com/rstudio/reticulate/issues/1811.
I think it would be good if we had a way to record the versions of dependencies used for each test run. Then we can see what changed between a good and bad run and help debug if it was a dependency update.
Not sure the best way to track, so whomever picks this up might need to talk it over to with the team. This could be just dumping all the versions to a file in the repo each time.. or just spitting it out to console..
Thoughts on what to track:
- Python modules from
qa-example-content/requirements.txt - R modules from
qa-example-content/DESCRIPTION uvandcondaversions- Github runner image
- Anything else we install from "latest" ?
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 reviewing qa-example-content/requirements.txt and qa-example-content/DESCRIPTION, then inspect the e2e test-run configuration and GitHub runner setup. Define with the team which dependency and environment versions must be recorded and where the output should appear; done means each test run captures the agreed versions for later comparison.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, r
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100