mirror of
https://github.com/Tria-plc/edr-platform.git
synced 2026-08-26 18:42:49 +00:00
b356433886
The onboarding journey had been failing at the company step for a while: that step was restructured into StepSection cards, so its TIN and VAT fields no longer have <label> elements and the label-based fill() helper could not find them. Match on aria-label instead, which also sidesteps the "0012345678" placeholder both fields share. Two further staleness bugs were hiding behind that one, both in fill() itself. It chained clear() into type() on a subject captured beforehand, so a step-persist PATCH resolving between the two detached it; and re-querying by the captured id was no better, because the fields remount rather than re-render and Mantine mints a fresh generated id when they do. Resolve label -> for -> element afresh for each action. fillPhone gets the same treatment. Tighten what the journey proves about Fayda. It verified out-of-band and then never checked the result reached the UI, so assert the panel renders fayda-mock's own payload — name, phone and email — which only holds if it travelled Fayda -> API -> UI, and cross-check ownerFaydaSub on the company, since that sub is what locks the owner's fields server-side. The PoA step now asserts no file input exists while the PoA is unverified, covering the DARS gating; asserted structurally so rewording the document setting cannot turn a regression into a passing test.