Fix unit tests assertion parameters for expected and actual values

[GabrieleMessina]

Fix ordering of params in assertions with "expected" as first argument and "actual" as second.

Closes #55

PR Checklist

• [x] Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
• [x] Based off latest main branch of toolkit
• [x] PR doesn't include merge commits (always rebase on top of our main, if needed)
• [x] Tested code with current supported SDKs
• [ ] New component
  • [ ] Pull Request has been submitted to the documentation repository instructions. Link:
  • [ ] Added description of major feature to project description for NuGet package (4000 total character limit, so don't push entire description over that)
• [ ] Tests for the changes have been added (for bug fixes / features) (if applicable)
• [ ] Header has been added to all new source files (run build/UpdateHeaders.bat)
• [x] Contains NO breaking changes
• [ ] Every new API (including internal ones) has full XML docs
• [x] Code follows all style conventions