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.
Checklist
-
make -j4 test
(UNIX), orvcbuild test
(Windows) passes -
commit message follows commit guidelines