Design Lab
Design it, then prove it
One workspace for the three kinds of proving this platform needs: a part bench for the hardware, a screen-flow designer that writes its own test suite, and an acceptance check that scores a spec against its bands.
Screen flow and test suite
Screen flow
1
2
3
Generated test suite
0% passed · 0/13 cases
- Happy pathSign in loads with its empty state and no console errors
- ValidationSign in blocks submission while required fields are empty
- ErrorSign in shows a retry when its request fails
- AccessSign in is unreachable for a signed-out visitor
- Happy pathChoose a portal loads with its empty state and no console errors
- ValidationChoose a portal blocks submission while required fields are empty
- StateGoing back from Choose a portal keeps the values entered on Sign in
- ErrorChoose a portal shows a retry when its request fails
- Happy pathConfirm purchase loads with its empty state and no console errors
- ValidationConfirm purchase blocks submission while required fields are empty
- StateGoing back from Confirm purchase keeps the values entered on Choose a portal
- ErrorConfirm purchase shows a retry when its request fails
- AccessConfirm purchase is unreachable for a signed-out visitor
Cases are derived from the flow above: change a screen, a data dependency or an access rule, and the suite changes with it. Ticking a case records a pass for this session only.