-
Notifications
You must be signed in to change notification settings - Fork 71
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
Use voxpupuli-acceptance #647
Conversation
Hold off, I messed up and wiped a lot of my changes accidentally. |
Luckily I made a backup branch before I started the dangerous operations. Pushing fixed versions again and should be ready for review. |
716ce37
to
e65ec6f
Compare
@dhollinger this is inspired by what you said: we shouldn't template the spec acceptance helper. It doesn't, but provides a way to trivially do for trivial helpers. I'd be interested in what you think. This is also where I think https://github.com/voxpupuli/voxpupuli-test should be in an ideal world, but there's too much variation in that file that I haven't been able to trim just yet. |
This moves a lot of logic from modulesync into a gem. This greatly reduces the amount of code we have to sync. It also starts to manage spec_acceptance_helper.rb in various modules when they only need a trivial helper.
e65ec6f
to
99eb60e
Compare
|
This moves a lot of logic from modulesync into a gem. This greatly reduces the amount of code we have to sync. It also starts to manage spec_acceptance_helper.rb in various modules when they only need a trivial helper.