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

Fix unit tests assertion parameters for expected and actual values #55

Open
Arlodotexe opened this issue Dec 4, 2021 · 0 comments · May be fixed by #642
Open

Fix unit tests assertion parameters for expected and actual values #55

Arlodotexe opened this issue Dec 4, 2021 · 0 comments · May be fixed by #642

Comments

@Arlodotexe
Copy link
Member

Expected behavior

In unit tests, Assert methods such as Assert.AreEqual(value, otherValue) should have the first parameter be the expected value, second parameter the actual value.

Current behavior

Some correct usage, mostly backwards. Example
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@Arlodotexe