quarto-dev / quarto-dev/quarto-cli
Tests suite improvement ideas
Open
@cderv is already working on this.
Since Sep 6, 2024.
enhancement
epic
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
This issue is here to track improvement ideas for ou tests suites
Testing built versions
- Scheduled test on our latest build version (would help surface https://github.com/quarto-dev/quarto-cli/issues/4257 maybe)
Computations
- Testing with latest versions of R, Python and Julia packages
- Testing with dev versions of some R, Python and Julia packages
- Testing with pinned version of some know package to insure no regression (e.g for https://github.com/quarto-dev/quarto-cli/issues/4122 where jupyter-client 7 or 8 will have difference and we want to support boths)
Test performance
- Improve speed of commit testing - parallelization ?
- #4099
- #10696
Publishing
- We need to test
quarto publishbefore release somehow
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.
Assessment
This issue has not been assessed yet.