summaryrefslogtreecommitdiff
path: root/tests/vb2_ui_action_tests.c
diff options
context:
space:
mode:
authorHsuan Ting Chen <roccochen@chromium.org>2020-05-27 15:03:43 +0800
committerCommit Bot <commit-bot@chromium.org>2020-05-30 17:12:42 +0000
commitccb0f595f353154ad38a2f64cf038cfdc472291c (patch)
tree8f5c5c4c1e37be2a4e6a2303354bb03c6c8df270 /tests/vb2_ui_action_tests.c
parent5e3b9473173ea452e298d8424b3e5db2e48bcb4a (diff)
downloadvboot-ccb0f595f353154ad38a2f64cf038cfdc472291c.tar.gz
vboot/ui: Synchronize mock inputs for vb2_ui_tests
We have two different mock inputs currently, and soon to be three. Since the input-solving order should not be strictly defined, it is difficult to write complicated scenarios under current approach. We cannot make sure if the ui_loop implementation exits earlier and ignores certain mock inputs. This CL synchronizes mock inputs with an iteration counter. We can write detailed scenarios by assigning the inputs iter-by-iter. BUG=b:146399181, b:156448738 TEST=make clean && make runtests TEST=make clean && DETACHABLE=1; make runtests TEST=make clean && PHYSICAL_PRESENCE_KEYBOARD=1; make runtests BRANCH=none Signed-off-by: Hsuan Ting Chen <roccochen@chromium.org> Change-Id: Ia839a6614eb0453b9f64075298a89a2db59d4070 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/vboot_reference/+/2217532 Reviewed-by: Yu-Ping Wu <yupingso@chromium.org> Commit-Queue: Yu-Ping Wu <yupingso@chromium.org>
Diffstat (limited to 'tests/vb2_ui_action_tests.c')
0 files changed, 0 insertions, 0 deletions