Skip to content

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

Open
@Arlodotexe

Description

@Arlodotexe

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions