Clarify that assert_equals relies on ===

[tobie]

Sorry for creating a branch here for this. The new GH Web interface no longer lets you create branches in your own fork. :(

---

This change is 

[annevk]

Does it? I thought it still used ==...

[wpt-pr-bot]

Notifying @dontcallmedom, @gsnedders, @sideshowbarker, and @zcorpan. (Learn how reviewing works.)

[tobie]

@annevk: https://github.com/w3c/web-platform-tests/blob/master/resources/testharness.js#L866-L876

[w3c-bots]

View the complete job log.

Firefox (nightly channel)

Testing web-platform-tests at revision 736688f
Using browser at version BuildID 20170501100238; SourceStamp 076a7a66096f9e8d102548397254be32eb26bc3d
Starting 10 test iterations
No tests run.

[w3c-bots]

View the complete job log.

Chrome (unstable channel)

Testing web-platform-tests at revision 736688f
Using browser at version 60.0.3080.5 dev
Starting 10 test iterations
No tests run.

[annevk]

Oh, cool. Did that change or did I just misremember?

[tobie]

I have no idea. I end-up checking every time, which is why I'm documenting it. The name's a bit of a misnomer, as other JS test frameworks tend to associate equal to == and identical to ===.

[zcorpan]

testharness.js has always used === here.

[gsnedders]

It should be equivalent to Object.is, which just exposes the internal ES SameValue function.

[tobie]

@gsnedders maybe that's what should be in the doc?

[gsnedders]

@tobie IMO yes, especially now there's many sensible things we can link to (like the MDN Object.is page), compared with previously where we only could have linked to the formal SameValue definition.