te')); return $arr; } /* 遍历用户所有主题 * @param $uid 用户ID * @param int $page 页数 * @param int $pagesize 每页记录条数 * @param bool $desc 排序方式 TRUE降序 FALSE升序 * @param string $key 返回的数组用那一列的值作为 key * @param array $col 查询哪些列 */ function thread_tid_find_by_uid($uid, $page = 1, $pagesize = 1000, $desc = TRUE, $key = 'tid', $col = array()) { if (empty($uid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('uid' => $uid), array('tid' => $orderby), $page, $pagesize, $key, $col); return $arr; } // 遍历栏目下tid 支持数组 $fid = array(1,2,3) function thread_tid_find_by_fid($fid, $page = 1, $pagesize = 1000, $desc = TRUE) { if (empty($fid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('fid' => $fid), array('tid' => $orderby), $page, $pagesize, 'tid', array('tid', 'verify_date')); return $arr; } function thread_tid_delete($tid) { if (empty($tid)) return FALSE; $r = thread_tid__delete(array('tid' => $tid)); return $r; } function thread_tid_count() { $n = thread_tid__count(); return $n; } // 统计用户主题数 大数量下严谨使用非主键统计 function thread_uid_count($uid) { $n = thread_tid__count(array('uid' => $uid)); return $n; } // 统计栏目主题数 大数量下严谨使用非主键统计 function thread_fid_count($fid) { $n = thread_tid__count(array('fid' => $fid)); return $n; } ?>javascript - Mocks broken after updating to Jest 26 - Stack Overflow
最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

javascript - Mocks broken after updating to Jest 26 - Stack Overflow

programmeradmin3浏览0评论

I just updated react-scripts to 4.0 which includes Jest@26 and some acpanying test packages here's the package.json diff:

After upgrading, some Jest mocks have begun to fail. It seems like the mocked return value is just undefined? Am I missing something? Here's one of the failing mocks

import useFetch from "use-http";

jest.mock("use-http", () => ({
    __esModule: true,
    default: jest.fn()
}));

describe("the user context", () => {
    beforeAll(() => {
        useFetch.mockReturnValue({
            get: async () => Promise.resolve({ foo: 666 }),
            response: { ok: true }
        });
    });

Tests that try to utilize the 'get' method fail with:

TypeError: Cannot destructure property 'get' of '(0 , _useHttp.default)(...)' as it is undefined.

And another that isn't default, doesn't import the package for one-time mocks:

jest.mock("_hooks", () => ({
    useBaseUrls: jest.fn().mockReturnValue({
        app: "bar"
    })
}));

Tests that access the 'app' property throw TypeError: Cannot read property 'app' of undefined

I just updated react-scripts to 4.0 which includes Jest@26 and some acpanying test packages here's the package.json diff:

After upgrading, some Jest mocks have begun to fail. It seems like the mocked return value is just undefined? Am I missing something? Here's one of the failing mocks

import useFetch from "use-http";

jest.mock("use-http", () => ({
    __esModule: true,
    default: jest.fn()
}));

describe("the user context", () => {
    beforeAll(() => {
        useFetch.mockReturnValue({
            get: async () => Promise.resolve({ foo: 666 }),
            response: { ok: true }
        });
    });

Tests that try to utilize the 'get' method fail with:

TypeError: Cannot destructure property 'get' of '(0 , _useHttp.default)(...)' as it is undefined.

And another that isn't default, doesn't import the package for one-time mocks:

jest.mock("_hooks", () => ({
    useBaseUrls: jest.fn().mockReturnValue({
        app: "bar"
    })
}));

Tests that access the 'app' property throw TypeError: Cannot read property 'app' of undefined

Share Improve this question asked Dec 18, 2020 at 20:55 eejeej 1131 silver badge7 bronze badges 3
  • It seems like the mocked return value is just undefined? Am I missing something? - yes, it's undefined, because jest.fn() doesn't return anything. It's not workable regardless of Jest 26, did you try to fix this? Tests that access the 'app' property throw - please, provide stackoverflow./help/mcve that can reproduce the problem. – Estus Flask Commented Dec 19, 2020 at 8:40
  • These tests were functional prior to upgrading -- for the first example note the mocked return value of jest.fn() before each test. For the second, a return value is defined explicitly inline. Neither test expects jest.fn() to return anything, just to enable mocking. – eej Commented Dec 23, 2020 at 17:00
  • Double check that you don't have resetMocks config option or jest.resetAllMocks anywhere, initial mocks are naturally inpatible with them. – Estus Flask Commented Dec 24, 2020 at 7:42
Add a ment  | 

1 Answer 1

Reset to default 20

Jest 26 changed the default behavior of resetMocks to true, which resets mock state before each test.

You can revert to the prior behavior by disabling resetMocks in package.json

  "jest": {
    "resetMocks": false
  }

A discussion to change the default back again is currently an open issue on their Github: https://github./facebook/create-react-app/issues/9935

发布评论

评论列表(0)

  1. 暂无评论