Jest automock 不适用于模块

Rafał Wrzeszcz

我在为我的模块运行 Jest 测试时遇到了麻烦 - 我有一个简单的入口点类:

import { Callback, CloudFrontRequestEvent, Context, Handler } from "aws-lambda";

import { CloudFrontHandler } from "./CloudFrontHandler";
import { OriginClient } from "./OriginClient";
import { ResponseRenderer } from "./ResponseRenderer";
import { TemplateRenderer } from "./TemplateRenderer";

export class LambdaHandler {
    private readonly renderer: TemplateRenderer;

    constructor(renderer: TemplateRenderer) {
        this.renderer = renderer;
    }

    public handle: Handler = (event: CloudFrontRequestEvent, _: Context, callback: Callback): void => {
        console.log(new CloudFrontHandler(null, null)); // <- just an empty object here! CloudFrontHandler {}
        console.log(new OriginClient(null)); // <- properly mocked
        console.log(new ResponseRenderer(null, null)); // <- properly mocked
        new CloudFrontHandler(
            new OriginClient(event.Records[0].cf.request),
            new ResponseRenderer(callback, this.renderer),
        )
            .handle(); // <- because CloudFrontHandler is not mocked, an error occurs here
    }
}

无论出于何种原因,CloudFrontHandler类都不会被嘲笑(OriginClient并且ResponseRenderer被正确地自动嘲笑)。以下是我的测试课:

import "jest";
import { Callback, CloudFrontRequest, CloudFrontRequestEvent } from "aws-lambda";
import { mocked } from "ts-jest/utils";
import { LambdaHandler, TemplateRenderer } from "../../../main/nodejs";

import { CloudFrontHandler } from "../../../main/nodejs/edge/CloudFrontHandler";
import { OriginClient } from "../../../main/nodejs/edge/OriginClient";
import { ResponseRenderer } from "../../../main/nodejs/edge/ResponseRenderer";

jest.mock("../../../main/nodejs/edge/CloudFrontHandler");
jest.mock("../../../main/nodejs/edge/OriginClient");
jest.mock("../../../main/nodejs/edge/ResponseRenderer");

const MockedCloudFrontHandler = mocked(CloudFrontHandler);
const MockedOriginClient = mocked(OriginClient);
const MockedResponseRenderer = mocked(ResponseRenderer);

describe("LambdaHandler", (): void => {
        it("should handle CloudFront request", (): void => {
                const templateRenderer: TemplateRenderer = {} as TemplateRenderer;
                const callback: Callback = jest.fn() as Callback;
                const request: CloudFrontRequest = {} as CloudFrontRequest;
                const event: CloudFrontRequestEvent = {
                    Records: [
                        {
                            cf: {
                                request: request,
                            },
                        },
                    ],
                } as CloudFrontRequestEvent;

                let handler: LambdaHandler = new LambdaHandler(templateRenderer);
                handler.handle(event, null, callback)
                // todo

                expect(MockedCloudFrontHandler).toHaveBeenCalledTimes(1);
                expect(MockedOriginClient).toHaveBeenCalledTimes(1);
                expect(MockedResponseRenderer).toHaveBeenCalledTimes(1);
        });
});

(我分别保留源文件和测试文件,因此所有这些src/main src/test路径)

为什么 Jest 不会嘲笑这个模块类?

-编辑-

错误信息是:

TypeError: (intermediate value).handle is not a function
Rafał Wrzeszcz

我的问题下的评论指出了根本原因 - 这里的问题是,这CloudFrontHandler.handle是一个箭头函数,TypeScript 将其转换为构造函数中分配的属性。由于构造函数是自动模拟的,因此未分配该函数。为该.handle()方法创建手动模拟解决了这个问题。

本文收集自互联网,转载请注明来源。

如有侵权,请联系 [email protected] 删除。

编辑于
0

我来说两句

0 条评论
登录 后参与评论

相关文章