如何使用Jest和Enzyme在React(Native)中为父组件提供功能来测试组件?

时间:2018-10-05 12:46:43

标签: typescript react-native jestjs enzyme formik

我正在构建一个React Native应用程序,并且正在使用Jest和Enzyme进行单元测试。此外,我正在使用TypeScript。

我使用Formik构建以下表单。

import strings from "./strings";
import styles from "./styles";
import { strings as loginStrings } from "../../screens/Login";
import { Formik, FormikActions, FormikProps } from "formik";
import React, { Component } from "react";
import { View } from "react-native";
import { Button, Input } from "react-native-elements";
import { NavigationScreenProp } from "react-navigation";
import { object as yupObject, string as yupString } from "yup";

export interface FormValues {
  email: string;
  password: string;
}

export interface Props {
  navigation: NavigationScreenProp<any, any>;
}

export default class LoginForm extends Component<Props, object> {
  handleSubmit = (values: FormValues, formikBag: FormikActions<FormValues>) => {
    // ... api calls and stuff
  };

  renderForm = ({
    values,
    handleSubmit,
    setFieldValue,
    touched,
    errors,
    setFieldTouched,
    isValid,
    isSubmitting
  }: FormikProps<FormValues>) => (
    <View style={styles.container}>
      // ... two inputs and a button
    </View>
  );

  render() {
    return (
      <Formik
        initialValues={{ email: "", password: "" }}
        onSubmit={(values: FormValues, formikBag: FormikActions<FormValues>) =>
          this.handleSubmit(values, formikBag)
        }
        validationSchema={yupObject().shape({
          email: yupString()
            .email(strings.invalidEmailFormat)
            .required(strings.emailRequired),
          password: yupString()
            .min(8, strings.passwordMinLength)
            .required(strings.passwordRequired)
        })}
        render={(formikBag: FormikProps<FormValues>) => this.renderForm(formikBag)}
      />
    );
  }
}

如您所见,它只是一种简单的形式。现在,我想测试<Formik />组件是否已通过renderForm()handleSubmit,因此我编写了以下测试:

it("should be passed the component's handleSubmit function for onSubmit", () => {
  expect(wrapper.find("Formik").prop("onSubmit")).toEqual(
    (values: FormValues, formikBag: FormikActions<FormValues>) =>
      wrapper.instance().handleSubmit(values, formikBag)
  );
});

renderForm()相同。不幸的是,这引发了错误:

● LoginForm › rendering › should be passed the component's handleSubmit function for onSubmit

    expect(received).toEqual(expected)

    Expected value to equal:
      [Function anonymous]
    Received:
      [Function onSubmit]

    Difference:

    - Expected
    + Received

    - [Function anonymous]
    + [Function onSubmit]

      28 |
      29 |     it("should be passed the component's handleSubmit function for onSubmit", () => {
    > 30 |       expect(wrapper.find("Formik").prop("onSubmit")).toEqual(
         |                                                       ^
      31 |         (values: FormValues, formikBag: FormikActions<FormValues>) =>
      32 |           wrapper.instance().handleSubmit(values, formikBag)
      33 |       );

因此,我不确定如何正确测试该功能是否已传递到组件。怎么会这样?

我发现有一种工作方式,就是这样将函数传递给<Formik />

onSubmit={this.handleSubmit}
render={this.renderForm}

然后:

expect(wrapper.find("Formik").prop("onSubmit)).toEqual(wrapper.instance().onSubmit)

问题是,过去,当我只是像这样传递函数时,我在单元测试中遇到了麻烦。同样通过这种方式,我可以松开TypeScript的类型。有没有一种方法可以使我的最初尝试奏效?”

1 个答案:

答案 0 :(得分:1)

定义匿名函数时,实际上是在创建一个新函数,因此它将永远不等于渲染器内部使用的那个函数。您可以选择将其存储为对象的一部分,并检查引用是否相等(这是您建议的工作方式):

expect(wrapper.find("Formik").prop("onSubmit)).toEqual(wrapper.instance().onSubmit)

另一种选择是模拟handleSubmit,并使您的测试检查单击handleSubmit按钮时是否调用Submit,在我看来这是更合理的测试。

// set handleSubmit to our fake mock function
wrapper.instance().handleSubmit = jest.fn();
wrapper.update();
// Here you need to simulate a click to submit form
// I don't know how your input looks like
// but it will be similar to
inp.simulate('click')
// expect our mock function to have been called at least once
expect(wrapper.instance().handleSubmit).toHaveBeenCalledTimes(1);