oasisprotocol / oasisprotocol/oasis-core
Test confidential runtimes in long-term tests
Open
Nobody has claimed this yet.
c:key management
c:testing
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
We should test confidential runtimes interacting with key manager(s) in long-term tests.
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 locating the long-term tests and the code covering confidential runtimes and key manager interactions. Determine the existing test conventions and add coverage for those interactions; done means the relevant runtime/key manager scenarios run successfully as part of the long-term tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100