oasisprotocol / oasisprotocol/oasis-sdk
Write an e2e test that generates only valid operations
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 90
- Forks
- 35
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 5
Description
The current txgen e2e test generates all kinds of transactions, including invalid ones, so errors are expected and we can't fail the test on error.
We should write a separate test that also uses txgen to generate transactions for the simple-keyvalue runtime, but in a more intelligent way -- the generated insert/get/remove operations should always succeed, so that we can detect when an actual error happens and fail the test.
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
Start by locating the current txgen end-to-end test and the simple-keyvalue runtime setup. Add a separate test that generates insert, get, and remove operations in an order or with inputs that always succeed, then run the e2e test to confirm unexpected errors fail it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100