-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: notification을 타입계층으로 리팩터링 #929
base: develop
Are you sure you want to change the base?
Conversation
Test Results 62 files 62 suites 13s ⏱️ Results for commit deb422d. |
📝 Test Coverage Report
|
@@ -195,5 +204,46 @@ void returnMissing_When_isMissing_Mate() { | |||
assertThat(mateEtaResponses.mateEtas().get(1).status()).isNotEqualTo(EtaStatus.MISSING); | |||
} | |||
} | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
리팩터링으로 인해 findAllMeetingLogsOrderOfEntryAndDepartureNotification()를 대체할 테스트를 인수 테스트로 추가하였습니다.
import org.junit.jupiter.api.Test; | ||
import org.mockito.Mockito; | ||
|
||
class DepartureReminderTest { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
발송 시점이 현재 시점보다 이른 경우, 즉시 발송한다는 책임은 NotificatinService가 아닌 DepartureReminder의 내부 로직으로 캡슐화되어 테스트를 이전했습니다.
🚩 연관 이슈
close #926
📝 작업 내용
🏞️ 스크린샷 (선택)
🗣️ 리뷰 요구사항 (선택)
❌ 아직 리뷰하지 말아주세요 -> PR 관련 노션 페이지 작성 예정