feature685 B

Gherkin — French Keywords (# language: fr)

A feature written entirely in French keywords, declared by the # language: fr header that must be the first line of the file. Parsers that hardcode English keywords read this as a feature with no scenarios rather than reporting an error, so it fails silently.

Internationalization Code parsing Encoding detection

Preview — first 24 linesfeature

# language: fr
@panier
Fonctionnalité: Total du panier

  Contexte:
    Etant donné que le taux de TVA est de 20 pour cent

  Scénario: Un panier avec un seul article affiche la TVA
    Etant donné que mon panier est vide
    Quand j'ajoute 1 article "NX-1042"
    Alors le sous-total est "12.99"
    Et la TVA est "2.60"
    Et le total est "15.59"

  Plan du Scénario: La quantité multiplie le sous-total
    Etant donné que mon panier est vide
    Quand j'ajoute <quantite> articles "<sku>"
    Alors le sous-total est "<sous_total>"

    Exemples:
      | sku     | quantite | sous_total |
      | NX-1042 |        1 |      12.99 |
      | NX-1042 |        3 |      38.97 |

Specifications

Seed: 61200
Encoding: UTF-8
Line Endings: LF
Gherkin Dialect: fr
Language: fr
Scenarios: 1
Scenario Outlines: 1
Example Rows: 2
Keywords: Fonctionnalité, Contexte, Scénario, Plan du Scénario, Exemples
Non Ascii Keywords: true

Testing contract

Expected to pass

Scenario: Parse a Gherkin feature whose keywords come from a non-English dialect.
Expected result: The language header selects the fr keyword set, yielding one Scénario and one Plan du Scénario that expands to two scenarios.

What is a .feature file?

A .feature file holds a Gherkin specification: a business-readable, plain-text description of behaviour written as Feature, Background, Scenario, and Scenario Outline blocks whose steps begin with Given, When, Then, And, or But. Scenario Outlines are parameterised by an Examples table, and tags such as @smoke mark subsets of the suite. Cucumber, Behave, SpecFlow, and Behat all read the same grammar, with localised keyword sets available for non-English specifications.

How to use this file

Use an example .feature file to test Gherkin parsers, step-definition matchers, linters, and editor tooling — verifying tag inheritance, Scenario Outline expansion against the Examples table, docstring and data-table arguments, and behaviour on deliberately malformed keywords.

How to use this file for testing

“Gherkin — French Keywords (# language: fr)” is a deterministic Novus Examples fixture for Internationalization, Code parsing, Encoding detection. Parallel text and accented, multi-script content — for testing translation pipelines, Unicode handling, and localization tooling.

Documented properties for this file: seed 61200 · fr · UTF-8 · LF. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

Test and coverage reports document their totals (suites, cases, passes, failures, skips, covered lines) in the spec table. Point your CI dashboard, coverage gate, or report converter at the file and assert those counts survive; format twins carry identical numbers so a conversion can be scored exactly.

Load the catalog with your i18n framework and verify placeholder interpolation and plural handling; the RTL and CJK variants exercise bidirectional text and font fallback.