Skip to content

Conversation

@ccouzens
Copy link
Contributor

I'm going to be upgrading the Ruby version.
This is going to require me to upgrade the Rubocop version.

Before I begin, I want to be able to run:

./bin/generate --all
bundle exec rake test
bundle exec rubocop
git status

And see no failures or changed code.
This way, I can easily verify I haven't broken anything in the version upgrades.
This pull request gets the project into that good state.


I suspect regenerating the exercises is good for keeping the project fresh as well.
Only 6 exercises needed regenerating.
Phone number and space age were easy.
Gigasecond needed a change to it's generator.
Acronym needed a change to it's generator and a small change to the example solution.
Sum of multiples needed a small change to it's example solution.
Wordy needed a more involved change to it's example solution.

This regenerates phone_number and space-age tests.
They're still syntactically correct and the tests still pass for them.
I've not committed acronym_test, sum_of_multiples or wordy as
regenerating them breaks them.

Keeping the exercises up to date is generally a good idea. I'm
particuarly interested in regenerating them so I can know the effect of
my other changes.

I'll be upgrading the ruby version and the rubocop version. By
regenerating before hand, I can more easily verify that my changes
haven't changed the regeneration process.

```
./bin/generate --all
```
Regenerate the sum-of-multiples test case. The example solution needed
fixing to incorporate the new test case.
The new test case that has a number but no operations broke the example
solution. I fixed the test case by not having the regular expression
require any operations.
@kotp
Copy link
Member

kotp commented Jan 29, 2019

./bin/local-status-check provides the rake and rubocop executions, by the way. Put that in your pre-commit hook and you get the behavior for free.

@kotp kotp requested a review from emcoding June 13, 2019 03:43
@iHiD iHiD closed this Jan 28, 2021
@iHiD iHiD deleted the branch exercism:master January 28, 2021 19:15
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