Re: [Cucumber:8918] Scenarios for foreign languages

Google's translate API can detect the language of a text. Perhaps you
could use this in your step definition. See the "Detect source
language" section here:
http://code.google.com/apis/language/translate/v2/getting_started.html.

Richard

On Wed, Aug 31, 2011 at 3:52 PM, Andy Waite <andywaite@...> wrote:
> I trying to implement tests for behaviour which goes something like
> this:
>
>  Scenario: Viewing the home page in Spanish
>
>    Given that my browser's language is set to Spanish
>    When I view the home page
>    Then all the content should be in Spanish
>
> But I'm at a loss about how best to implement the 'Then' step
> definition. Checking for particular strings in Spanish (or any other
> language) would likely make the tests very fragile.
>
> Andy
>
> --
> You received this message because you are subscribed to the Google Groups "Cukes" group.
> To post to this group, send email to cukes@...
> To unsubscribe from this group, send email to cukes+unsubscribe <at> googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/cukes?hl=en.
>
>

Re: [Cucumber:8919] Which versions of Ruby should Cucumber support?

Re: [Cucumber:8920] Which versions of Ruby should Cucumber support?

On 31 August 2011 16:49, Mike Sassak <msassak@...> wrote:
> Hello Cucumber Ruby Users,
>
> A question about the state of adoption of Ruby 1.9.x: what would you
> say if Cucumber dropped support for Ruby versions < 1.8.7? What about
> dropping support for 1.8.x entirely? How many test suites would burst
> into flames if that happened? Rails doesn't support 1.8.6 anymore, but
> I don't think many of the big Ruby projects are dropping 1.8.7 just
> yet, but one day it will happen. Please note that if anything happens
> to Cucumber in this regard, it will happen slowly and deliberately.
> You won't wake up one morning to find that all your 1.8.x suites broke
> with a bump of the tiny version number.
>
> What are your thoughts about this?
> Mike
>
> --
> You received this message because you are subscribed to the Google Groups "Cukes" group.
> To post to this group, send email to cukes@...
> To unsubscribe from this group, send email to cukes+unsubscribe@...
> For more options, visit this group at http://groups.google.com/group/cukes?hl=en.
>
>
I think a widely used testing tool like Cucumber should be expected to
work on all currently supported versions of Ruby, and I would define
"supported versions" to mean every ruby that is supported by ruby.lang
and currently to mean between now and x years ago. So cucumber drops
support later than ruby.lang. In other words it should ideally be very
conservative about dropping language support.

Assuming that this would kill development then we need a good way to
gently drop versions and leave people with a good outlet if they have
to continue using a really old cucumber. With something as serious is
dropping support for a major ruby version would forking the project
and releasing a legacy gem be a viable solution

e.g. release cucumber1.8.7 gem or a cucumber1.8.x gem

I have no idea if this is practical or sensible, but is does seem to
me that Cucumber will be very useful for working with legacy ruby and
rails projects for many years to come, and that just specifying an
older version of the gem to use is not enough for something so major
as say dropping 1.8.x support.

All best

Andrew

-- 
------------------------
Andrew Premdas
blog.andrew.premdas.org

--

-- 
You received this message because you are subscribed to the Google Groups "Cukes" group.
To post to this group, send email to cukes@...
To unsubscribe from this group, send email to cukes+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/cukes?hl=en.

Re: [Cucumber:8921] Which versions of Ruby should Cucumber support?

On Wed, Aug 31, 2011 at 11:30 PM, Eumir Gaspar
<imacaterpillar@...> wrote:
>
>
> On Thu, Sep 1, 2011 at 4:38 AM, David Kowis <dkowis@...> wrote:
>>
>> On Wed, Aug 31, 2011 at 10:49 AM, Mike Sassak <msassak@...> wrote:
>> > Hello Cucumber Ruby Users,
>> >
>> > A question about the state of adoption of Ruby 1.9.x: what would you
>> > say if Cucumber dropped support for Ruby versions < 1.8.7? What about
>> > dropping support for 1.8.x entirely? How many test suites would burst
>> > into flames if that happened? Rails doesn't support 1.8.6 anymore, but
>> > I don't think many of the big Ruby projects are dropping 1.8.7 just
>> > yet, but one day it will happen. Please note that if anything happens
>> > to Cucumber in this regard, it will happen slowly and deliberately.
>> > You won't wake up one morning to find that all your 1.8.x suites broke
>> > with a bump of the tiny version number.
>> >
>> > What are your thoughts about this?
>
> By dropping support, what do you mean? Like just ignore new bugs that are
> discovered? Or will this be more of a we all have to switch to 1.9 because
> cucumber will no longer run in 1.8? If it is the former, then I think that
> is a good thing, much like Rails did with 1.8.6. With the latter, it will be
> more troublesome with legacy apps that rely on this.
> I know that upgrading is, of course, for the better, but what about
> companies that don't have the budget for that? You can't just say "Sorry,
> but we have to charge you more since we'll have to migrate our test suite to
> 1.9...unless you don't want tests" or something to clients, right?
> In any case, I think that you just mean not thinking about 1.8 when creating
> new features and ignoring any new bugs so I guess that's all right. Just my
> two cents :)

