你必须使用querybytestd而不是getbytestd。

这里是一个代码示例，我想测试是否组件与“汽车”id不存在。

 describe('And there is no car', () => {
  it('Should not display car mark', () => {
    const props = {
      ...defaultProps,
      base: null,
    }
    const { queryByTestId } = render(
      <IntlProvider locale="fr" messages={fr}>
        <CarContainer{...props} />
      </IntlProvider>,
    );
    expect(queryByTestId(/car/)).toBeNull();
  });
});

你必须使用querybytestd而不是getbytestd。

这里是一个代码示例，我想测试是否组件与“汽车”id不存在。

 describe('And there is no car', () => {
  it('Should not display car mark', () => {
    const props = {
      ...defaultProps,
      base: null,
    }
    const { queryByTestId } = render(
      <IntlProvider locale="fr" messages={fr}>
        <CarContainer{...props} />
      </IntlProvider>,
    );
    expect(queryByTestId(/car/)).toBeNull();
  });
});

另一个解决方案:您也可以使用try/catch块

expect.assertions(1)
try {
    // if the element is found, the following expect will fail the test
    expect(getByTestId('your-test-id')).not.toBeVisible();
} catch (error) {
    // otherwise, the expect will throw, and the following expect will pass the test
    expect(true).toBeTruthy();
}

来自DOM测试库文档-出现和消失

Asserting elements are not present The standard getBy methods throw an error when they can't find an element, so if you want to make an assertion that an element is not present in the DOM, you can use queryBy APIs instead: const submitButton = screen.queryByText('submit') expect(submitButton).toBeNull() // it doesn't exist The queryAll APIs version return an array of matching nodes. The length of the array can be useful for assertions after elements are added or removed from the DOM. const submitButtons = screen.queryAllByText('submit') expect(submitButtons).toHaveLength(2) // expect 2 elements not.toBeInTheDocument The jest-dom utility library provides the .toBeInTheDocument() matcher, which can be used to assert that an element is in the body of the document, or not. This can be more meaningful than asserting a query result is null. import '@testing-library/jest-dom/extend-expect' // use `queryBy` to avoid throwing an error with `getBy` const submitButton = screen.queryByText('submit') expect(submitButton).not.toBeInTheDocument()

对我来说(如果你想使用getbytestd):

expect(() => getByTestId('time-label')).toThrow()

使用queryBy / queryAllBy。

如您所说，如果没有找到任何东西，getBy*和getAllBy*将抛出一个错误。

然而，等效的方法queryBy*和queryAllBy*返回null或[]:

queryBy queryBy*查询返回查询的第一个匹配节点，如果没有匹配的元素则返回null。这对于断言不存在的元素非常有用。如果找到多个匹配项，则会抛出(使用queryAllBy代替)。 queryAllBy queryAllBy*查询返回一个包含所有匹配节点的数组，如果没有元素匹配则返回一个空数组([])。

https://testing-library.com/docs/dom-testing-library/api-queries#queryby

因此，对于您提到的特定两个查询，您将使用queryByText和querybytestd，但它们适用于所有查询，而不仅仅是这两个查询。