Skip to content

@JsonFormat 추가

@JsonFormat 추가 #48

Triggered via pull request October 19, 2023 08:38
Status Success
Total duration 18s
Artifacts
New pr to repo
7s
New pr to repo
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 6 warnings
NoticeQueryControllerTest$GetNotice.정상적인 요청이라면 200 응답을 반환한다.: NoticeQueryControllerTest$GetNotice#L172
java.lang.AssertionError: Expecting actual: NoticeResponse[id=1, title=title, bannerTitle=bannerTitle, bannerSubtitle=bannerSubtitle, content=content, deadline=2023-10-20T08:41, createdAt=2023-10-19T08:41] to be equal to: NoticeResponse[id=1, title=title, bannerTitle=bannerTitle, bannerSubtitle=bannerSubtitle, content=content, deadline=2023-10-20T08:41:03.934829495, createdAt=2023-10-19T08:41:03.934845595] when recursively comparing field by field, but found the following 2 differences: field/property 'createdAt' differ: - actual value : 2023-10-19T08:41 (java.time.LocalDateTime) - expected value: 2023-10-19T08:41:03.934845595 (java.time.LocalDateTime) field/property 'deadline' differ: - actual value : 2023-10-20T08:41 (java.time.LocalDateTime) - expected value: 2023-10-20T08:41:03.934829495 (java.time.LocalDateTime) The recursive comparison was performed with this configuration: - no overridden equals methods were used in the comparison (except for java types) - these types were compared with the following comparators: - java.lang.Double -> DoubleComparator[precision=1.0E-15] - java.lang.Float -> FloatComparator[precision=1.0E-6] - java.nio.file.Path -> lexicographic comparator (Path natural order) - actual and expected objects and their fields were compared field by field recursively even if they were not of the same type, this allows for example to compare a Person to a PersonDto (call strictTypeChecking(true) to change that behavior). - the introspection strategy used was: DefaultRecursiveComparisonIntrospectionStrategy
NoticeQueryControllerTest$GetNotices.정상적인 요청이라면 200 응답을 반환한다.: NoticeQueryControllerTest$GetNotices#L107
java.lang.AssertionError: Expecting actual: NoticePageResponse[totalPageNumber=1, currentPageNumber=0, notices=[NoticeResponse[id=1, title=title, bannerTitle=bannerTitle, bannerSubtitle=bannerSubtitle, content=content, deadline=2023-10-20T08:41, createdAt=2023-10-19T08:41]]] to be equal to: NoticePageResponse[totalPageNumber=1, currentPageNumber=0, notices=[NoticeResponse[id=1, title=title, bannerTitle=bannerTitle, bannerSubtitle=bannerSubtitle, content=content, deadline=2023-10-20T08:41:03.995087548, createdAt=2023-10-19T08:41:03.995109049]]] when recursively comparing field by field, but found the following 2 differences: field/property 'notices[0].createdAt' differ: - actual value : 2023-10-19T08:41 (java.time.LocalDateTime) - expected value: 2023-10-19T08:41:03.995109049 (java.time.LocalDateTime) field/property 'notices[0].deadline' differ: - actual value : 2023-10-20T08:41 (java.time.LocalDateTime) - expected value: 2023-10-20T08:41:03.995087548 (java.time.LocalDateTime) The recursive comparison was performed with this configuration: - no overridden equals methods were used in the comparison (except for java types) - these types were compared with the following comparators: - java.lang.Double -> DoubleComparator[precision=1.0E-15] - java.lang.Float -> FloatComparator[precision=1.0E-6] - java.nio.file.Path -> lexicographic comparator (Path natural order) - actual and expected objects and their fields were compared field by field recursively even if they were not of the same type, this allows for example to compare a Person to a PersonDto (call strictTypeChecking(true) to change that behavior). - the introspection strategy used was: DefaultRecursiveComparisonIntrospectionStrategy
NoticeQueryControllerTest.배너 공지사항 조회에 성공하면 200 응답을 반환한다.: backend/src/test/java/com/votogether/domain/notice/controller/NoticeQueryControllerTest.java#L71
java.lang.AssertionError: Expecting actual: NoticeResponse[id=1, title=title, bannerTitle=bannerTitle, bannerSubtitle=bannerSubtitle, content=content, deadline=2023-10-20T08:41, createdAt=2023-10-19T08:41] to be equal to: NoticeResponse[id=1, title=title, bannerTitle=bannerTitle, bannerSubtitle=bannerSubtitle, content=content, deadline=2023-10-20T08:41:03.687384879, createdAt=2023-10-19T08:41:03.688127090] when recursively comparing field by field, but found the following 2 differences: field/property 'createdAt' differ: - actual value : 2023-10-19T08:41 (java.time.LocalDateTime) - expected value: 2023-10-19T08:41:03.688127090 (java.time.LocalDateTime) field/property 'deadline' differ: - actual value : 2023-10-20T08:41 (java.time.LocalDateTime) - expected value: 2023-10-20T08:41:03.687384879 (java.time.LocalDateTime) The recursive comparison was performed with this configuration: - no overridden equals methods were used in the comparison (except for java types) - these types were compared with the following comparators: - java.lang.Double -> DoubleComparator[precision=1.0E-15] - java.lang.Float -> FloatComparator[precision=1.0E-6] - java.nio.file.Path -> lexicographic comparator (Path natural order) - actual and expected objects and their fields were compared field by field recursively even if they were not of the same type, this allows for example to compare a Person to a PersonDto (call strictTypeChecking(true) to change that behavior). - the introspection strategy used was: DefaultRecursiveComparisonIntrospectionStrategy
New pr to repo
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
New pr to repo
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
New pr to repo
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
정상적인 요청이라면 200 응답을 반환한다. (com.votogether.domain.notice.controller.NoticeQueryControllerTest$GetNotices) failed: com.votogether.domain.notice.controller.NoticeQueryControllerTest$GetNotices#L0
backend/build/test-results/test/TEST-com.votogether.domain.notice.controller.NoticeQueryControllerTest$GetNotices.xml [took 0s]
정상적인 요청이라면 200 응답을 반환한다. (com.votogether.domain.notice.controller.NoticeQueryControllerTest$GetNotice) failed: com.votogether.domain.notice.controller.NoticeQueryControllerTest$GetNotice#L0
backend/build/test-results/test/TEST-com.votogether.domain.notice.controller.NoticeQueryControllerTest$GetNotice.xml [took 0s]