🚧Refactor unit test assertions

[kselena]

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 cleanup the unit testing side of things and make the creation of unit tests easier.

Note

1. We have been migrating all of our assertion code for the past 6 months from standard XUnit assertions API to FluentAssertions API API. Most of the code base has been converted and examples can be found all of the place. Please don't hesitate to ask questions and for help if needed.
2. Please follow our Contribution Guide
3. Join the KinsonDigital Community!!

Acceptance Criteria

• Latest version of FluentAssertions Nuget package added to the project
• Refactor the files below:
  • MP3SoundDecoderTests.cs - 107 lines
  • OggSoundDecoderTests.cs - 140 lines
  • SoundDataTests.cs - 172 lines
  • AudioDeviceDoesNotExistExceptionTests.cs - 60 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.

[SyedMSawaid]

Assign me this as well.

[CalvinWilkinson]

@SyedMSawaid Just quick heads up on this one. The unit tests related to sounds can be a little touchy because there is unsafe code in there. There is a chance that some refactoring might have to be done with the mocking side of things, but not sure. It has been awhile since I was in the code.

Usually, you do not have any logic inside of your unit tests and that is bad practice. But at the time I had no choice and things needed to be tested I have plans to clean this up in the future.