So I think that this is an Authlogic issue, not a RSpec-Rails issue.
I'll keep digging and if I find a fix I'll update
On Oct 27, 10:53 pm, Brian Cardarella wrote:
> I've isolated the code pretty well. The session is being set with
> Authlogic, not certain if that makes a difference.
>
> The sess
I've isolated the code pretty well. The session is being set with
Authlogic, not certain if that makes a difference.
The session hash is empty on the test side but populated in the
controller when it shouldn't be.
On Oct 27, 10:45 pm, David Chelimsky wrote:
> On Oct 27, 2009, at 9:39 PM, Brian C
On Oct 27, 2009, at 9:39 PM, Brian Cardarella
wrote:
I noticed that a session that I am setting up in one exa,ple is still
available in another. Is RSpec-Rails supposed to tear down the session
or should I be doing this myself?
Unless you've got a before(:all) block, you should be getting a
I noticed that a session that I am setting up in one exa,ple is still
available in another. Is RSpec-Rails supposed to tear down the session
or should I be doing this myself?
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mail
On Oct 27, 2009, at 6:48 PM, Rodrigo Rosenfeld Rosas > wrote:
Em 27-10-2009 15:17, David Chelimsky escreveu:
On Oct 27, 2009, at 8:21 AM, Rodrigo Rosenfeld Rosas wrote:
Hi David, I'm giving a try to RSpec after we meet each other on
Rails Summit Latin America and I must admit I'm enjoying us
Em 27-10-2009 15:17, David Chelimsky escreveu:
On Oct 27, 2009, at 8:21 AM, Rodrigo Rosenfeld Rosas wrote:
Hi David, I'm giving a try to RSpec after we meet each other on Rails
Summit Latin America and I must admit I'm enjoying using
rspec/machinist/faker.
Since I have not written any contro
Thanks! That was very helpful. I did do some searching but didn't
come up with that result.
On Oct 27, 11:16 am, Ashley Moran
wrote:
> On Oct 27, 2009, at 3:51 pm, drewB wrote:
>
> > As you can see, I am not mocking current_user.objectives.create so I
> > have to look at assigns[:objective] to
On Oct 27, 2009, at 3:51 pm, drewB wrote:
As you can see, I am not mocking current_user.objectives.create so I
have to look at assigns[:objective] to test that things are working.
How would I go about mocking it?
Hi Drew
A virtually identical question was asked recently. Hopefully the
rep
I am having a lot of trouble figure out how to mock one my controller
methods. I was hoping someone might be able to help me.
---
Controller:
def create
@objective = current_user.objectives.create(params[:objective])
end
RSpec:
it "should create a new objec
On Oct 27, 2009, at 8:21 AM, Rodrigo Rosenfeld Rosas wrote:
Hi David, I'm giving a try to RSpec after we meet each other on
Rails Summit Latin America and I must admit I'm enjoying using rspec/
machinist/faker.
Since I have not written any controllers yet, I hadn't taken a
chance to try we
Amit,
Your controller spec that you said was working was not actually testing your
controller since you were not calling any of your controller methods.
I'd suggest you create some code from rspec_scaffold on your rails project
and just check out the code that's generated for you.
ruby script/ge
Hi David, I'm giving a try to RSpec after we meet each other on Rails
Summit Latin America and I must admit I'm enjoying using
rspec/machinist/faker.
Since I have not written any controllers yet, I hadn't taken a chance to
try webrat.
But there is a situation that I would like some feedback
Hello everybody,
I had written same scenario using normal code which is as follows :
def valid_attributes
{
:body => "test_description",
:title => "test123",
}
end
describe BbPostsController, "POST Create" do
before(:each) do
@post = BbPost.new
end
context "Admin" do
fixt
13 matches
Mail list logo
