summaryrefslogtreecommitdiffstats
path: root/OvmfPkg
diff options
context:
space:
mode:
authorKun Qin <kuqin12@gmail.com>2023-03-17 11:01:23 -0700
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>2023-07-20 20:20:42 +0000
commitc6b512962e92ae54a895bdfd2147abaf2c9e3e22 (patch)
treef67cad7c89d9a90c08b6f156404887f33fb193a5 /OvmfPkg
parentb2de9ec5a759aa4a7ac029cda9079dce077bf856 (diff)
downloadedk2-c6b512962e92ae54a895bdfd2147abaf2c9e3e22.tar.gz
edk2-c6b512962e92ae54a895bdfd2147abaf2c9e3e22.tar.bz2
edk2-c6b512962e92ae54a895bdfd2147abaf2c9e3e22.zip
UnitTestFrameworkPkg: UnitTestPersistenceLib: Save Unit Test Cache Option
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4467 Current implementation of UnitTestFrameworkPkg for shell-based unit test will save the unit test cache to the same volume as the test application itself. This works as long as the test application is on a writable volume, such as USB or EFI partition. Instead of saving the files to the same file system of unit test application, this change will save the cache file to the path where the user ran this test application. This change then added an input argument to allow user to specify where to save such cache file through `--CachePath` shell argument to allow even more flexibility. This change was tested on proprietary physical hardware platforms and QEMU based virtual platform. Cc: Sean Brogan <sean.brogan@microsoft.com> Cc: Michael Kubacki <mikuback@linux.microsoft.com> Cc: Michael D Kinney <michael.d.kinney@intel.com> Signed-off-by: Kun Qin <kuqin12@gmail.com> Reviewed-by: Michael Kubacki <michael.kubacki@microsoft.com> Reviewed-by: Michael D Kinney <michael.d.kinney@intel.com>
Diffstat (limited to 'OvmfPkg')
0 files changed, 0 insertions, 0 deletions