liquidmetal-dev / liquidmetal-dev/flintlock
[e2e] Add non-go Flintlock client tests
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 73
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 30
Description
**Describe the solution you'd like:**
We need to ensure that Flintlock works with clients that are not Go based. So, we should add some e2e tests where the client of the API is either Node or Python (or perhaps both).
**Why do you want this feature:**
Ensure that we aren't baking in anything that is Go client specific.
**Anything else you would like to add:**
This is a follow on to #468
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 reading the existing e2e test suite and the follow-on issue #468 to understand how Flintlock's API is currently exercised. Add coverage using a non-Go client in Node or Python, or both, and consider the work done when the e2e tests demonstrate that clients outside Go can use the API successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, nodejs, python
- Domain
- api, backend, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100