Skip to content

test: assert.strictEqual parameters ordered correctly

Rodrigo Muino Tomonari requested to merge github/fork/jdenbroeder/first-test-updates into master

The assert.strictEqual function should have the actual value first and the expected value second to enable easier debugging of AssertionErrors.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

Merge request reports