On 27/01/2009, at 7:44 PM, David Chelimsky wrote:
On Tue, Jan 27, 2009 at 1:48 PM, Nick Hoffman
wrote:
G'day folks. I've been beating my head on this one problem for a
couple of
hours, and have managed to figure out what's causing it. However, I
don't
understand why it's happening, nor do I
On Wed, Jan 28, 2009 at 12:55 AM, s.ross wrote:
>
> Ok, I created stories
> http://github.com/sxross/cucumber_textile_formatter/tree/master
> :)
> On Jan 27, 2009, at 12:09 PM, aslak hellesoy wrote:
>
I'm inviting EVERYBODY to help design a new HTML format for Cucumber
0.2's new HTML formatter.
On Tue, Jan 27, 2009 at 1:48 PM, Nick Hoffman wrote:
> G'day folks. I've been beating my head on this one problem for a couple of
> hours, and have managed to figure out what's causing it. However, I don't
> understand why it's happening, nor do I know how to solve or get around it.
>
> One of my
Ok, I created stories
http://github.com/sxross/cucumber_textile_formatter/tree/master
:)
On Jan 27, 2009, at 12:09 PM, aslak hellesoy wrote:
On Tue, Jan 27, 2009 at 8:14 PM, s.ross wrote:
Sheepishly, I am announcing that I created a textile formatter for
Cuke. It was unabashedly ripped o
On Jan 27, 2009, at 12:08 PM, Brian Takita wrote:
On Tue, Jan 27, 2009 at 4:15 AM, Matt Wynne
wrote:
Not done it, but Cucumber acceptance tests would surely be a good
fit here:
Given there is a database "foo"
When I run the script
Then there should be a backup no more th
On Tue, Jan 27, 2009 at 12:08 PM, Brian Takita wrote:
>
> Yes, I have experience testing capistrano. My experience with unit
> testing Capistrano has been less than positive. Capistrano is
> difficult to test. Basically you have to mock out the shell/run/file
> transfer commands to do unit tests.
On Tue, Jan 27, 2009 at 8:14 PM, s.ross wrote:
> Sheepishly, I am announcing that I created a textile formatter for Cuke. It
> was unabashedly ripped out of the HTML formatter, so there is almost
> certainly a better way to do it. The incentive behind this was my desire to
> get stories posted on
G'day folks. I've been beating my head on this one problem for a
couple of hours, and have managed to figure out what's causing it.
However, I don't understand why it's happening, nor do I know how to
solve or get around it.
One of my methods clones an arg, and it seems that doing so causes
Sheepishly, I am announcing that I created a textile formatter for
Cuke. It was unabashedly ripped out of the HTML formatter, so there is
almost certainly a better way to do it. The incentive behind this was
my desire to get stories posted on Github. Like, real fast. If only
Github let me p
Sweet. Thank you Ben. Tim
On Tue, Jan 27, 2009 at 11:00 AM, Ben Mabey wrote:
> On 1/27/09 10:33 AM, Tim Walker wrote:
>>
>> Hi Guys,
>>
>> I refactored my folder hierarchy organizing my cucumber features in
>> sub-folders of features such as model, control, listeners, etc.
>>
>> When I run from t
On 1/27/09 10:33 AM, Tim Walker wrote:
Hi Guys,
I refactored my folder hierarchy organizing my cucumber features in
sub-folders of features such as model, control, listeners, etc.
When I run from the command line now I use the -r features prior to
specifying the folder name, all is good. From t
On Tue, Jan 27, 2009 at 9:13 AM, James Byrne wrote:
> James Byrne wrote:
>
> >
> > I moved the task :features => 'db:test:prepare' statement from after
> > task :features => "features:all" to before it, but this does not
> > influence the observed behaviour.
> >
>
> I lied. Evidently moving the t
Hi Guys,
I refactored my folder hierarchy organizing my cucumber features in
sub-folders of features such as model, control, listeners, etc.
When I run from the command line now I use the -r features prior to
specifying the folder name, all is good. From textmate, APPLE-R, how
do I specify the -r
On Tue, Jan 27, 2009 at 4:15 AM, Matt Wynne wrote:
> Not done it, but Cucumber acceptance tests would surely be a good fit here:
>
>Given there is a database "foo"
>When I run the script
>Then there should be a backup no more than 10 minutes old
>And the backup shou
James Byrne wrote:
>
> I moved the task :features => 'db:test:prepare' statement from after
> task :features => "features:all" to before it, but this does not
> influence the observed behaviour.
>
I lied. Evidently moving the the db:test:prepare statement did resolve
the problem after all.
--
This may be misunderstanding on my part but I thought that running rake
features would automatically run rake db:test:prepare. However, this
does not seem to be the case. Am I mistaken or is this a bug?
The rake task I am using is this:
#in ./lib/tasks/cucumber.rake
desc "Exercise cucumber feat
On 27/01/2009, at 11:03 AM, Nick Hoffman wrote:
Hey guys. I've just found some odd behaviour within RSpec 1.1.12 ,
and would like to know whether this is a bug, or I'm doing something
wrong.
When I give multiple return values to a stub, like this:
SubtitleFile.stub!(:new).and_return @sf1, @
Hey guys. I've just found some odd behaviour within RSpec 1.1.12 , and
would like to know whether this is a bug, or I'm doing something wrong.
When I give multiple return values to a stub, like this:
SubtitleFile.stub!(:new).and_return @sf1, @sf2
RSpec complains:
Mock 'SubtitleFile_1001' re
Not done it, but Cucumber acceptance tests would surely be a good fit
here:
Given there is a database "foo"
When I run the script
Then there should be a backup no more than 10 minutes old
And the backup should restore OK
And the restored database should contain
19 matches
Mail list logo
