test: change order of assert.strictEquals arguments
Fix assert.strictEquals argument order.
Arguments were actual first, expected second, contrary to the documentation. Now, actual value is first and expected value is second.
Checklist
-
make -j4 test
(UNIX), orvcbuild test
(Windows) passes -
commit message follows commit guidelines