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.

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 #363

Closed
18 tasks done
kselena opened this issue Sep 8, 2022 · 4 comments · Fixed by #724
Closed
18 tasks done

🚧Refactor unit test assertions #363

kselena opened this issue Sep 8, 2022 · 4 comments · Fixed by #724
Assignees
Labels
good-first-issue Good for newcomers medium-priority Medium Priority preview Done while in preview tech-debt Code refactoring or cleanup / tech debt reduction

Comments

@kselena
Copy link
Member

kselena commented Sep 8, 2022

Complete The Item Below

  • I have updated the title without removing the 🚧 emoji.

Description

Refactor all of the unit test assertions to use the FluentAssertions library.

This will greatly clean up the unit testing side of things and make the creation of unit tests easier.

Acceptance Criteria

  • Latest version of FluentAssertions Nuget package added to the project
  • Refactor the files below:
    • ShaderManagerTests.cs - 176 lines - Remove in previous release
    • ShaderProgramTests.cs - 407 lines
    • TextureShaderTests.cs - 86 lines
    • BatchSizeAttributeTests.cs - 25 lines - Remove in a previous release
    • FontGlyphBatchItemTests.cs - 366 lines - Work performed with other issue
    • GLErrorEventArgsTests.cs - 39 lines
    • GLWindowTests.cs - 1537 lines
    • GPUBufferNameAttributeTests.cs - 39 lines
    • OpenGLExtensionMethodsTests.cs - 312 lines
    • ShaderNameAttributeTests.cs - 39 lines

ToDo Items

  • Change type labels added to this issue. Refer to the Change Type Labels section below.
  • Priority label added to this issue. Refer to the Priority Type Labels section below.
  • Issue linked to the correct project (if required).
  • Issue linked to the correct milestone (if required).

Issue Dependencies

No response

Related Work

No response

Additional Information:

Change Type Labels

Change Type Label
Bug Fixes 🐛bug
Breaking Changes 🧨breaking changes
New Feature ✨new feature
Workflow Changes workflow
Code Doc Changes 🗒️documentation/code
Product Doc Changes 📝documentation/product

Priority Type Labels

Priority Type Label
Low Priority low priority
Medium Priority medium priority
High Priority high priority

Code of Conduct

  • I agree to follow this project's Code of Conduct.
@kselena kselena added tech-debt Code refactoring or cleanup / tech debt reduction medium-priority Medium Priority labels Sep 8, 2022
@stale
Copy link

stale bot commented Nov 16, 2022

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.

@stale stale bot added the stale Signifies that an issue is stale label Nov 16, 2022
@CalvinWilkinson CalvinWilkinson removed the stale Signifies that an issue is stale label Nov 16, 2022
@CalvinWilkinson CalvinWilkinson added the preview Done while in preview label Dec 21, 2022
@stale
Copy link

stale bot commented Feb 19, 2023

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.

@stale stale bot added the stale Signifies that an issue is stale label Feb 19, 2023
@CalvinWilkinson CalvinWilkinson removed the stale Signifies that an issue is stale label Feb 21, 2023
@stale
Copy link

stale bot commented Apr 22, 2023

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.

@stale stale bot added the stale Signifies that an issue is stale label Apr 22, 2023
@CalvinWilkinson CalvinWilkinson removed the stale Signifies that an issue is stale label Apr 24, 2023
@CalvinWilkinson CalvinWilkinson added the good-first-issue Good for newcomers label May 8, 2023
@CalvinWilkinson CalvinWilkinson removed their assignment May 8, 2023
@stale
Copy link

stale bot commented Jul 9, 2023

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.

@stale stale bot added the stale Signifies that an issue is stale label Jul 9, 2023
@CalvinWilkinson CalvinWilkinson removed the stale Signifies that an issue is stale label Jul 9, 2023
@CalvinWilkinson CalvinWilkinson self-assigned this Sep 4, 2023
@CalvinWilkinson CalvinWilkinson added this to the v1.0.0-preview.26 milestone Sep 4, 2023
CalvinWilkinson added a commit that referenced this issue Sep 4, 2023
CalvinWilkinson added a commit that referenced this issue Sep 4, 2023
* Start work for issue #363

* tests: refactor to fluent assertions

* tests: refactor to fluent assertions

* tests: refactor to fluent assertions

* tests: refactor to fluent assertions

* tests: refactor to fluent assertions

* tests: refactor to fluent assertions

* refactor: change code to meet coding standards
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good-first-issue Good for newcomers medium-priority Medium Priority preview Done while in preview tech-debt Code refactoring or cleanup / tech debt reduction
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants