Improve logging output.
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 1
- Forks
- 1
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
The logging output currently uses enginekit/logging. It's logging format was designed to be concise and easily greppable but does require the user to understand a set of icons and concepts before it can be understood.
I don't think this is a particularly good fit for testkit which really should be trying to direct users as to how to fix problems.
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 reviewing the current enginekit/logging output and how testkit presents problems to users. Define a clearer logging format that does not require prior knowledge of icons or concepts and directs users toward fixing failures; done means the revised output is understandable to testkit users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100