RGB-Tools / RGB-Tools/rust-lightning
fix unit tests
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 9
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Running the unit tests currently results in a bunch of compilation errors and test failures, I assume because it's a pain to maintain so many tests & maybe many of them are irrelevant to this branch's work on RGB. But could the failures be hiding any bugs? It might be worth taking a stab at fixing this.
As an experiment I let Claude run for a while and fix a bunch of bugs when the main package is run, i.e. cargo test -p lightning: https://github.com/orbitalturtle/utexo-rust-lightning/pull/1
It was able to fix the compilation errors and fix 77/81 failing tests, I believe. But its work would need some review.
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 running cargo test -p lightning to catalog the compilation errors and failing tests. Review the changes in the referenced pull request and determine which failures represent real bugs versus outdated or irrelevant tests. Done means the test suite builds and the remaining failures have been resolved or clearly justified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100