Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/features/logging-for-object-resolution.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ import { version } from '../data.json';
# Logging for Object Resolution

AutoParams provides detailed logging capabilities that help you understand how objects are being resolved during test execution. To enable logging, apply the `@LogResolution` annotation to your test method alongside `@AutoParams`. When enabled, the resolution log is printed to standard output during test execution, making it easy to trace how each value is generated.

<br/>
For example, resolving a `User` class produces a detailed trace. Given the following class:

<JavaKotlinCodeBlock>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ import { version } from '../data.json';
# 개체 해결에 대한 로깅

AutoParams는 테스트 실행 중 개체가 어떻게 해결되는지 이해하는 데 도움이 되는 자세한 로그를 제공합니다. 로깅을 활성화하려면 테스트 메서드에 `@LogResolution` 애노테이션을 `@AutoParams`와 함께 적용합니다. 활성화된 경우, 테스트 실행 중 표준 출력으로 출력되어 각 값이 어떻게 생성되는지 쉽게 추적할 수 있습니다.

<br/>
`User` 클래스의 자세한 추적 정보가 생성되는 예를 살펴보겠습니다. 다음 클래스가 주어졌을 때,

<JavaKotlinCodeBlock>
Expand Down
6 changes: 3 additions & 3 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@
"typecheck": "tsc"
},
"dependencies": {
"@docusaurus/core": "^3.8.0",
"@docusaurus/faster": "^3.8.0",
"@docusaurus/preset-classic": "^3.8.0",
"@docusaurus/core": "^3.8.1",
"@docusaurus/faster": "^3.8.1",
"@docusaurus/preset-classic": "^3.8.1",
"@mdx-js/react": "^3.0.0",
"clsx": "^2.0.0",
"prism-react-renderer": "^2.3.0",
Expand Down
Loading