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

Cleaning up leftovers after extracting ValidateSelection use-case Gem. #84

Merged
merged 2 commits into from
Nov 8, 2016

Conversation

jdickey
Copy link
Contributor

@jdickey jdickey commented Nov 8, 2016

As per Issue #71. New Gem uses revised use-case protocol rather than arbitrary public attributes.

Modified "validate selection"'s main test suite to use the new `Result`
object per new-standard use-case protocol. That test suite goes away
next.

272 tests, 310 assertions, 0 failures, 0 errors, 0 skips
Coverage: 2509 / 2511 LOC (99.92%) covered.
RuboCop: 90 files inspected, no offenses detected
Flay: Total score 0
Flog: Total 713.1; method average 3.3; max 6.6 (Prolog::UseCases::AcceptSingleProposal#entity_attribs)
Reek: 0 warnings
@jdickey jdickey added the bug label Nov 8, 2016
@jdickey jdickey added this to the Gem Release 0.16.0 milestone Nov 8, 2016
@jdickey jdickey self-assigned this Nov 8, 2016
262 tests, 300 assertions, 0 failures, 0 errors, 0 skips
Coverage: 2452 / 2454 LOC (99.92%) covered.
RuboCop: 89 files inspected, no offenses detected
Flay: Total score 0
Flog: Total 713.1; method average 3.3; max 6.6 (Prolog::UseCases::AcceptSingleProposal#entity_attribs)
Reek: 0 warnings
@jdickey jdickey merged commit 00dad50 into master Nov 8, 2016
@jdickey jdickey deleted the issue-71-cleanup branch November 8, 2016 06:03
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant