On 4/24/20 9:14 PM, Richard Henderson wrote: > What user-mode testing do you think might be improved by using avocado?
Test unmodified real-world binaries, know to work in the field. Test can be added by users without having to be a TCG developer, see https://www.mail-archive.com/qemu-devel@nongnu.org/msg626608.html: class LoadBFLT(LinuxUserTest): def test_stm32(self): rootfs_url = ('https://elinux.org/images/5/51/' 'Stm32_mini_rootfs.cpio.bz2') rootfs_path_bz2 = self.fetch_asset(rootfs_url, ...) busybox_path = self.workdir + "/bin/busybox" res = self.run("%s %s" % (busybox_path, cmd)) ver = 'BusyBox v1.24.0.git (2015-02-03 22:17:13 CET) ...' self.assertIn(ver, res.stdout_text) cmd = 'uname -a' res = self.run("%s %s" % (busybox_path, cmd)) unm = 'armv7l GNU/Linux' self.assertIn(unm, res.stdout_text) This is a fairly trivial test, cheap (no need to cross-build), yet it still covers quite some QEMU code. > IMO at present we have a fairly comprehensive testing infrastructure for > user-mode that is simply underused. With docker, we have a set of > cross-compilers for most guest architectures, and we are able to build > statically linked binaries that are copied out of the container for > testing by the just-built qemu binaries on the host. This > infrastructure is used by check-tcg. It's fairly easy to add new test > cases to be run on one or all guests. What you describe is a different and complementary test set. Craft tests and build them with QEMU. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1874674 Title: [Feature request] acceptance test class to run user-mode binaries Status in QEMU: New Bug description: Currently the acceptance test framework only target system-mode emulation. It would be useful to test user-mode too. Ref: https://www.mail-archive.com/qemu-devel@nongnu.org/msg626610.html To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1874674/+subscriptions