Skip to content

Conversation

@unicornrainbow
Copy link

This assumes rspec was being used, and that may be an incorrect assumption. Not
sure what test/spec mapped too, but that wasn't available for me locally, so I
had to remove it.

With these changes I can get the project specs to run for my locally using ruby
2.0.0.

$ rspec spec

All pass expect for two. I have work around fixes to get the last two specs
passing, but not exactly sure why they're failing.

If there was a different test framework being used, there may be an easier way to get
the specs to pass, but this is what I got working with rspec.

@unicornrainbow
Copy link
Author

This may be better to be pulled into a dev branch targeting an eventual new version release.

I was getting an error when trying to `bundle install` in 1.9.3. Relaxing the
version numbers I added fixed it and, and the specs still pass the same on 1.9.3
and 2.0.0.
@bradediger
Copy link
Member

Thanks, I'll be taking a look at this soon.

test/spec is an old BDD interface on top of test/unit, which I'm no longer using for current projects. RSpec is great -- it's my current default for new work.

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