Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unit testing #482

Open
Andras-Csanyi opened this issue Feb 7, 2022 · 1 comment
Open

Unit testing #482

Andras-Csanyi opened this issue Feb 7, 2022 · 1 comment

Comments

@Andras-Csanyi
Copy link
Contributor

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).
@jbomhold3
Copy link
Collaborator

Right now only unit tests we have setup is for inputs. To be frank I suck at setting them up. If your skilled in it would love your input on the matter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jbomhold3 @Andras-Csanyi