Support for French Definitions

Hi,

My manager wants me to describe the tests in French. We have some tests in French that we’ve done with cucumber and selenium js

#language: fr

Fonctionnalité: Filtrer la liste de contenus par type de contenu

  Scénario: L'option du filtre Type de contenu est présent
    Etant donné qu'on est dans la liste de contenus
    Alors le filtre Type de contenu est visible
    Et les valeurs disponibles du filtres Type de contenu sont sélectionnable

It works fine in seleniumjs. This is a step_definition that we have

this.Given(/^le service de contenus est disponible$/, function () {
        return driver.get(shared.env.baseUrl);
    });

However, when I use this .feature file and create the definition steps, cypress does not recognize the tests. I get Error: Step implementation missing for: on est dans la liste de contenus

If I change the French keywords to English it works fine. Is there something I can do to have the step definitions in French?

Thanks

[mathieutu]

Sure. I don’t know an example of what, but here is a part of a feature, with the corresponding simplified selectors :

#language: fr
Fonctionnalité: Appel téléphonique

  Lorsqu'un client appel à l'agence, le téléphone ouvre automatiquement une page dans le navigateur avec le numéro de la
  personne qui appelle. Ce numéro doit ensuite servir à identifier si le client existe déjà et afficher le contact.

  Scénario: Client connu

    Lorsque je visite la page "/contacts?telephone=0123456789"
    Alors je dois lire "01 23 45 67 89" dans le "téléphone du contact"
    Et je dois lire "M. Doe John" dans le "nom complet du contact"
    Et je dois lire "[e-mail]" dans l'"email du contact"

When(/^je visite la page "(.*)"$/, pageUrl => {
  cy.visit(pageUrl);
});

Then(/^je dois lire "(.*)" dans (?:le |la |l'|les )"(.*)"$/, (text, name) => {
  cy.get(getSelector(name)).should('contain', text)
});

[badeball]

Due to personal reasons, the previous maintainers of this package are stepping down and handing the reigns over to me, a long-time contributor to the project and a user of it myself. This is a responsibility I’m very excited about. Furthermore, I’d like to thank @lgandecki ++ for all the work that they’ve done so far.

Read more about the transfer of ownership here.

The repository has however moved and all outstanding issues are being closed. This is not a reflection of the perceived importance of your reported issue. However, if after upgrading to the new version, you still find there to be an issue, feel free to open up another ticket or comment below. Please make sure to read CONTRIBUTING.md before doing so.