-
Notifications
You must be signed in to change notification settings - Fork 419
Upgrade to RSpec 3.0 #128
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
Upgrade to RSpec 3.0 #128
Conversation
The cause I've identified so far is the invalid conversion of Your spec has an |
So, I think there are 2 options: 1. Name the subject and use the name in the hooksubject(:actor, &subject_definition)
after { terminate_actors actor } 2. Continue using
|
@yujinakayama Thank you for the help and the suggestions! I'll refactor the tests this evening. |
@yujinakayama I've made the changes you suggested and all the tests pass on my local machine. I expect that Travis will verify a successful upgrade to RSpec 3.0. Thank you again for your assistance. |
@jdantonio you've been faster by few minutes I was just about to push actress_fixes too :) |
Thanks |
@jdantonio You're welcome :). |
@pitr-ch I woke up this morning much earlier than normal so I took advantage of the time. Than you for looking into those tests. |
All specs now pass with RSpec 3.0.
Original PR Comments:
This branch represents my attempt to upgrade us to RSpec 3.0. We now have almost 30 failing tests.
I followed the step-by-step Instructions verbatim and used the transpec tool as directed. I ran everything under
ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-darwin13.0]
on my MacBook Pro. The test suite was green at the start. Now I get numerous failed tests when runningbundle exec rspec -fd --color --seed 1
. None of our intermittently failing specs are amongst the current set of failing tests. All the failing tests are in two files:I'll work on these specific tests later then report the issues to the RSpec team. The full output of the test run is below.
RSpec Output