nuts-foundation / nuts-foundation/nuts-node
Refactor e2e tests for better test coverage
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
We currently have the "RFC021" e2e-test that provides the most coverage, but still not enough. At the same time, it was never intended as the "one test that tests databases".
Should we create a new e2e-test that tests:
- all steps (including now missing revocation) for a particular application flow/use case
- on all supported databases
Then we can simplify RFC021 test to cover only RFC021 (and not discovery and statuslist functionality, like it currently does).
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 reviewing the existing RFC021 e2e test and the project's supported databases. Define the application flow and its complete steps, including revocation, then separate RFC021 coverage from discovery and statuslist functionality. Done means the new flow is tested across all supported databases and RFC021 is reduced to RFC021-specific coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100