您好,我正在尝试测试使用Material-UI创建的Slider组件,但是我无法将测试用于p enter link description here ass。我想使用fireEvent
和@testing-library/react
测试值更改。我一直在关注此帖子以正确查询DOM,但无法获取正确的DOM节点。
谢谢。
<Slider />
组件
// @format
// @flow
import * as React from "react";
import styled from "styled-components";
import { Slider as MaterialUISlider } from "@material-ui/core";
import { withStyles, makeStyles } from "@material-ui/core/styles";
import { priceRange } from "../../../domain/Search/PriceRange/priceRange";
const Wrapper = styled.div`
width: 93%;
display: inline-block;
margin-left: 0.5em;
margin-right: 0.5em;
margin-bottom: 0.5em;
`;
// ommited code pertaining props and styles for simplicity
function Slider(props: SliderProps) {
const initialState = [1, 100];
const [value, setValue] = React.useState(initialState);
function onHandleChangeCommitted(e, latestValue) {
e.preventDefault();
const { onUpdate } = props;
const newPriceRange = priceRange(latestValue);
onUpdate(newPriceRange);
}
function onHandleChange(e, newValue) {
e.preventDefault();
setValue(newValue);
}
return (
<Wrapper
aria-label="range-slider"
>
<SliderWithStyles
aria-labelledby="range-slider"
defaultValue={initialState}
// getAriaLabel={index =>
// index === 0 ? "Minimum Price" : "Maximum Price"
// }
getAriaValueText={valueText}
onChange={onHandleChange}
onChangeCommitted={onHandleChangeCommitted}
valueLabelDisplay="auto"
value={value}
/>
</Wrapper>
);
}
export default Slider;
Slider.test.js
// @flow
import React from "react";
import { cleanup,
render,
getAllByAltText,
fireEvent,
waitForElement } from "@testing-library/react";
import "@testing-library/jest-dom/extend-expect";
import Slider from "../Slider";
afterEach(cleanup);
describe("<Slider /> specs", () => {
// [NOTE]: Works, but maybe a better way to do it ?
xdescribe("<Slider /> component aria-label", () => {
it("renders without crashing", () => {
const { container } = render(<Slider />);
expect(container.firstChild).toBeInTheDocument();
});
});
// [ASK]: How to test the event handlers with fireEvent.
describe("<Slider /> props", () => {
it("display a initial min value of '1'", () => {
const renderResult = render(<Slider />);
// TODO
});
it("display a initial max value of '100'", () => {
const renderResult = render(<Slider />);
// TODO
});
xit("display to values via the onHandleChangeCommitted event when dragging stop", () => {
const renderResult = render(<Slider />);
console.log(renderResult)
// fireEvent.change(renderResult.getByText("1"))
// expect(onChange).toHaveBeenCalled(0);
});
// [NOTE]: Does not work, returns undefined
xit("display to values via the onHandleChange event when dragging stop", () => {
const renderResult = render(<Slider />);
console.log(renderResult.container);
const spanNodeWithAriaAttribute = renderResult.container.firstChild.getElementsByTagName("span")[0].getAttribute('aria-label')
expect(spanNodeWithAriaAttribute).toBe(/range-slider/)
});
});
// [ASK]: Works, but a snapshot is an overkill a better way of doing this ?
xdescribe("<Slider /> snapshot", () => {
it("renders without crashing", () => {
const { container } = render(<Slider />);
expect(container.firstChild).toMatchSnapshot();
});
});
});
答案 0 :(得分:3)
战斗了几个小时后,我得以解决与测试MUI滑块有关的案例
这实际上取决于您需要如何测试,在我的情况下,我必须检查使用marks
滑块道具单击标记后标签文本的内容是否已更改。
问题
1)slider
组件根据元素getBoundingClientRect
和MouseEvent
2)如何查询slider
并触发事件。
3)JSDOM对读取元素实际高度和宽度的限制导致了问题1
解决方案
1)模拟getBoundingClientRect
也应该解决3号问题
2)将测试ID添加到滑块并使用use fireEvent.mouseDown(contaner, {....})
const sliderLabel = screen.getByText("Default text that the user should see")
// add data-testid to slider
const sliderInput = screen.getByTestId("slider")
// mock the getBoundingClientRect
sliderInput.getBoundingClientRect = jest.fn(() => {
return {
bottom: 286.22918701171875,
height: 28,
left: 19.572917938232422,
right: 583.0937919616699,
top: 258.22918701171875,
width: 563.5208740234375,
x: 19.572917938232422,
y: 258.22918701171875,
}
})
expect(sliderInput).toBeInTheDocument()
expect(sliderLabel).toHaveTextContent("Default text that the user should see")
await fireEvent.mouseDown(sliderInput, { clientX: 162, clientY: 302 })
expect(sliderLabel).toHaveTextContent(
"New text that the user should see"
)
答案 1 :(得分:1)
我将上述解决方案变成了简单的(打字稿)助手
export class Slider {
private static height = 10
// For simplicity pretend that slider's width is 100
private static width = 100
private static getBoundingClientRectMock() {
return {
bottom: Slider.height,
height: Slider.height,
left: 0,
right: Slider.width,
top: 0,
width: Slider.width,
x: 0,
y: 0,
} as DOMRect
}
static change(element: HTMLElement, value: number, min: number = 0, max: number = 100) {
const getBoundingClientRect = element.getBoundingClientRect
element.getBoundingClientRect = Slider.getBoundingClientRectMock
fireEvent.mouseDown(
element,
{
clientX: ((value - min) / (max - min)) * Slider.width,
clientY: Slider.height
}
)
element.getBoundingClientRect = getBoundingClientRect
}
}
用法:
Slider.change(getByTestId('mySlider'), 40) // When min=0, max=100 (default)
// Otherwise
Slider.change(getByTestId('mySlider'), 4, 0, 5) // Sets 4 with scale set to 0-5
答案 2 :(得分:0)
我建议不要为自定义组件编写测试,并认为该组件适用于我们所有情况。
通读this article了解更多详细信息。他们提到了如何为包装react-select
的组件编写单元测试。
我采用了类似的方法,并为我的第三方滑块组件编写了一个模拟文件。
在setupTests.js
中:
jest.mock('@material-ui/core/Slider', () => (props) => {
const { id, name, min, max, onChange, testid } = props;
return (
<input
data-testid={testid}
type="range"
id={id}
name={name}
min={min}
max={max}
onChange={(event) => onChange(event.target.value)}
/>
);
});
借助此模拟,您可以像这样简单地在测试中触发更改事件:
fireEvent.change(getByTestId(`slider`), 25);
请确保将正确的testid
作为对SliderWithStyles
组件的支持
答案 3 :(得分:0)
以 @rehman_00001's answer 为基础,我为组件创建了一个文件模拟。我是用 TypeScript 写的,但如果没有类型,它应该也能正常工作。
__mocks__/@material-ui/core/Slider.tsx
import { SliderTypeMap } from '@material-ui/core';
import React from 'react';
export default function Slider(props: SliderTypeMap['props']): JSX.Element {
const { onChange, ...others } = props;
return (
<input
type="range"
onChange={(event) => {
onChange && onChange(event, parseInt(event.target.value));
}}
{...(others as any)}
/>
);
}
现在,Material UI <Slider/>
组件的每次使用都将在测试期间呈现为一个简单的 HTML <input/>
元素,使用 Jest 和 react-testing-library
更容易使用。
{...(others as any)}
是一个 hack,它让我不必担心确保原始组件的每个可能的 prop 都得到正确处理。根据您所依赖的 Slider
道具,您可能需要在解构期间提取额外的道具,以便您可以将它们正确地转换为对普通 <input/>
元素有意义的内容。 See this page in the Material UI docs 了解每个可能属性的信息。