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

Implement shouldBeOneOf matcher and assertions #647

Merged
merged 1 commit into from
Feb 11, 2019

Conversation

LeoColman
Copy link
Member

Closes #616

@LeoColman LeoColman merged commit 2e0b3c4 into master Feb 11, 2019
@LeoColman LeoColman deleted the feature/616-should-be-one-of-matcher branch February 11, 2019 13:36
LeoColman added a commit that referenced this pull request Feb 11, 2019
Pull request #647 introduced the matcher `shouldBeOneOf`. This matcher is going to be introduced in a future version of KotlinTest, and with it, the documentation must be current.

This wasn't added as part of #647 because we didn't want documentation to include a matcher not existent yet.

Part of #616
LeoColman added a commit that referenced this pull request Feb 11, 2019
Pull request #647 introduced the matcher `shouldBeOneOf`. This matcher is going to be introduced in a future version of KotlinTest, and with it, the documentation must be current.

This wasn't added as part of #647 because we didn't want documentation to include a matcher not existent yet.

Part of #616
sksamuel pushed a commit that referenced this pull request Feb 17, 2019
Pull request #647 introduced the matcher `shouldBeOneOf`. This matcher is going to be introduced in a future version of KotlinTest, and with it, the documentation must be current.

This wasn't added as part of #647 because we didn't want documentation to include a matcher not existent yet.

Part of #616
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.

2 participants