Hi,
Are there any tools available that can parse the Cucumber/Gherkin DSL
code and produce the more human readable list oriented test cases? It
sounds like it should be theoritically possible to write the test
cases in Gherkin code and then produce both the automated test cases
and the manual tes
Hi guys,
I guess, this idea will be a good decision for a small project on its
early days of development - in that case, all features can easily be
defined and QA will have some scenarios to test.
As Gema and Charlie have shown, this will not work for manual
testcases for Ubuntu on the whole. How
On Sat, Dec 10, 2011 at 7:56 PM, Gema Gomez wrote:
> Hi,
>
> I agree with Charlie, but I think it is worth discussing this idea and
> the reasons why (imo) this way of developing test cases wouldn't work
> in our case.
>
> When I was reading about this method in this thread it altogether
> remind
Hi,
I agree with Charlie, but I think it is worth discussing this idea and
the reasons why (imo) this way of developing test cases wouldn't work
in our case.
When I was reading about this method in this thread it altogether
reminded me of the days when we were trying to move the development of
Sy
On 10/12/11 13:43, Charlie Kravetz wrote:
> On Sat, 10 Dec 2011 12:35:21 +0200
> Руаньяк wrote:
>
> > Hi,
>
> > 2011/12/10 Alex Lourie :
> >> I have the following questions:
> >>
> >> 1. How long does it take to write something like that for someone
> who's not
> >> a programmer and have no idea a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 10 Dec 2011 12:35:21 +0200
Руаньяк wrote:
> Hi,
>
> 2011/12/10 Alex Lourie :
> > I have the following questions:
> >
> > 1. How long does it take to write something like that for someone who's not
> > a programmer and have no idea about Cucu
Hi,
2011/12/10 Alex Lourie :
> I have the following questions:
>
> 1. How long does it take to write something like that for someone who's not
> a programmer and have no idea about Cucumber or unit testing in general?
I guess, it should not take much time. The only rule to be followed is
'Action a
On Sat, Dec 10, 2011 at 11:44 AM, Руаньяк wrote:
> 2011/12/9 Gema Gomez :
> > +1 to brendand for putting it so clearly.
> >
> > On the other hand, I am happy to do the intellectual exercise of trying
> > to imagine what a long test case would look like with Gherkin method,
> > and figure out if i
2011/12/9 Gema Gomez :
> +1 to brendand for putting it so clearly.
>
> On the other hand, I am happy to do the intellectual exercise of trying
> to imagine what a long test case would look like with Gherkin method,
> and figure out if it would work. Can someone have a go at, let's say..
> http://te
+1 to brendand for putting it so clearly.
I am not very keen on rewriting everything twice, we should be creating
test cases that whether manual or automated, are reusable and not need
changing unless the behavior of Ubuntu changes. Otherwise, we are
shooting ourselves on the foot... we will alway
Hi all,
2011/12/9 Alex Lourie :
>
>
> On Fri, Dec 9, 2011 at 12:41 PM, Brendan Donegan
> wrote:
>>
>> Not sure I buy some of the criticisms of the ISTQB definitions, but it's
>> certainly true that Gherkin encodes the tests in such a way as to make
>> it possible for tools to parse them, whereas
On Fri, Dec 9, 2011 at 12:41 PM, Brendan Donegan <
brendan.done...@canonical.com> wrote:
> Not sure I buy some of the criticisms of the ISTQB definitions, but it's
> certainly true that Gherkin encodes the tests in such a way as to make
> it possible for tools to parse them, whereas perhaps ISTQB
Not sure I buy some of the criticisms of the ISTQB definitions, but it's
certainly true that Gherkin encodes the tests in such a way as to make
it possible for tools to parse them, whereas perhaps ISTQB definitions
don't have that. I do think the language ends up looking slightly weird
for manual t
Hi all,
After some hot debate in the mailing list about re-writing and
categorizing testcases, I've decided to propose an adoption of another
testcase DSL: Gherkin.
Current ISTQB definition doesn't seem to be elegant enough to quickly
describe the expected behavior of the system. As for me, these
14 matches
Mail list logo
