On 14 May 2009, at 05:01, Phlip wrote:
anmaxp wrote:
I'm having sort of an issue here, I'm trying to test the update of
the
last_login field upon login, here is my test
it "assigns a new last_login timestamp" do
User.expects(:update_attribute).at_least_once.returns(true)
User.any_inst
On Tue, Aug 19, 2008 at 2:35 PM, Jonathan Linowes
wrote:
>
>rake spec RAILS_ENV=production
>
> that way the db:test:prepare uses the production db rather than the
> development one
I know this thread is long dead but ... you must be joking.
///ark
___
anmaxp wrote:
I'm having sort of an issue here, I'm trying to test the update of the
last_login field upon login, here is my test
it "assigns a new last_login timestamp" do
User.expects(:update_attribute).at_least_once.returns(true)
User.any_instance.expects(:update_attribute).with(:fie
On Wed, May 13, 2009 at 9:59 PM, Matthew Isleb wrote:
> I know this thread is long dead, but I'm finding that I have the same
> problem. 'rake spec:modles' loads the development environment and
> clobbers my development database. I have to run set RAILS_ENV=test in
> order for the tests to run cor
I know this thread is long dead, but I'm finding that I have the same
problem. 'rake spec:modles' loads the development environment and
clobbers my development database. I have to run set RAILS_ENV=test in
order for the tests to run correctly.
Commenting out that rake task line does not solve t
Hey everyone,
I'm having sort of an issue here, I'm trying to test the update of the
last_login field upon login, here is my test
it "assigns a new last_login timestamp" do
User.expects(:update_attribute).at_least_once.returns(true)
post :create, :email => 'b...@example.com', :password
On May 13, 2009, at 1:42 PM, Fernando Perez wrote:
Hi,
I use restful routes. In one of my views I have a form that looks
like:
<%- form_tag '/items/update', :method => :put do -%>
...
<%= submit_tag "Recalculate" %>
<%- end -%>
I know I cheated a bit, as I should be submitting to /items
Hi,
I use restful routes. In one of my views I have a form that looks like:
<%- form_tag '/items/update', :method => :put do -%>
...
<%= submit_tag "Recalculate" %>
<%- end -%>
I know I cheated a bit, as I should be submitting to /items/1 instead.
Anyway, now how can I trigger the update act
On 13 Maj, 01:14, Randy Harmon wrote:
> mortench wrote:
> > The new rspec beta book and the rspec site mentions that it is
> > possible to add a hash to "describe" and "it" constructs but very,
> > very litle information about the particulars.
>
> > What can the options hash be used for and what s
On 13 Maj, 07:28, David Chelimsky wrote:
> You can access the group and example options from within an example:
>
> describe "group options hash", :defined_in => :group do
> it "is available in examples via self.class.options" do
> self.class.options[:defined_in].should == :group
> end
> e
Hi--
On May 13, 2009, at 12:47 AM, Lee wrote:
I found a potential solution from this blog:
http://www.rubytutorials.net/2008/02/29/small-rspec-revelations-rjs/
In my spec for the view in which I want to include the AJAX
functionality ("new.html.erb_spec.erb"), I have added a couple of
Examples
On May 13, 7:08 pm, David Chelimsky wrote:
>
> I actually think that what you're doing is perfectly fine. Just not
> the common case. That's why I think it's OK to support explicitly
> assigning self as subject, but not making that a default behaviour.
>
> If it were me, and it's *not*, but if i
On Wed, May 13, 2009 at 11:02 AM, Jarmo Pertman wrote:
> On May 12, 6:21 am, David Chelimsky wrote:
>>
>> I don't want to promote using self as subject. I think being able to
>> do so explicitly, as we can now with your previous patch, is perfectly
>> reasonable. But doing so is a bit of a trick
On Wed, May 13, 2009 at 11:02 AM, Jarmo Pertman wrote:
> On May 12, 6:21 am, David Chelimsky wrote:
>>
>> I don't want to promote using self as subject. I think being able to
>> do so explicitly, as we can now with your previous patch, is perfectly
>> reasonable. But doing so is a bit of a trick
On May 12, 6:21 am, David Chelimsky wrote:
>
> I don't want to promote using self as subject. I think being able to
> do so explicitly, as we can now with your previous patch, is perfectly
> reasonable. But doing so is a bit of a trick in my view, and runs
> counter to the overall intent of the st
Matt Wynne wrote:
I'm still bugged by the fact that when I get an exception during a
feature run (e.g. Couldn't find partial) then what I see in the
console is all the HTML to report that error in a browser.
I have had a few ideas for this bubbling around at the back of my
mind. I wondered wh
> I am running into this situation:
>
> Feature 1
>
> Scenario A
> ...
> Then we should have currency exchange rates for "USD" on file
> And we should ...
>
>
> Feature 2
>
> Scenario D
> ...
> Then we should have currency exchange rates for "USD" on file
> | code|
>
I am running into this situation:
Feature 1
Scenario A
...
Then we should have currency exchange rates for "USD" on file
And we should ...
Feature 2
Scenario D
...
Then we should have currency exchange rates for "USD" on file
| code|
|"EUR"|
|"
Well I can't help you but I do have a similar problem. In my case
Cucumber-Selenium works, Cucumber-Webrat works but Cucmber-Webrat-
Selenium doesn't work because Webrat issues requests to www.example.com
and Selenium starts up a mongrel on localhost:3001, connects to it via
Firefox and then throws
On Wed, May 13, 2009 at 8:42 AM, Matt Wynne wrote:
> I'm still bugged by the fact that when I get an exception during a feature
> run (e.g. Couldn't find partial) then what I see in the console is all the
> HTML to report that error in a browser.
>
> I have had a few ideas for this bubbling around
I'm still bugged by the fact that when I get an exception during a
feature run (e.g. Couldn't find partial) then what I see in the
console is all the HTML to report that error in a browser.
I have had a few ideas for this bubbling around at the back of my
mind. I wondered whether anyone els
I found a potential solution from this blog:
http://www.rubytutorials.net/2008/02/29/small-rspec-revelations-rjs/
In my spec for the view in which I want to include the AJAX
functionality ("new.html.erb_spec.erb"), I have added a couple of
Examples to drive out the some of the AJAX functionality:
22 matches
Mail list logo
