You could create /sys/firmware/efi/efivars/ tarballs of a bunch of real systems with the properties that you want, keep them in the tests, and unpack these in your test cases. You most probably just need a few of them, so you can strip them down or possibly create them individually as files, but a full tarball might be the quickest start.
FTR, I would strongly advise against that, see https:/ /github. com/martinpitt/ umockdev/ issues/ 110#issuecommen t-736224503 . You want the tests to work independently on the hardware it's running on, so that you can run it on e.g. standard autopkgtest infra.
You could create /sys/firmware/ efi/efivars/ tarballs of a bunch of real systems with the properties that you want, keep them in the tests, and unpack these in your test cases. You most probably just need a few of them, so you can strip them down or possibly create them individually as files, but a full tarball might be the quickest start.