Skip to content
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

test: 1차 모집시 멤버십 생성 후 실제 가입하지 않은 경우 2차 모집 멤버십 접수 테스트 추가 #744

Merged
merged 1 commit into from
Sep 3, 2024

Conversation

Sangwook02
Copy link
Member

@Sangwook02 Sangwook02 commented Sep 3, 2024

🌱 관련 이슈

📌 작업 내용 및 특이사항

  • 지난번에 todo로 남겨뒀던 부분 테스트 작성했습니다.

📝 참고사항

📚 기타

Summary by CodeRabbit

  • 테스트
    • 멤버십 신청 프로세스의 두 번째 모집 라운드에서의 성공적인 신청을 검증하는 새로운 테스트 케이스 추가.

@Sangwook02 Sangwook02 self-assigned this Sep 3, 2024
@Sangwook02 Sangwook02 requested a review from a team as a code owner September 3, 2024 04:42
Copy link

coderabbitai bot commented Sep 3, 2024

Walkthrough

변경 사항은 MembershipServiceTest 클래스에 새로운 테스트 케이스를 추가하여 모집 라운드 중 멤버십 신청 기능을 검증합니다. 새로 추가된 테스트 메서드는 첫 번째 모집 라운드에서 정회원 가입 조건을 충족하지 못한 경우에도 두 번째 모집 라운드에서 멤버십 신청이 성공적으로 이루어질 수 있음을 확인합니다. 이로 인해 멤버십 신청 로직의 테스트 커버리지가 확장됩니다.

Changes

파일 경로 변경 요약
src/test/java/com/gdschongik/gdsc/domain/membership/application/MembershipServiceTest.java 새로운 테스트 메서드 추가: 멤버십을_1차모집시_생성했지만_정회원_가입조건을_만족하지_않았다면_2차모집에서_멤버십_가입신청에_성공한다

Assessment against linked issues

Objective Addressed Explanation
1차 모집시 멤버십 생성 후 실제 가입하지 않은 경우 테스트 추가 (#729)

🐰 새로운 테스트가 생겼네,
모집 라운드의 기쁨을 전해,
조건을 못 맞춰도 괜찮아,
두 번째 기회가 기다려,
멤버십 신청, 성공하길 바라! 🌟


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Tip

Early access features: enabled

We are currently testing the following features in early access:

  • Anthropic claude-3-5-sonnet for code reviews: Anthropic claims that the new Claude model has stronger code understanding and code generation capabilities than their previous models. Note: Our default code review model was also updated late last week. Please compare the quality of the reviews between the two models by toggling the early access feature.

Note:

  • You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.
  • Please join our Discord Community to provide feedback and report issues on the discussion post.

Copy link

github-actions bot commented Sep 3, 2024

Job Summary for Gradle

Check Style and Test to Develop :: build-test
Gradle Root Project Requested Tasks Gradle Version Build Outcome Build Scan®
gdsc check 8.5 Build Scan published

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 171694c and d7d768a.

Files selected for processing (1)
  • src/test/java/com/gdschongik/gdsc/domain/membership/application/MembershipServiceTest.java (2 hunks)
Additional comments not posted (1)
src/test/java/com/gdschongik/gdsc/domain/membership/application/MembershipServiceTest.java (1)

5-5: 새로운 임포트 추가 승인

새로운 테스트 메서드에 필요한 클래스들을 적절히 임포트하였습니다.

Also applies to: 9-9, 14-14, 17-17

Comment on lines +45 to +74
@Test
void 멤버십을_1차모집시_생성했지만_정회원_가입조건을_만족하지_않았다면_2차모집에서_멤버십_가입신청에_성공한다() {
// given
createMember();
logoutAndReloginAs(1L, ASSOCIATE);

RecruitmentRound firstRound = createRecruitmentRound(
RECRUITMENT_ROUND_NAME,
LocalDateTime.now().minusDays(5),
LocalDateTime.now().plusDays(1),
ACADEMIC_YEAR,
SEMESTER_TYPE,
ROUND_TYPE,
Money.from(20000L));

RecruitmentRound secondRound = createRecruitmentRound(
RECRUITMENT_ROUND_NAME,
LocalDateTime.now().minusDays(1),
LocalDateTime.now().plusDays(1),
ACADEMIC_YEAR,
SEMESTER_TYPE,
RoundType.SECOND,
Money.from(20000L));

// when & then
membershipService.submitMembership(firstRound.getId());

assertThatCode(() -> membershipService.submitMembership(secondRound.getId()))
.doesNotThrowAnyException();
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

테스트 메서드 개선 제안

새로운 테스트 메서드가 시나리오를 잘 커버하고 있습니다. 다음과 같은 개선 사항을 제안합니다:

  1. 첫 번째 라운드 제출에 대한 검증을 추가하세요.

첫 번째 라운드 제출 후 예외가 발생하지 않는지 확인하는 assertion을 추가하세요. 예:

assertThatCode(() -> membershipService.submitMembership(firstRound.getId()))
        .doesNotThrowAnyException();
  1. 각 제출 후 멤버십 상태를 확인하세요.

각 라운드 제출 후 멤버십 상태를 확인하는 assertion을 추가하세요. 예:

Membership firstRoundMembership = membershipRepository.findByMemberIdAndRecruitmentRoundId(1L, firstRound.getId()).orElseThrow();
assertThat(firstRoundMembership.getStatus()).isEqualTo(MembershipStatus.PENDING);

Membership secondRoundMembership = membershipRepository.findByMemberIdAndRecruitmentRoundId(1L, secondRound.getId()).orElseThrow();
assertThat(secondRoundMembership.getStatus()).isEqualTo(MembershipStatus.PENDING);
  1. 테스트 시나리오에 대한 영문 설명을 추가하세요.

메서드 이름 위에 영문으로 테스트 시나리오를 설명하는 주석을 추가하세요. 예:

/**
 * Test case: Successful membership application in the second recruitment round
 * Scenario: A member created a membership in the first round but did not meet the full membership conditions.
 * Expected: The member should be able to successfully apply for membership in the second round.
 */

이러한 개선사항들은 테스트의 가독성과 유지보수성을 향상시킬 것입니다.

Copy link
Member

@AlmondBreez3 AlmondBreez3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Copy link
Contributor

@seulgi99 seulgi99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Sangwook02 Sangwook02 merged commit 634ebdd into develop Sep 3, 2024
1 check passed
@Sangwook02 Sangwook02 deleted the test/729-unstatisfied-membership branch September 3, 2024 06:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

✅ 1차 모집시 멤버십 생성 후 실제 가입하지 않은 경우 테스트 추가
3 participants