nuts-foundation / nuts-foundation/nuts-node
e2e: test whether replacing cURL/Bash tests with IntelliJ HTTP Client improves maintainability
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
Could make tests easier to write and read, see:
- https://hub.docker.com/r/jetbrains/intellij-http-client
- https://blog.jetbrains.com/idea/2022/12/http-client-cli-run-requests-and-tests-on-ci
Idea:
- Keep using Bash to run tests and manage Docker containers
- Replace actual tests (cURL and assertions) with HTTP CLient 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
No files or test entry points are named; start by locating the existing end-to-end Bash tests, cURL requests, assertions, and Docker container orchestration. Read the linked IntelliJ HTTP Client documentation, then determine whether the existing test suite can run HTTP Client tests while Bash continues to manage containers and CI execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, docker
- Domain
- devops, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100