oasisprotocol / oasisprotocol/oasis-core
Derive e2e test account addresses properly
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
The wall of hard-coded accounts in go/oasis-test-runner/scenario/e2e/test_accounts.go are based on deterministic entity/node identities generated by the test harness. Instead of having a wall of hard-coded account addresses, derive these at runtime properly for easier maintainability.
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 with go/oasis-test-runner/scenario/e2e/test_accounts.go and inspect how the test harness generates deterministic entity and node identities. Trace the e2e account setup to determine where addresses can be derived at runtime; done means the hard-coded account address list is removed and the tests obtain equivalent addresses from the generated identities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100