Complete Unit Tests in Config and Communication
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- C#
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
LukeBot.Config and LukeBot.Communication are both libraries which are the most tested in the repo. They still require some extra work though:
- Config
- Make sure many use cases and APIs are covered
- Add tests for potential ConfUtils (see #1 )
- Communication
- CommunicationSystem
- EventSystem
- IntercomSystem (complete/check for completeness)
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 locating the existing tests for the LukeBot.Config and LukeBot.Communication libraries and compare their coverage with the listed Config, CommunicationSystem, EventSystem, and IntercomSystem areas. Done means the relevant use cases and APIs are covered and IntercomSystem tests have been checked for completeness.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100