Unit testing
- Dominant language
- HTML
- Stars
- 931
- Forks
- 163
- PR merge metrics
- No merged PRs in 30d
Description
I have a little time and contributing here seems to be a good option. To refresh my Blazor knowledge testing is a good start, not to mention that I love working with tests.
Is there a strategy I should follow when it comes to unit testing? Any priority order?
By default, I would go through the components and I would add unit tests for all of them.
I see bunit is still used (if I remember correctly I introduced them).
Contributor guide
Research direction
Start by reviewing the existing bUnit tests and how the project’s components are covered. The issue suggests adding unit tests across components but does not name files, priorities, or a specific completion criterion, so agree on a focused scope before starting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100