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 Tests - Explore more advanced NUnit Functionality #129

Open
mbaker3 opened this issue Oct 21, 2022 · 2 comments
Open

Unit Tests - Explore more advanced NUnit Functionality #129

mbaker3 opened this issue Oct 21, 2022 · 2 comments
Labels
effort-low Easy - 1 to 2 hours priority-low Get to it when you get to it. No rush. status-backlog Tasks captured but not yet planned. type-chore Clean-up and optimization

Comments

@mbaker3
Copy link
Member

mbaker3 commented Oct 21, 2022 •
edited
Loading

There are some more advanced attributes that can be assigned to tests. Could we benefit from them in our current tests to increase coverage and testing without as much copy/paste?

Ex: MathUtilTests
@mbaker3 mbaker3 added effort-low Easy - 1 to 2 hours priority-low Get to it when you get to it. No rush. status-backlog Tasks captured but not yet planned. type-chore Clean-up and optimization labels Oct 21, 2022
@tjvezina
Copy link
Contributor

NUnit Docs

TestCase would do what you want, basically run the same test repeatedly with different inputs and expected outputs.

@mbaker3
Copy link
Member Author

mbaker3 commented Oct 22, 2022

yea, [Range] looks interesting too. Writing the GetDigitCount() tests the logic was getting sufficiently complex that I thought maybe NUnit should be doing more of the heavy lifting...or maybe I should embrace repetitive code in my tests.

I think I need to read up on best practices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort-low Easy - 1 to 2 hours priority-low Get to it when you get to it. No rush. status-backlog Tasks captured but not yet planned. type-chore Clean-up and optimization
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mbaker3 @tjvezina