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: assert.strictEqual parameters ordered correctly #23538

Closed
wants to merge 1 commit into from
Closed

test: assert.strictEqual parameters ordered correctly #23538

wants to merge 1 commit into from

Commits on Oct 12, 2018

  1. test: assert.strictEqual parameters ordered correctly 

    The assert.strictEqual function should have the actual
value first and the expected value second to enable
easier debugging of AssertionErrors.
    @jdenbroeder
    jdenbroeder committed Oct 12, 2018
    Configuration menu
    Copy the full SHA
    7dbc40c View commit details
    Browse the repository at this point in the history