c3d58a7a26
Add a new buildroot image based test that attaches a TPM emulator to the I2C bus and checks for a known PCR0 value for the image that was booted. Note that this does not tear down swtpm process when qemu execution fails. The swtpm process will exit when qemu exits if a connection has been made, but if the test errors before connection then the swtpm process will still be around. Signed-off-by: Joel Stanley <joel@jms.id.au> Reviewed-by: Stefan Berger <stefanb@linux.ibm.com> Reviewed-by: Cédric Le Goater <clg@kaod.org> Reviewed-by: Ninad Palsule <ninad@linux.ibm.com> Message-id: 20230328120844.190914-1-joel@jms.id.au |
||
---|---|---|
.. | ||
acpi-bits | ||
avocado_qemu | ||
virtiofs_submounts.py.data | ||
acpi-bits.py | ||
boot_linux_console.py | ||
boot_linux.py | ||
boot_xen.py | ||
cpu_queries.py | ||
empty_cpu_model.py | ||
hotplug_cpu.py | ||
info_usernet.py | ||
intel_iommu.py | ||
kvm_xen_guest.py | ||
linux_initrd.py | ||
linux_ssh_mips_malta.py | ||
load_bflt.py | ||
machine_aarch64_virt.py | ||
machine_arm_canona1100.py | ||
machine_arm_integratorcp.py | ||
machine_arm_n8x0.py | ||
machine_aspeed.py | ||
machine_avr6.py | ||
machine_m68k_nextcube.py | ||
machine_microblaze.py | ||
machine_mips_fuloong2e.py | ||
machine_mips_loongson3v.py | ||
machine_mips_malta.py | ||
machine_rx_gdbsim.py | ||
machine_s390_ccw_virtio.py | ||
machine_sparc64_sun4u.py | ||
machine_sparc_leon3.py | ||
migration.py | ||
multiprocess.py | ||
netdev-ethtool.py | ||
pc_cpu_hotplug_props.py | ||
ppc_74xx.py | ||
ppc_405.py | ||
ppc_bamboo.py | ||
ppc_mpc8544ds.py | ||
ppc_prep_40p.py | ||
ppc_pseries.py | ||
ppc_virtex_ml507.py | ||
README.rst | ||
replay_kernel.py | ||
replay_linux.py | ||
reverse_debugging.py | ||
riscv_opensbi.py | ||
smmu.py | ||
tcg_plugins.py | ||
tesseract_utils.py | ||
tuxrun_baselines.py | ||
version.py | ||
virtio_check_params.py | ||
virtio_version.py | ||
virtio-gpu.py | ||
vnc.py | ||
x86_cpu_model_versions.py |
============================================= Integration tests using the Avocado Framework ============================================= This directory contains integration tests. They're usually higher level, and may interact with external resources and with various guest operating systems. For more information, please refer to ``docs/devel/testing.rst``, section "Integration tests using the Avocado Framework".