onepub-dev / onepub-dev/reVault
Add tests for the native libraries in each language binding.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 0
- Avg merge
- 1h 55m
- Merged PRs (30d)
- 1
Description
We need to ensure that we have e2e coverage of deploying a language binding for each of the supported languages.
The tests need to ensure that the native library deploys as expect (are PATHS important here?) and that the api is then fully functional.
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 files, supported languages, or existing test entry points are named. First map the language bindings and their native-library deployment paths, then locate the current end-to-end test setup. Done means each supported binding deploys its native library and exercises the API successfully, including any PATH behavior the project confirms is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100