Skip to content

test: fix assert.strictEqual() parameter order

Rodrigo Muino Tomonari requested to merge github/fork/lotharthesavior/master into master

…follow the order actual-value->expected-value.

According to the documentation, the strictEqual assertions should follow the order actual-value -> expected-value. This PR is changing the current situation of the test parallel/test-tcp-wrap-connect.js to accomplish it.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines

Merge request reports