Ecosystem (crater) testing for core crates

Open
#402 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
testing-qa, tooling

Research direction

Start by reading the Crater project and the embedded-hal repository referenced in the issue, then review related issue #381 for existing context. Define which foundational crates and consumers should be tested, how runs would be triggered, and what reporting or mitigation workflow would count as done.

Written by the indexing model from the issue text.

Description

triage-2024-keep

given we have a set of foundational crates depended on by practically the whole ecosystem (like https://github.com/rust-embedded/embedded-hal/), the risk of changes to these foundational crates causing large volumes of annoyance is pretty high.

it'd be awesome to have https://github.com/rust-lang/crater (or something like it) running over consumers of these crates so we can be informed of and mitigate the impacts of any necessary breakage.

possibly related to: https://github.com/rust-embedded/wg/issues/381

cc. @therealprof

Dominant language
No language data
Stars
2.1k
Forks
116
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 rust-embedded/wg

All issues in rust-embedded/wg

Similar issues

More Testing & QA issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.