assert.equal() and assert.deepEqual() used incorrectly

[LarryBattle]

Not really a bug but could potentially lead to misleading error messages during testing. The problem is that most of the test cases supply the expected value as the actual value and vice versa for assert.equal() and assert.deepEqual().

_Node 0.10.x Assertion Signatures:_

• assert.equal(actual, expected, [message])
• assert.deepEqual(actual, expected, [message])

Example of incorrect usage. File: complex.test.js Line: 16 Code:

assert.equal(10, res.im);

Should be: Code:

assert.equal(res.im, 10);

Matrix.test.js is the only file that uses assert.deepEqual() and assert.equal() correctly.

I'll try to submit a pull request if I have time this week.

[Dakkers]

@LarryBattle cool, thanks for noticing this. if you find yourself too busy, I can take a look.

[LarryBattle]

Used jsfmt for the job.

Code:

 jsfmt --rewrite "assert.deepEqual(a,b) -> assert.deepEqual(b,a)" !(m*.*) --write
 jsfmt --rewrite "assert.equal(a,b) -> assert.equal(b,a)" !(m*.*) --write

Will make pull request soon.