Fam Zheng <f...@redhat.com> writes:
> Signed-off-by: Fam Zheng <f...@redhat.com>
> ---
> tests/docker/test-basic.sh | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
> create mode 100755 tests/docker/test-basic.sh
>
> diff --git a/tests/docker/test-basic.sh b/tests/docker/test-basic.sh
> new file mode 100755
> index 0000000..c2b32ad
> --- /dev/null
> +++ b/tests/docker/test-basic.sh
> @@ -0,0 +1,22 @@
> +#!/bin/bash -e
> +#
> +# Basic compiling test that everyone already does. But why not automate it?
> +#
> +# Copyright (c) 2016 Red Hat Inc.
> +#
> +# Authors:
> +# Fam Zheng <f...@redhat.com>
> +#
> +# This work is licensed under the terms of the GNU GPL, version 2
> +# or (at your option) any later version. See the COPYING file in
> +# the top-level directory.
> +
> +. common.rc
> +
> +cd $(mktemp -d)
> +mkdir build
> +mkdir install
> +cd build
> +build_qemu --target-list=x86_64-softmmu --prefix="${pwd}/install"
> +make check $MAKEFLAGS
> +make install
>From my excursions last week into the tests directory I discovered the
unit tests are built for a number of different qtest binaries. For
completeness we should probably include the whole list:
#+name: qtest-targets
#+begin_src sh :dir ~/lsrc/qemu/qemu.git :results scalar
grep -E "check-qtest-[[:alnum:]]+-y " tests/Makefile | cut -d " " -f 1 | sort -u
#+end_src
#+RESULTS: qtest-targets
#+begin_example
check-qtest-arm-y
check-qtest-generic-y
check-qtest-i386-y
check-qtest-ipack-y
check-qtest-microblazeel-y
check-qtest-mips64el-y
check-qtest-mips64-y
check-qtest-mips-y
check-qtest-pci-y
check-qtest-ppc64-y
check-qtest-ppc-y
check-qtest-sh4eb-y
check-qtest-sh4-y
#check-qtest-sparc64-y
check-qtest-sparc64-y
#check-qtest-sparc-y
check-qtest-virtioserial-y
check-qtest-virtio-y
check-qtest-x86_64-y
check-qtest-xtensaeb-y
check-qtest-y
#+end_example
--
Alex Bennée
