u-boot.git/include/test/cedit-test.h, branch next Unnamed repository; edit this file 'description' to name the repository. expo: Use standard numbering for save and discard 2024-10-18T20:10:22+00:00 Simon Glass sjg@chromium.org 2024-10-14T22:31:57+00:00 d8ff97ce91529263c9d82a4bc00e133822673ab0 Set aside some expo IDs for 'save' and 'discard' buttons. This avoids needing to store the IDs for these. Adjust the documentation and expo tool for the new EXPOID_BASE_ID value. Ignore these objects when saving and loading the cedit, since they do not contain real data. Adjust 'cedit run' to return failure when the user exits the expo without saving. Update the test for this change as well. Signed-off-by: Simon Glass <sjg@chromium.org> 
Set aside some expo IDs for 'save' and 'discard' buttons. This avoids
needing to store the IDs for these. Adjust the documentation and expo
tool for the new EXPOID_BASE_ID value.

Ignore these objects when saving and loading the cedit, since they do
not contain real data.

Adjust 'cedit run' to return failure when the user exits the expo
without saving. Update the test for this change as well.

Signed-off-by: Simon Glass <sjg@chromium.org>
expo: Update tests to include textline 2023-10-11T19:43:55+00:00 Simon Glass sjg@chromium.org 2023-10-02T01:13:39+00:00 c2bd2d33d92cf729dfa7bac6c4c754098f0a2dfb Provide test coverage for the new expo object type, including building and reading/writing settings. Signed-off-by: Simon Glass <sjg@chromium.org> 
Provide test coverage for the new expo object type, including building
and reading/writing settings.

Signed-off-by: Simon Glass <sjg@chromium.org>
expo: Support building an expo from a description file 2023-07-14T16:54:51+00:00 Simon Glass sjg@chromium.org 2023-06-01T16:23:01+00:00 82cafee133ee5c087449761988c096fc26a17cf6 The only way to create an expo at present is by calling the functions to create each object. It is useful to have more data-driven approach, where the objects can be specified in a suitable file format and created from that. This makes testing easier as well. Add support for describing an expo in a devicetree node. This allows more complex tests to be set up, as well as providing an easier format for users. It also provides a better basis for the upcoming configuration editor. Signed-off-by: Simon Glass <sjg@chromium.org> 
The only way to create an expo at present is by calling the functions to
create each object. It is useful to have more data-driven approach, where
the objects can be specified in a suitable file format and created from
that. This makes testing easier as well.

Add support for describing an expo in a devicetree node. This allows more
complex tests to be set up, as well as providing an easier format for
users. It also provides a better basis for the upcoming configuration
editor.

Signed-off-by: Simon Glass <sjg@chromium.org>