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

test: use the correct parameter order on assert.strictEqual() #23520

Closed
wants to merge 1 commit into from
Closed

test: use the correct parameter order on assert.strictEqual() #23520

wants to merge 1 commit into from

Commits on Oct 12, 2018

  1. test: use the correct parameter order on assert.strictEqual() 

    The parameter order for assert.strictEqual() should be actual, expected
rather than expected, actual which can make test failure messages
confusing. This change reverses the order of the assertion to
match the documented parameter order.
    @lrdcasimir
    lrdcasimir committed Oct 12, 2018
    Configuration menu
    Copy the full SHA
    211f4b1 View commit details
    Browse the repository at this point in the history