新增: - backend/venv/ - Python 虚拟环境 - backend/start.sh - 启动脚本(使用虚拟环境) - backend/requirements.txt - 依赖列表 - .gitignore - 忽略虚拟环境和缓存文件 说明: - 每个项目使用独立虚拟环境 - 避免依赖冲突 - 启动脚本自动创建和激活虚拟环境
33 lines
998 B
Markdown
33 lines
998 B
Markdown
# Suggest using `toBeCalledWith()` or `toHaveBeenCalledWith()` (`prefer-called-with`)
|
|
|
|
The `toBeCalled()` matcher is used to assert that a mock function has been
|
|
called one or more times, without checking the arguments passed. The assertion
|
|
is stronger when arguments are also validated using the `toBeCalledWith()`
|
|
matcher. When some arguments are difficult to check, using generic match like
|
|
`expect.anything()` at least enforces number and position of arguments.
|
|
|
|
This rule warns if the form without argument checking is used, except for `.not`
|
|
enforcing a function has never been called.
|
|
|
|
## Rule details
|
|
|
|
The following patterns are warnings:
|
|
|
|
```js
|
|
expect(someFunction).toBeCalled();
|
|
|
|
expect(someFunction).toHaveBeenCalled();
|
|
```
|
|
|
|
The following patterns are not warnings:
|
|
|
|
```js
|
|
expect(noArgsFunction).toBeCalledWith();
|
|
|
|
expect(roughArgsFunction).toBeCalledWith(expect.anything(), expect.any(Date));
|
|
|
|
expect(anyArgsFunction).toBeCalledTimes(1);
|
|
|
|
expect(uncalledFunction).not.toBeCalled();
|
|
```
|