Skip to content

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

Rodrigo Muino Tomonari requested to merge github/fork/lrdcasimir/fix-assertion-parameter-order into master

The parameter order for assert.strictEqual() should be strictEqual(actual, expected) rather than strictEqual(expected, actual) which can make test failure messages confusing. This change reverses the order of the assertion to match the documented parameter order.

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

Merge request reports