+lots :)
Generally when we have problems with features its because we are trying to
do to much at once. So in your case date entry is being complicated by
different contexts, birth and incident. One of the tennents of BDD is to
write the simplest thing you can to make you feature pass. I think
Also, if people are into this sort of thing, I would be up for helping build
it.
On Tue, Dec 16, 2008 at 3:17 AM, Mischa Fierer f.mis...@gmail.com wrote:
A few other things...
In the interface that I was describing, it would solve several problems to
have something like:
Given I'm a client
aidy lewis wrote:
Hi,
I have a step that has been defined by the user
Given /a logged in user/ {}
Now in that step I have my own step (not defined by the business) of
Given all projects have been deleted
This sounds like something that might be better suited to a Before / After.
On Dec 16, 2008, at 6:50 AM, aidy lewis wrote:
Hi,
I have a step that has been defined by the user
Given /a logged in user/ {}
Now in that step I have my own step (not defined by the business) of
Given all projects have been deleted
The second step needs to be included in the first
A few other things...
In the interface that I was describing, it would solve several problems to
have something like:
Given I'm a client
When I follow new story
And I drag in Given I am a Pet Owner
And I press new action
And I select When I follow
And I fill in follows_what_link with Buy another
Hi,
I have a step that has been defined by the user
Given /a logged in user/ {}
Now in that step I have my own step (not defined by the business) of
Given all projects have been deleted
The second step needs to be included in the first
Given /a logged in user/ do
Given(all projects have
I can maybe offer something here. *begin rambling*
My team of 4 (2 coders, 2 biz people) has recently switched to using Pivotal
Tracker, and we've been doing the following:
1) Figure out what we can do that will add value
2) Draw out the ui / changes on a whiteboard
3) Write out features copy
I am working with the authlogic gem and trying to create a simple login
test from cucumber features. The feature statement is:
Given the user is not logged in
The step definition for this is confounding me. In the
application_controller the authlogic tutorial recommends the following:
private
On Tue, Dec 16, 2008 at 1:34 PM, James Byrne li...@ruby-forum.com wrote:
I am working with the authlogic gem and trying to create a simple login
test from cucumber features. The feature statement is:
Given the user is not logged in
The step definition for this is confounding me. In the
On Tue, Dec 16, 2008 at 2:01 PM, Lenny Marks le...@aps.org wrote:
On Dec 9, 2008, at 10:40 PM, Avdi Grimm wrote:
I contributed an article on BDD and RSpec to the Ruby Advent Calendar
2008, going over some of the rules I've collected for interpreting
what your specs say about your design. It
On Tue, Dec 16, 2008 at 2:51 PM, Ben Mabey b...@benmabey.com wrote:
David Chelimsky wrote:
On Tue, Dec 16, 2008 at 2:01 PM, Lenny Marks le...@aps.org wrote:
On Dec 9, 2008, at 10:40 PM, Avdi Grimm wrote:
I contributed an article on BDD and RSpec to the Ruby Advent Calendar
2008, going
Lenny Marks wrote:
On Dec 9, 2008, at 10:40 PM, Avdi Grimm wrote:
I contributed an article on BDD and RSpec to the Ruby Advent Calendar
2008, going over some of the rules I've collected for interpreting
what your specs say about your design. It can be found here:
On Dec 16, 2008, at 5:17 PM, Avdi Grimm wrote:
So I was running my specs with -w the other day, and noticed a lot of
warnings being produced. Some of these appear to be coming from RSpec
internals, which is an issue in its own right but not the subject of
this email. What I'm asking about
On Tue, Dec 16, 2008 at 11:46 PM, Scott Taylor sc...@railsnewbie.comwrote:
On Dec 16, 2008, at 5:17 PM, Avdi Grimm wrote:
So I was running my specs with -w the other day, and noticed a lot of
warnings being produced. Some of these appear to be coming from RSpec
internals, which is an
Doing this for Restful-Authentication I add the following in
features/support/env.rb
# Make visible for testing
ApplicationController.send(:public, :logged_in?, :current_user,
:authorized?)
Hopefully something similar will work with Authlogic
Andrew
2008/12/16 James Byrne li...@ruby-forum.com
So I can confirm that I'm logged in, that the user is who I say he is, etc.
e.g
Then /^I should be logged in$/ do
controller.logged_in?.should be_true
end
makes sense?
2008/12/16 Zach Dennis zach.den...@gmail.com
On Tue, Dec 16, 2008 at 6:47 PM, Andrew Premdas aprem...@gmail.com
wrote:
On Wed, Dec 17, 2008 at 1:48 AM, Andrew Premdas aprem...@gmail.com wrote:
So I can confirm that I'm logged in, that the user is who I say he is, etc.
e.g
Then /^I should be logged in$/ do
controller.logged_in?.should be_true
Or:
controller.should be_logged_in
Aslak
end
makes
On Tue, Dec 16, 2008 at 8:30 PM, Zach Dennis zach.den...@gmail.com wrote:
On Tue, Dec 16, 2008 at 7:48 PM, Andrew Premdas aprem...@gmail.com wrote:
So I can confirm that I'm logged in, that the user is who I say he is, etc.
e.g
Then /^I should be logged in$/ do
18 matches
Mail list logo
