Document that the jest code mods won't cover all cases? · mjackson/expect#230

(4 comments) (0 reactions) (0 assignees)JavaScript (2,290 stars) (132 forks)batch import

documentationhelp wanted

説明

I'm trying out migrating from mocha & expect to just jest.

The code mods handled most of the cases, but there are some MAJOR differences in how Jest's isEqual matcher works, mostly because it does not use the is-equal package anymore.

This means things like this worked with expect but DO NOT work with jest:

expect(["abc"]).toEqual("abc");

function createEnhancedFunction() {
  var myFunction = function() { return "a value"; };
  myFunction.a = "123";
  return myFunction;
}

expect({ a: createEnhancedFunction() }).toEqual({ a: createEnhancedFunction() });

The first difference is easy to work around, but the second one (inability to compare functions and treat them as equal) has me a little stumped.

I'd think it would be good to emphasize that is-equal is no longer used for equality checks, and maybe suggest some workarounds in the docs?

コントリビューターガイド

技術スタック: javascript
領域: testing
Issue 種別: documentation
難度: 2
推定時間: 1-3 hours
活動状況: stale
明確さ: clear
前提条件: なし
初心者向け度: 80
調査方針: Investigate the current documentation of the expect library to see if it already mentions the differences between expect and jest equality matchers. If not, add a section highlighting that jest no longer uses the `is equal` package and provide workarounds for common cases like comparing functions or arrays. Consider linking to relevant files such as README.md or the docs folder.