El 28/6/2009, a las 23:04, Matt Wynne escribió:
On 28 Jun 2009, at 13:07, Wincent Colaiuta wrote:
I've had one of my recurring doubts about test doubles come up again.
The full post is here but I'll abbreviate the content in this
message in any case:
https://wincent.com/blog/thinking-abou
On 28 Jun 2009, at 11:33, Michael wrote:
I'm trying to figure out how to test that the current_user does end up
being attached to a new model that is being created which happens to
be an Album.
Here is the Controller code.
def create
@album = current_user.albums.new params[:album]
if @
On 28 Jun 2009, at 13:07, Wincent Colaiuta wrote:
I've had one of my recurring doubts about test doubles come up again.
The full post is here but I'll abbreviate the content in this
message in any case:
https://wincent.com/blog/thinking-about-switching-to-rr
Basically, in one of my contr
Awesome presentation, thanks for clarifying it Ben.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
Jesse Crockett wrote:
Ben Mabey wrote:
On Jun 28, 2009, at 8:32 AM, Jesse Crockett wrote:
When I use integrate_views, can I write view spec in what would
otherwise be isolated controller spec?
Correct, by default RSpec's controller specs will not render the
view. This allows y
Sarah Allen wrote:
> I find that testing views independently is useful just to catch HTML
> errors that can sometime creep in during a re-factor. These check
> important details that would be more tedious using cucumber. The
> controller specs establish the post-condition for the controller
> ind
Ben Mabey wrote:
> On Jun 28, 2009, at 8:32 AM, Jesse Crockett wrote:
>
>> When I use integrate_views, can I write view spec in what would
>> otherwise be isolated controller spec?
>
> Correct, by default RSpec's controller specs will not render the
> view. This allows you to test the controller
I find that testing views independently is useful just to catch HTML
errors that can sometime creep in during a re-factor. These check
important details that would be more tedious using cucumber. The
controller specs establish the post-condition for the controller
independent of the view.
I'm trying to figure out how to test that the current_user does end up
being attached to a new model that is being created which happens to
be an Album.
Here is the Controller code.
def create
@album = current_user.albums.new params[:album]
if @album.save
flash[:notice] = "The alb
I'm trying to figure out how to test that the current_user does end up
being attached to a new model that is being created which happens to
be an Album.
Here is the Controller code.
def create
@album = current_user.albums.new params[:album]
if @album.save
flash[:notice] = "The alb
On Jun 28, 2009, at 8:32 AM, Jesse Crockett wrote:
Hello,
I've been trying for two years to pick up BDD. I'm making progress,
have just read through the chapters in The RSpec Book on spec'ing
views
and controllers.
What is the difference between using integrate_views and doing what
seems
Hello,
I've been trying for two years to pick up BDD. I'm making progress,
have just read through the chapters in The RSpec Book on spec'ing views
and controllers.
What is the difference between using integrate_views and doing what
seems to be a lot of extra work to test the views in isolation?
I've had one of my recurring doubts about test doubles come up again.
The full post is here but I'll abbreviate the content in this message
in any case:
https://wincent.com/blog/thinking-about-switching-to-rr
Basically, in one of my controller specs I wanted to verify that the
following
13 matches
Mail list logo
