dozenit / pokerhandevaluator Goto Github PK

Evaluate ranking within the category Two Pairs:

• Assuming two given hands are in that category: When are they tied? When is there a winner?
• See Must Have 3.2.1

Hint: Shared Logic

• Recognizing duplicates is shared between #10, #11, #12 and #16, and should build on each other accordingly.
  • This helps avoid redundancy and additional refactoring overhead on merge.

Evaluate ranking within the category Straight:

• Assuming two given hands are in that category: When are they tied? When is there a winner?
• See Must Have 3.2.1

Evaluate ranking within the category Flush:

• Assuming two given hands are in that category: When are they tied? When is there a winner?
• See Must Have 3.2.1

• Execute ./cradlew build on merge requests.
• Use OpenJDK 15

Suggestion: GitHub provides a preconfigured gradle.yaml script.

Evaluate ranking within the category Three of a Kind:

• Assuming two given hands are in that category: When are they tied? When is there a winner?
• See Must Have 3.2.1

Hint: Shared Logic

• Recognizing duplicates is shared between #10, #11, #12 and #16, and should build on each other accordingly.
  • This helps avoid redundancy and additional refactoring overhead on merge.

The following documents needed for development should be added to the wiki:

• Vision (Calling it a vision might be a bit much - it's mostly the task description)
• Requirements

Desired Project Setup:

• OpenJDK 15 (Latest JDK provided by Arch Linux)
• Gradle, using the Gradle Wrapper
• JUnit for testing
• Recommended IDE: IntelliJ

Implement categories to allow basic ranking.

• Compare Must Have 3.2 - Hand Rank Scoring Order

Evaluate ranking within the category Pair:

• Assuming two given hands are in that category: When are they tied? When is there a winner?
• See Must Have 3.2.1
  Evaluate ranking within the category Three of a Kind:
• Assuming two given hands are in that category: When are they tied? When is there a winner?
• See Must Have 3.2.1

Hint: Shared Logic

• Recognizing duplicates is shared between #10, #11, #12 and #16, and should build on each other accordingly.
  • This helps avoid redundancy and additional refactoring overhead on merge.

Evaluate ranking within the category Straight Flush:

• Assuming two given hands are in that category: When are they tied? When is there a winner?
• See Must Have 3.2.1

Evaluate ranking within the category High Card:

• Assuming two given hands are in that category: When are they tied? When is there a winner?
• See Must Have 3.2.1

Evaluate ranking within the category Four of a Kind:

• Assuming two given hands are in that category: When are they tied? When is there a winner?
• See Must Have 3.2.1

Hint: Shared Logic

• Recognizing duplicates is shared between #10, #11, #12 and #16, and should build on each other accordingly.
  • This helps avoid redundancy and additional refactoring overhead on merge.

Implement functionality for a poker hand that includes five poker cards.

This covers the following requirements:

• Must Have 1 - Setting a Poker Hand
• Must Have 2 - Allowed Poker Hands
  • Restriction on card type
  • Restriction on card amount

Implementation details:

• See suggested classes

Evaluate ranking within the category Full House:

• Assuming two given hands are in that category: When are they tied? When is there a winner?
• See Must Have 3.2.1