views:

44

answers:

2

i like cucmber stories. they just look great. I am trying to find a way to use them in my daily work as a projet manager / developer / tester / analyst (you name it :p).

problem ? my clients speak french only. No english.

i see that cucumber seems to support 40 languages (wow!) => http://wiki.github.com/aslakhellesoy/cucumber/spoken-languages

does anyone have examples in french or other recommandations to write stories in french ? any kind of feedback regarding this ?

A: 

Cucumbers includes examples in a number of languages. Check out http://github.com/aslakhellesoy/cucumber/blob/master/examples/i18n/fr/features/addition.feature for example.

Jason Noble
nice. as is the resulting file seems a bit clumsy, kinda not so natural (compared to what it sounds/feels in english). have you actually tried it in a fr project ? (or in another language anyway?)
No, I haven't, I speak English and Ruby. :)
Jason Noble
A: 

I have two stories I would like to share

The Swedish-English Cucumber Cocktail
Last year I was working in a project where we were writing stories that used a mix of Swedish and English. Scripts in English but test subject was in Swedish.

Feature: Search
  In order to make sure people can find my documentation
  I want to check it is listed on the first page in results

  Scenario: Search for åäö
    Given I have opened search page
    When I search for "åäö"
    Then I should see a link to document called "åäö_test_document"

We had a lot of trouble in the beginning, even raising an issue to the Cucumber community. But after an update the issue was fixed and it since worked like a charm.

Link to Issue
https://rspec.lighthouseapp.com/projects/16211/tickets/506-cucumber-windows-swedish-characters

The Cucumberless Cocktail
In another product we started using Cucumber but after a few weeks a tinkering we dropped it and stopped using it and used a Grails-JUnit-Maven solution instead.

Alot of my colleagues (not working in this project) critised us for doing this, since "Cucumber is so good", "Cucumber is so easy to read and write". I had to tell them, over and over, that the reason we dropped cucumber was NOT because it wasn't working. It was working great.

The reason we dropped it was that the whole point, IMHO, of using Cucumber is to add an extra easy-readable layer on top of you tests so that your client can read and write tests. Our client couldn't care less about our tests. And we developers/testers were happy writing JUNIT and we didn't need that extra layer. So we couldn't see any reason for adding that extra layer.

What I am trying to say to you is:
Are your clients really going to read your tests and write their own? If not, if YOU still want the cucumber scripts, write them in english and skip the french. Or drop the extra layer like we did and use Ruby/Rails excellent inbuilt testing framework.

Hope this helps

Jonas Söderström
yes it does help. It is probably too much to ask my client to write the cuccumber scenarios from scratch. However, during meetings if i show them those scenarios, they will understand them crystal clear. Meeting after meeting, they might even be tempted to write/modify thei own and it would help writing them in real time with them.Besides, at this point, there is no "specification document". And i know they will want one. So instead of maintaining both a stupid word doc and some tests to reflect the word doc. maybe they would agree to stick to cuccumber as the spec reference