Hi, I'd like to introduce some basic tests for bg_setenv/bg_printenv.
I know that there are unit-tests (and typically I prefer them to tests like these) but nevertheless I am convinced that these kind of tests are useful: they can catch errors which unit-tests simply cannot do (e.g. linking, see our discussion here [1]. The original motivation for these tests was to test the new bg_printenv CLI options which I have implemented (but not yet submitted) and to ensure that I did not break the existing interface. Following the "upstream first" principle, I'm hereby trying to bring them upstream. Kind regards, Michael [1] https://www.mail-archive.com/[email protected]/msg01351.html Michael Adler (1): bg_setenv: added basic tests for bg_setenv CLI .github/workflows/main.yaml | 5 +- .gitmodules | 9 +++ docs/COMPILE.md | 3 +- tests/bats | 1 + tests/bg_setenv.bats | 108 +++++++++++++++++++++++++++++++++ tests/files/BGENV.DAT | Bin 0 -> 132104 bytes tests/test_helper/bats-assert | 1 + tests/test_helper/bats-support | 1 + 8 files changed, 126 insertions(+), 2 deletions(-) create mode 160000 tests/bats create mode 100755 tests/bg_setenv.bats create mode 100644 tests/files/BGENV.DAT create mode 160000 tests/test_helper/bats-assert create mode 160000 tests/test_helper/bats-support -- 2.33.0 -- You received this message because you are subscribed to the Google Groups "EFI Boot Guard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/efibootguard-dev/20211020070554.411028-1-michael.adler%40siemens.com.
