Speed will possibly become a big issue once you get above 1-2k steps or so.
Testjour was written to solve this:
http://github.com/brynary/testjour/tree/master
While I haven't been able to use it myself, since I work mostly from home,
it apparently radically reduces the time it takes to run
Hi Matt/Dan
2009/3/2 Matt Wynne m...@mattwynne.net:
At the moment, IMO, the tools for feeding back the features to non-technical
people are pretty immature. My colleague Dan Lucraft wrote a tool which
produces a nicely-formatted PDF document from your features folder[1] which
is great, but
On 3 Mar 2009, at 10:06, aidy lewis wrote:
Hi Matt/Dan
2009/3/2 Matt Wynne m...@mattwynne.net:
At the moment, IMO, the tools for feeding back the features to non-
technical
people are pretty immature. My colleague Dan Lucraft wrote a tool
which
produces a nicely-formatted PDF document
On Tue, Mar 3, 2009 at 2:06 AM, aidy lewis aidy.le...@googlemail.com wrote:
Hi Matt/Dan
2009/3/2 Matt Wynne m...@mattwynne.net:
At the moment, IMO, the tools for feeding back the features to non-technical
people are pretty immature. My colleague Dan Lucraft wrote a tool which
produces a
At 16:41 -0800 3/3/09, Pat Maddox wrote:
Not quite. Some customers don't want to sit down next to you as you
write the stories. In that situation, we'll talk about features, I
take notes, then I write up the features and ship them via email or
wiki. They're still involved in the creation of
Let me share my experience.
On my side we do produce 3 documents before starting with rspec.
1- A web designer creates a design for a screen in conjunction with the
marketing team and the analyst assigned to the this feature. The marketing
dep, acts as the customer.
2-The analyst produce a
On Tue, Mar 3, 2009 at 5:06 AM, aidy lewis aidy.le...@googlemail.com wrote:
To me the user\customer should be involved in the creation of the
stories and the acceptance criteria and by producing a pdf later in
the cycle for those stakeholders to read and understand may be argued
as something
At 21:21 -0500 3/3/09, Remi Gagnon wrote:
For now we are not having any tool to transfer
stories-scenarios from our word doc to rspec file.
If any of you have something for that, let me know.
I don't have any software to offer, but I can offer a
suggestion regarding process. If the word
Hi Tom,
We have written an extension that counts your tests and provides a
link(s) to the failure backtrace in the Cucumber HTML.
There seem to be issues when Cucumber writes to the HTML over around
800 steps, so we are waiting for version 0.2.
Aidy
On 26/02/2009, Tom ten Thij
On 26 Feb 2009, at 15:33, Tom ten Thij wrote:
We will be using Cucumber for a fairly large project. Are there any
areas that cucumber is lacking when there are many scenarios?
I believe the best candidate for showing our client the scenario
results is the html output. It strikes me that that
We will be using Cucumber for a fairly large project. Are there any
areas that cucumber is lacking when there are many scenarios?
I believe the best candidate for showing our client the scenario
results is the html output. It strikes me that that becomes fairly
cumbersome to check with many
Tom ten Thij wrote:
We will be using Cucumber for a fairly large project. Are there any
areas that cucumber is lacking when there are many scenarios?
I believe the best candidate for showing our client the scenario
results is the html output. It strikes me that that becomes fairly
12 matches
Mail list logo
