Nicolas
20d52aee2d
Les tests e2e (apps/web/cypress/e2e/) étaient de simples specs Cypress (.cy.ts), sans lien avec Cucumber alors qu'apps/api utilise déjà Gherkin pour ses propres tests BDD. Intègre @badeball/cypress-cucumber-preprocessor pour écrire les scénarios utilisateurs en Gherkin des deux côtés, même vocabulaire. - cypress.config.ts : specPattern sur *.feature, wiring du préprocesseur (esbuild bundler + plugin cucumber) - Les 11 fichiers .cy.ts sont remplacés par des paires .feature/.steps.ts (co-localisées, même nom) — conversion complète, comportement équivalent (mêmes intercepts, mêmes assertions) - cypress/support/step_definitions/common.steps.ts : steps partagés entre features (connexion, navigation, assertions génériques de texte/URL/champ) — globaux à toute la suite, réutilisables tels quels - cypress/support/profile.ts : profil du compte "connecté" courant, assemblé au fil de plusieurs Given avant le premier visit/When - README : nouvelle section "Cucumber (apps/web)" (miroir de la section existante pour apps/api), mise à jour des références aux anciens noms de fichiers .cy.ts (déjà obsolètes avant ce changement) Vérification : impossible d'exécuter Cypress dans cet environnement (crash Electron/GPU au lancement, limitation déjà documentée dans le README — reproductible sur main, indépendante de ce changement). À la place : - les 447 steps Gherkin des 11 .feature ont été vérifiés programmatiquement contre les 165 patterns de step enregistrés : 0 non résolu, 0 ambigu - les 11 .feature parsent correctement avec le parser Gherkin officiel (57 scénarios au total) - tous les .steps.ts passent `biome check` (syntaxe + style) sans erreur - CYPRESS_INSTALL_BINARY déjà géré (voir PR précédente) — le binaire est bien présent localement (`cypress verify` OK), donc le blocage est spécifiquement le sandbox GPU de cet environnement, pas l'installation La vraie exécution reste à vérifier via le job `e2e` de la CI GitHub Actions sur cette PR — c'est le chemin déjà documenté dans le README pour cet environnement précis.
67 lines
3.1 KiB
Gherkin
67 lines
3.1 KiB
Gherkin
Feature: Onboarding wizard
|
|
As a newly signed-up user
|
|
I want to set my diet, household, and allergens
|
|
So that my profile is ready before I start planning meals
|
|
|
|
Background:
|
|
Given the planning request returns nothing
|
|
|
|
Scenario: Walks through all three steps, creating a household on the way, and lands on the home page
|
|
Given the diets reference list has options
|
|
And selecting the diet will succeed
|
|
And the household request returns no household
|
|
And creating a household will succeed
|
|
And the allergies reference list has options
|
|
And updating allergies will succeed
|
|
And I have signed up
|
|
Then the URL should include "/onboarding/regime"
|
|
And I should see "Étape 1 sur 3"
|
|
When I select "Végétarien" from the "diet" field
|
|
And I click the button "Continuer"
|
|
Then the diet update request should have been made with diet id 2
|
|
And the URL should include "/onboarding/foyer"
|
|
And I should see "Étape 2 sur 3"
|
|
When I fill in the "houseName" field with "Chez Alice"
|
|
And I click the button "Créer"
|
|
Then the household creation request should have been made with name "Chez Alice"
|
|
And the URL should include "/onboarding/allergenes"
|
|
And I should see "Étape 3 sur 3"
|
|
And I should see the section "Allergies"
|
|
And I should see the section "Intolérances"
|
|
When I check the checkbox "Arachides"
|
|
And I click the button "Terminer"
|
|
Then the allergies update request should have been made with allergy id 1
|
|
And the URL should be the home page
|
|
And I should see the heading "Planning de la semaine"
|
|
|
|
Scenario: Lets the regime and allergens steps be skipped without changing anything
|
|
Given the diets reference list is empty
|
|
And selecting the diet will succeed
|
|
And the household request returns no household
|
|
And the allergies reference list is empty
|
|
And updating allergies will succeed
|
|
And I have signed up
|
|
Then the URL should include "/onboarding/regime"
|
|
When I click the button "Continuer"
|
|
Then the diet update request should have been made with no diet id
|
|
And the URL should include "/onboarding/foyer"
|
|
When I click the button "Passer cette étape"
|
|
Then the URL should include "/onboarding/allergenes"
|
|
When I click the button "Terminer"
|
|
Then the allergies update request should have been made with no allergy ids
|
|
And the URL should be the home page
|
|
|
|
Scenario: Lets the household step be completed by joining an existing household instead of creating one
|
|
Given the diets reference list is empty
|
|
And selecting the diet will succeed
|
|
And the household request returns no household
|
|
And joining a household will succeed
|
|
And the allergies reference list is empty
|
|
And updating allergies will succeed
|
|
And I have signed up
|
|
When I click the button "Continuer"
|
|
Then the URL should include "/onboarding/foyer"
|
|
When I fill in the "inviteCode" field with "abcd2345"
|
|
And I click the button "Rejoindre"
|
|
Then the household join request should have been made with invite code "ABCD2345"
|
|
And the URL should include "/onboarding/allergenes"
|