-
-
Notifications
You must be signed in to change notification settings - Fork 16
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.
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
🚧Refactor unit test assertions #359
Comments
This issue has been automatically marked as stale due to the lack of activity for 60 days. The issue will be closed after 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale due to the lack of activity for 60 days. The issue will be closed after 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale due to the lack of activity for 60 days. The issue will be closed after 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale due to the lack of activity for 60 days. The issue will be closed after 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale due to the lack of activity for 60 days. The issue will be closed after 7 days if no further activity occurs. Thank you for your contributions. |
Hello, I would like to work on this! Please assign it to me! |
Absolutley!! If you have any questions, please don't hesitate to ask. I have a discord server as well that you can join and ask questions. |
The |
Complete The Item Below
Description
Refactor all of the unit test assertions to use the FluentAssertions library.
This will greatly cleanup the unit testing side of things and make the creation of unit tests easier.
Acceptance Criteria
GLFWErrorEventArgsTests.cs
- 37 linesGLFWDisplayChangedEventArgsTests.cs
- 22 linesGLFWDisplayTests.cs
- 211 linesOpenGLServiceTests.cs
- 439 lines- 158 linesBufferManagerTests.cs
ToDo Items
Issue Dependencies
No response
Related Work
No response
Additional Information:
Change Type Labels
🐛bug
🧨breaking changes
✨new feature
workflow
🗒️documentation/code
📝documentation/product
Priority Type Labels
low priority
medium priority
high priority
Code of Conduct
The text was updated successfully, but these errors were encountered: