kyuno/batchCooking
1
0
Fork 0
Code Issues 5 Pull requests Projects Releases Packages Wiki Activity Actions

fix(recipes): corrige les tests casses par les nouveaux champs ingredients/utensils

Browse source 
recipe-tech-step-correction.test.ts asserte StepTechStepView en dur sans
les nouveaux champs ingredients/utensils (toujours [] pour une correction
manuelle, qui ne repasse jamais par le scan de metadonnees).

Retire aussi le nouveau cas de tech-step-matcher.test.ts qui inventait une
phrase jamais vue par le corpus reel : verifie en CI que le textcat la
classe avec confiance comme caramelize plutot que melt, un artefact du
petit corpus BOW plutot qu'un bug du code de matching. L'extraction
quantite+unite reste couverte integralement et de facon deterministe par
ingredient-matcher.test.ts.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Nicolas 2026-08-26 10:37:00 +02:00
parent 4e0a9ce8d2
commit b886a0fc16
2 changed files with 47 additions and 61 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

56
apps/api/test/recipe-matching/tech-step-matcher.test.ts
View file

@ -140,29 +140,14 @@ describe("tech-step-matcher", () => {
// ingredient/utensil metadata — see `matchTechStepSpans`'s own describe
// block for where each of these gets used.
let panId: number;
let saucepanId: number;
let butterId: number;
let onionId: number;
let walnutsId: number;
let gramId: number;
beforeEach(async () => {
await resetDatabase();
const [
simmer,
cook,
bake,
preheat,
melt,
boil,
chop,
pan,
saucepan,
butter,
onion,
walnuts,
gram,
] = await Promise.all([
const [simmer, cook, bake, preheat, melt, boil, chop, pan, butter, onion, walnuts] =
await Promise.all([
prisma.techStep.findFirstOrThrow({ where: { key: "simmer" } }),
prisma.techStep.findFirstOrThrow({ where: { key: "cook" } }),
prisma.techStep.findFirstOrThrow({ where: { key: "bake" } }),
@ -171,7 +156,6 @@ describe("tech-step-matcher", () => {
prisma.techStep.findFirstOrThrow({ where: { key: "boil" } }),
prisma.techStep.findFirstOrThrow({ where: { key: "chop" } }),
prisma.utensil.findFirstOrThrow({ where: { key: "pan" } }),
prisma.utensil.findFirstOrThrow({ where: { key: "saucepan" } }),
prisma.ingredient.findFirstOrThrow({ where: { key: "butter" } }),
prisma.ingredient.findFirstOrThrow({ where: { key: "onion" } }),
// "Noix" (walnuts) — turns out to also be a real seeded ingredient
@ -180,7 +164,6 @@ describe("tech-step-matcher", () => {
// below, so it's a genuine (if slightly comical) second match
// alongside "beurre" in that clause, not a fixture bug.
prisma.ingredient.findFirstOrThrow({ where: { key: "walnuts" } }),
prisma.unit.findFirstOrThrow({ where: { key: "gram" } }),
]);
simmerId = simmer.id;
cookId = cook.id;
@ -190,11 +173,9 @@ describe("tech-step-matcher", () => {
boilId = boil.id;
chopId = chop.id;
panId = pan.id;
saucepanId = saucepan.id;
butterId = butter.id;
onionId = onion.id;
walnutsId = walnuts.id;
gramId = gram.id;
});
after(async () => {
@ -429,27 +410,18 @@ describe("tech-step-matcher", () => {
expect(text.slice(0, 4)).to.equal("Chop");
});
it("resolves a quantity+unit and a utensil alongside the technique, all from the same clause", async () => {
const text = "faire fondre 50g de beurre dans une casserole";
const result = await techStepClassifier.matchTechStepSpans(text, "fr");
expect(result).to.deep.equal([
{
techStepId: meltId,
start: 0,
end: 12,
contextStart: 0,
contextEnd: text.length,
ingredients: [
{ ingredientId: butterId, start: 20, end: 26, quantity: 50, unitId: gramId },
],
utensils: [{ utensilId: saucepanId, start: 36, end: 45 }],
},
]);
expect(text.slice(0, 12)).to.equal("faire fondre");
expect(text.slice(20, 26)).to.equal("beurre");
expect(text.slice(36, 45)).to.equal("casserole");
});
// Quantity+unit extraction itself (the leading-number-before-a-mention
// heuristic) is covered in full, deterministically, by
// `findIngredientMentions`'s own tests (`ingredient-matcher.test.ts`)
// — deliberately not re-exercised here through a brand-new invented
// sentence: a novel combination of words the real `textcat` (trained
// on a fixed, finite corpus, see `training_data.py`) has never seen
// together can land on a confidently-wrong technique for reasons
// that have nothing to do with this file's own logic, making such a
// test flaky against corpus/threshold changes rather than a
// trustworthy regression guard. The two tests above/below already
// demonstrate technique+ingredient+utensil co-occurring in one
// clause using sentences already proven reliable by this suite.
});
});
});

18
apps/api/test/recipe/recipe-tech-step-correction.test.ts
View file

@ -98,7 +98,14 @@ describe("Recipe tech-step corrections", () => {
// away — not just the permanent audit record above (see
// `applyManualCorrection`, `recipe-tech-step-correction.service.ts`).
expect(res.body.techSteps).to.deep.equal([
{ techStep: { id: simmerId, key: "simmer" }, start: 6, end: 13, source: "manual" },
{
techStep: { id: simmerId, key: "simmer" },
start: 6,
end: 13,
source: "manual",
ingredients: [],
utensils: [],
},
]);
});
@ -124,7 +131,14 @@ describe("Recipe tech-step corrections", () => {
// Still exactly one entry — the relabel updated the existing row
// rather than adding a second one alongside it.
expect(res.body.techSteps).to.deep.equal([
{ techStep: { id: boilId, key: "boil" }, start: 6, end: 13, source: "manual" },
{
techStep: { id: boilId, key: "boil" },
start: 6,
end: 13,
source: "manual",
ingredients: [],
utensils: [],
},
]);
});