test: fix assert.strictEqual() parameter order
…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), orvcbuild test
(Windows) passes -
tests and/or benchmarks are included -
commit message follows commit guidelines