Hi Eumir,

To clarify: there is no possibility I can see of Cucumber dropping
support for 1.8.x in the 1.x series. The code has already been
written, after all, and it would be silly to remove it. Neither do I
think anyone would just start ignoring patches for 1.x, or fail to fix
serious problems or regressions in its behavior. That doesn't serve
anyone well. For new major versions with new code and features,
however, the situation is potentially different.

Mike

> --
> Eumir Gaspar
> Ruby on Rails Developer/Rails UI Specialist
> github: http://github.com/corroded
> tech blog: http://aelogica.com/author/eumir/
> odesk: http://www.odesk.com/users/~~8951a3b425021bda
> stackoverflow: http://stackoverflow.com/users/334545/corroded
> working with
> rails: http://www.workingwithrails.com/person/19554-eumir-gaspar
> linked in: http://ph.linkedin.com/pub/eumir-gaspar/7/969/98a
>
> --
> You received this message because you are subscribed to the Google Groups
> "Cukes" group.
> To post to this group, send email to cukes@...
> To unsubscribe from this group, send email to
> cukes+unsubscribe@...
> For more options, visit this group at
> http://groups.google.com/group/cukes?hl=en.
>

--

-- 
You received this message because you are subscribed to the Google Groups "Cukes" group.
To post to this group, send email to cukes@...
To unsubscribe from this group, send email to cukes+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/cukes?hl=en.

[Cucumber:8922] running specific wip scenario

I would like to run only one  javascript scenario as wip, what
cucumber command should I use ?

I tried  cucumber:wip    , placing both tags    <at> wip,  <at> javascript
before the scenario , doesn't seems to work ..

Feature: feature-A
  In order to ...
  A user should be able to ....

     <at> javascript,  <at> wip
    Scenario: 1- User ......
      Given I am authenticated ...
      When ....
      Then ....

     <at> javascript
    Scenario: 2- User ......
      Given I am authenticated ...
      When ....
      Then ....

     <at> javascript
    Scenario: 3-User ......
      Given I am authenticated ...
      When ....
      Then ....

--

-- 
You received this message because you are subscribed to the Google Groups "Cukes" group.
To post to this group, send email to cukes@...
To unsubscribe from this group, send email to cukes+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/cukes?hl=en.

Re: [Cucumber:8923] [wire] Issue with scenario outline with background but without examples

Re: [Cucumber:8924] [wire] Issue with scenario outline with background but without examples

Re: [Cucumber:8926] Cucumber-JVM: Tags and the commandline

[Cucumber:8926] Cucumber-JVM: Dependency injection in step implementations

With cuce4duke it was possible to define step-definition-classes that
had constructors with arguments.
The runtime then injected the necessary arguments into the step
definition.

Example:
https://github.com/cucumber/cuke4duke/blob/master/examples/java-ejb3/src/test/java/org/books/test/acceptance/SearchSteps.java

Is this still a desired feature in cucumber-JVM?

I would like to work on that feature. What would be the approach?
1. Create & grab a ticket
2. Send a pull request

As far as I have seen, for step definitions in java this would be
implemented starting from the JavaBackend:
https://github.com/cucumber/cucumber-jvm/blob/master/java/src/main/java/cucumber/runtime/java/JavaBackend.java

But that would mean that this feature has to be implemented explicitly
for each language... which is probably unavoidable ... or am I missing
something?

--

-- 
You received this message because you are subscribed to the Google Groups "Cukes" group.
To post to this group, send email to cukes@...
To unsubscribe from this group, send email to cukes+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/cukes?hl=en.

[Cucumber:8927] Cucumber-JVM: How-To work on new features?

I am currently diving into the cucumber-JVM implementation.

I just wanted to ask how to get the most pleasant development
experience.

My approach so far was:

1. Make a change in cucumber-jvm (core or language backend ...)
2. run mvn clean install
3. run an example that is using cucumber-jvm (i.e. the java-calulator
or java-webbit-websockets-selenium ...)

I wanted to know if there is a way to remove step 2 from the feedback
cycle?

How do you guys work on new features?

--

-- 
You received this message because you are subscribed to the Google Groups "Cukes" group.
To post to this group, send email to cukes@...
To unsubscribe from this group, send email to cukes+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/cukes?hl=en.