简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
AaronAllen0262 · 2026年2月25日 12:12 UTC
Have you got a saved failure response as well as a success, because I would start by making the screen tell those apart before collecting a museum of edge cases
22分Yes, an accepted coupon and a rejected coupon from the same application version; the programmer says the stand-in bypasses the parsing code, which explains a lot
2分Then test through the parser. A mock taking a shortcut around the broken bit is just a second application with better manners.
10分Our packing demo once showed the result of the previous carton, so does your rejected response actually change the displayed coupon identity as well as the colour?
0分Keep an example with no result too, Aaron, since that was the case that first bothered you.
20分The saved reject exposed it: our wrapper tests whether the response has contents, then treats that as acceptance, without reading the result field; the reject response has contents too, obviously
18分Expensive way to ask whether a box contains paper, that
10分What does the corrected code do with an unrecognised result value? Don't let an else branch quietly become another green lamp.
11分It reports an unreadable result and leaves acceptance unset; the programmer added a test with an unrecognised value as well as the captured accept and reject, but has not checked the display identity yet
17分Please do the identity check, Aaron, especially if a coupon result can arrive while another coupon is already selected on screen.
19分Callum, would you include reopening the screen with no new response, so an old colour cannot sneak back in from saved display state?
0分Yes, that is close to what caught us, though ours happened when changing cartons rather than reopening the screen.
0分We added reject_after_accept, empty_response and reopen_without_result to the application tests, plus a response for the wrong coupon; the first three now pass, but the wrong-coupon case revealed that the heading changes before the old result is removed
8分Good find. Does the export have the same old-result problem?
21分The export already used the response's coupon identity correctly; we fixed the display reset and the wrong-coupon test now leaves the selected coupon pending, with the other response listed against its own identity, and all five saved-response cases pass through the normal parser and screen code
7分That's a useful bit of work while the bench is unavailable, and considerably more convincing than true with a cheerful face
3分