liquidmetal-dev / liquidmetal-dev/flintlock
Test reconciliation
Open
Nobody has claimed this yet.
area/testing
kind/feature
priority/important-soon
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 73
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 30
Description
**Describe the solution you'd like:**
The reconciliation has zero tests and that's an important part of the application.
**Why do you want this feature:**
It's an important part of the application and without test, we are living in a terrible medieval dark age without tests.
**Anything else you would like to add:**
Nope.
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
No files, tests, or entry points are named in the issue. Locate the reconciliation implementation and its existing test conventions first, then determine the important reconciliation scenarios to cover; done means the reconciliation behavior has meaningful automated test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100