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.
69 lines
3.6 KiB
Gherkin
69 lines
3.6 KiB
Gherkin
Feature: Recipe form — associating ingredients
|
|
As a signed-in user
|
|
I want to build a recipe by picking ingredients, quantities, and steps
|
|
So that I can save a complete recipe in one form
|
|
|
|
Background:
|
|
Given I am signed in as "Alice" "Martin"
|
|
And my household id is 1
|
|
And the ingredient/diet catalog is available
|
|
|
|
Scenario: Adds an ingredient from the picker, fills its quantity/unit, and creates the recipe
|
|
Given creating the recipe will succeed and return id 42
|
|
When I visit "/recettes/nouvelle"
|
|
And I fill in the "recipe-name" field with "Salade de tomates"
|
|
And I search the ingredient picker for "tomat"
|
|
And I select the ingredient "Tomate" from the picker
|
|
Then the ingredient "Tomate" should no longer be in the picker
|
|
And the recipe should include the ingredient "Tomate"
|
|
When I fill in the ingredient's quantity with "3" and unit "unité"
|
|
And I add a step
|
|
And I fill in the step description with "Couper les tomates."
|
|
Then the "Enregistrer" button should not be disabled
|
|
When I click the button "Enregistrer"
|
|
Then the recipe creation request should have included name "Salade de tomates" and ingredient 1 with quantity 3 and unit "unité"
|
|
And the URL should include "/recettes/42"
|
|
|
|
# Regression test for the exact bug reported: `crypto.randomUUID()` (used
|
|
# to mint each ingredient/step draft's client-only React key) throws
|
|
# outside a secure context — https, or literally the hostname `localhost`
|
|
# — so a LAN IP during on-device testing or a Capacitor WebView's
|
|
# `capacitor://` origin hit a black screen with "TypeError:
|
|
# crypto.randomUUID is not a function" the instant an ingredient was
|
|
# added. Cypress's own origin is secure, so this forces the same failure
|
|
# by deleting `crypto.randomUUID` before the app boots — see
|
|
# `apps/web/src/lib/client-key.ts`, which replaced it.
|
|
Scenario: Still works when crypto.randomUUID is unavailable (insecure-context regression)
|
|
When I visit the new recipe form without a secure random UUID
|
|
And I fill in the "recipe-name" field with "Recette hors contexte sécurisé"
|
|
And I select the ingredient "Tomate" from the picker
|
|
And I select the ingredient "Œuf" from the picker
|
|
Then there should be 2 ingredient rows
|
|
And the recipe should include the ingredient "Tomate"
|
|
And the recipe should include the ingredient "Œuf"
|
|
When I add a step
|
|
And I add a step
|
|
Then there should be 2 step editor items
|
|
|
|
Scenario: Excludes an already-selected ingredient from the picker, and removing it brings it back
|
|
When I visit "/recettes/nouvelle"
|
|
And I select the ingredient "Carotte" from the picker
|
|
Then the ingredient "Carotte" should no longer be in the picker
|
|
When I remove the ingredient "Carotte" from the recipe
|
|
Then the ingredient "Carotte" should be visible in the picker
|
|
And there should be 0 ingredient rows
|
|
|
|
Scenario: Preloads an existing recipe's ingredients when editing, and lets you add another
|
|
Given recipe 7 exists with an egg omelette
|
|
And updating recipe 7 will succeed
|
|
When I visit "/recettes/7/modifier"
|
|
Then the recipe should include the ingredient "Œuf"
|
|
And the ingredient's quantity should be "3"
|
|
When I select the ingredient "Tomate" from the picker
|
|
Then there should be 2 ingredient rows
|
|
When I fill in the last ingredient's quantity with "1" and unit "unité"
|
|
And I click the button "Enregistrer"
|
|
Then the recipe update request should have included these ingredients:
|
|
| ingredientId | quantity | unit |
|
|
| 2 | 3 | unité |
|
|
| 1 | 1 | unité |
|