On Apr 29, 10:37 am, Ben Mabey wrote:
> However, that is not done yet. As it stands now you
> have two options: a) have the test execution and script in the same
> process or b) Use ARMailer[1] in your testing environment. ARMailer
> places the messages in a database for queuing. So instead of
> I don't know if this will interest anyone, but I thought it was a
> pretty cool use of Cucumber :)
>
OMG sooo cool.
Added here:
http://wiki.github.com/aslakhellesoy/cucumber/tutorials-and-related-blog-posts
Aslak
>
> I've posted a Blog article on how I use Cucumber to test an Erlang
> Server
On Sat, May 2, 2009 at 11:25 AM, wrote:
>
> The only potentially unhappiness is going to come from whomever reads the
> code later and is not familiar with the plugin and wonders where the hell
> that method is being defined.
>
To whom I'd say "Welcome to Rails." :)
///ark
_
Julian Leviston wrote:
Fair enough.
The steps from step definitions one is the best approach for what I
want, and it's actually what am doing, but I do notice that there's a
lot of the time when I'm actually re-typing the same text (ie once in
the explicit explanation of what it means to log
> You *could* write wrapper methods for chains like this and make Demeter
> happy, but to do that for every single call...
Thank you for your experience. I myself used to wrap these kind of
associations but I felt it started to clutter the Model file, so I
started to use association callbacks.
Hi,
When upgrading to rspec/rspec-rails 1.2.6 gem (from 1.1.12), I'm having
a new problem verifying routes that should not exist.
This is to support something like this in routes.rb:
map.resources :orders do |orders|
orders.resources :items, :except => [:index,:show]
end
I used to use lambd
You know what'd be awesome?
If Cucumber scenarios were referential.
I mean, wouldn't it be awesome if you could refer to them... so you
could build on them...
So in a login.feature I'd define:
Scenario: logging in
Given that a default user exists
And I am on the login page
When I fill in "u
Fair enough.
The steps from step definitions one is the best approach for what I
want, and it's actually what am doing, but I do notice that there's a
lot of the time when I'm actually re-typing the same text (ie once in
the explicit explanation of what it means to log in, and then once
m
Julian Leviston wrote:
You know what'd be awesome?
If Cucumber scenarios were referential.
I mean, wouldn't it be awesome if you could refer to them... so you
could build on them...
So in a login.feature I'd define:
Scenario: logging in
Given that a default user exists
And I am on the login
Hi Julian,
You can do just that, the scenarios stack like that quite well, and it is
reasonable to call a step from another, but you should have something like
Scenario: Logging In
Given there is a user
When I visit the login page
And I fill in username with ...
And I fill in passowrd with ..
On May 2, 2009 11:00am, Fernando Perez wrote:
Hi,
Using Ruby on Rails, let's says I have an Article model and Comment
model. An Article has_many :comments,
Using Rais idiom, one would do something like that in the
comments_controller/create:
@article = Article.find(params[:i
Hi,
Using Ruby on Rails, let's says I have an Article model and Comment
model. An Article has_many :comments,
Using Rais idiom, one would do something like that in the
comments_controller/create:
@article = Article.find(params[:id])
@article.comments.create(params[:comment])
I don't like too mu
Aslak Hellesøy wrote:
I use mkdir and touch.
Me too
Yeah, "mkdir -p features/support && mkdir -p features/step_defnintions
&& touch features/support/env.rb" is really all you need.
However, for new projects I really like to use jeweler to bootstrap all
the setup for Cucumber, RSpec, R
Jim Morris wrote:
I don't know if this will interest anyone, but I thought it was a
pretty cool use of Cucumber :)
I've posted a Blog article on how I use Cucumber to test an Erlang
Server directly by talking to my Erlang Nodes.
http://blog.wolfman.com/articles/2009/5/2/using-cucumber-to-test-e
Hi list,
I checked out the rspec-dev repository on a MBP (Leopard) and tried to
run the pre_commit task after going through the setup/configuration
steps on http://wiki.github.com/dchelimsky/rspec/contribute.
I'm getting DRB errors related to script/spec_server when running
specs: Address already
On Sat, May 2, 2009 at 2:11 AM, Doug wrote:
> Hi list,
>
> I checked out the rspec-dev repository on a MBP (Leopard) and tried to
> run the pre_commit task after going through the setup/configuration
> steps on http://wiki.github.com/dchelimsky/rspec/contribute.
>
> I'm getting DRB errors related
I use mkdir and touch.
Me too
On May 1, 11:25 pm, James Byrne wrote:
Setting up cucumber inside a Rails project is no more difficult than
running script/generate cucumber. But what does one do when working
without Rails at all? How do you generate the features tree and
all of
its de
I don't know if this will interest anyone, but I thought it was a
pretty cool use of Cucumber :)
I've posted a Blog article on how I use Cucumber to test an Erlang
Server directly by talking to my Erlang Nodes.
http://blog.wolfman.com/articles/2009/5/2/using-cucumber-to-test-erlang-servers
It us
I use mkdir and touch.
On May 1, 11:25 pm, James Byrne wrote:
> Setting up cucumber inside a Rails project is no more difficult than
> running script/generate cucumber. But what does one do when working
> without Rails at all? How do you generate the features tree and all of
> its default files
19 matches
Mail list logo
