Move more CI tests to rust tooling

Open
#1,839 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
bash, rust
Domain
ci-cd, testing, tooling

Research direction

Start by inventorying the bash CI scripts and the Rust tests under rust-tooling/ci-tests, then compare where each invokes clippy and which parts of an exercise they covers. Map the overlapping checks before deciding which tests can move; done means the CI behavior is consistent and the relevant checks still pass.

Written by the indexing model from the issue text.

Description

Some CI tests exist as bash scripts, others as rust tests in rust-tooling/ci-tests. Let's move more if not all of the bash stuff to rust. There is especially some overlap with clippy. Both bash scripts and rust tests run clippy over some parts of an exercise. That should be made more consistent.

Dominant language
Rust
Stars
1.8k
Forks
546
Avg merge
3h 58m
Merged PRs (30d)
5

Getting set up

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.

More from exercism/rust

All issues in exercism/rust

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.