nuts-foundation / nuts-foundation/nuts-node
Branch builds running end-to-end test should test against the latest version from "master"
Open
Nobody has claimed this yet.
prio: low
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
The end-to-end test spins up 2 nodes. One of them should be running the branch build, the other one the latest "master" version. That way we can assert new versions work properly with the previous version.
Older versions (say, a week or a month ago) might still break, though.
Contributor guide
No contributing guide indexed for this repository
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
No file or test path is named. Locate the branch-build end-to-end test and its two-node setup, then trace how each node's version is selected; done means one node runs the branch build and the other runs the latest master version, with coverage confirming compatibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100