-
-
Notifications
You must be signed in to change notification settings - Fork 764
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
generate configuration for autotest #10
Comments
Chad and Kabari are working on this (rspec hackfest FTW). |
Nobody is working on this now, so if anybody else wants to, just add a comment here that you're doing so. |
I got this one. |
David, I sent you a pull request before realizing you'd rather have "pull requests" pasted here. I'll do that from now on. |
justinko's patch: http://github.com/justinko/rspec-core/commit/291d316 |
Hey Justin - I applied your patch and got a syntax error
After addressing that, all the specs and cukes passed, but when I tried it on the command line with a pre-existing
Wanna take another shot? |
Fixed: http://github.com/justinko/rspec-core/commit/81d2be8 Question. Since aruba cannot cover the "gets" method, should I test it with RSpec doing something like this?: http://technicalpickles.com/posts/a-pattern-for-using-standard-in-and-out-in-your-ruby-code/ Thanks David. |
@justinko - No need to modify the design like that. This isn't java :) You can stub gets right on the object: interactor = Interactor.new interactor.stub(:gets).and_return("this") interactor.method_that_adds_and_that_to_gets.should eq("this and that") I generally try avoid stubbing methods on the subject of an example, but I'd probably go for the tradeoff here. |
I applied your patch (from 2 comments back) and got the same syntax error, and then got this after fixing it and trying to run:
|
I'm getting no errors with HEAD. I created another clean branch, try using this one: |
Add an option to the rspec command to configure a project directory for autotest, and eliminate the autospec command. Something like:
This would generate autotest/discover.rb, which would tell autotest that this is an rspec project.
The text was updated successfully, but these errors were encountered: