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

Poker: Make high card tests more robust #2336

Merged
merged 1 commit into from
Nov 4, 2023
Merged

Conversation

SLeitgeb
Copy link
Contributor

Ensure that high cards are checked in the correct order (high ranking cards down to low ranking cards). Tests previously succeeded even when comparing lowest ranking spare cards first (e.g. "3H JS" beats "2C 5H" even when comparing "3H" vs. "2C").

Two tests added to ensure hands with pairs and triplets of the same rank are checked for high cards down to the last card.

Copy link
Contributor

Hello. Thanks for opening a PR on Exercism. We are currently in a phase of our journey where we have paused community contributions to allow us to take a breather and redesign our community model. You can learn more in this blog post. As such, all issues and PRs in this repository are being automatically closed.

That doesn't mean we're not interested in your ideas, or that if you're stuck on something we don't want to help. The best place to discuss things is with our community on the Exercism Community Forum. You can use this link to copy this into a new topic there.


Note: If this PR has been pre-approved, please link back to this PR on the forum thread and a maintainer or staff member will reopen it.

Ensure that high cards are checked in the correct order (high ranking
cards down to low ranking cards). Tests previously succeeded even when
comparing lowest ranking spare cards first (e.g. "3H JS" beats "2C 5H"
even when comparing "3H" vs. "2C").

Two tests added to ensure hands with pairs and triplets of the same
rank are checked for high cards down to the last card.
@IsaacG
Copy link
Member

IsaacG commented Oct 31, 2023

Is there a forum post to discuss this change? Changes should be discussed on the forum prior to opening a PR.

@SLeitgeb
Copy link
Contributor Author

SLeitgeb commented Nov 1, 2023

I didn't know that, sorry about that. Created a new topic here.

@IsaacG
Copy link
Member

IsaacG commented Nov 4, 2023

Erik says this isn't a problem with existing code. It's been three days without anyone having any concern. I'll click the merge button 😄

@IsaacG IsaacG merged commit ccb6fdf into exercism:main Nov 4, 2023
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.

4 participants