public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <drjones@redhat.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, mtosatti@redhat.com, jen@redhat.com
Subject: [kvm-unit-tests PATCH 0/9] Generate standalone tests
Date: Fri, 10 Jul 2015 18:44:54 +0200	[thread overview]
Message-ID: <1436546703-12258-1-git-send-email-drjones@redhat.com> (raw)

Add support to convert unit tests to standalone scripts that
can be run outside the framework. This is almost an RFC, but
it doesn't impact the current framework (except for 'make install',
but was that ever used?). The scripting is ugly, but I see value
in having easily distributable unit tests.

Testing: if you run all standalone tests, concatenating all output
to a file, then that file will match test.log after running
run_tests.sh. Additionally, all prechecks are preserved, i.e.
specific arch and 'check' conditions from unittests.cfg.

Thanks,
drew

Andrew Jones (9):
  x86/run: source config.mak
  run_tests.sh: remove blank line from start of log
  run_tests.sh: add '-d' for dry-run
  run_tests.sh: allow default unittests.cfg override
  unittests.cfg: use double quotes
  arm/unittests.cfg: make test names more friendly
  scripts: introduce mk[all]standalone.sh
  Makefile: change 'make install' to install standalone tests
  standalone: add documentation to README

 Makefile                     |  10 ++--
 README                       |  10 ++++
 arm/run                      |  20 +++++---
 arm/unittests.cfg            |  16 +++----
 config/config-arm-common.mak |   2 -
 config/config-x86-common.mak |   2 -
 run_tests.sh                 |  47 +++++++++++-------
 scripts/mkallstandalone.sh   |  36 ++++++++++++++
 scripts/mkstandalone.sh      | 110 +++++++++++++++++++++++++++++++++++++++++++
 x86/run                      |  21 +++++++--
 x86/unittests.cfg            |  16 +++----
 11 files changed, 239 insertions(+), 51 deletions(-)
 create mode 100755 scripts/mkallstandalone.sh
 create mode 100755 scripts/mkstandalone.sh

-- 
2.4.3


             reply	other threads:[~2015-07-10 16:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 16:44 Andrew Jones [this message]
2015-07-10 16:44 ` [kvm-unit-tests PATCH 1/9] x86/run: source config.mak Andrew Jones
2015-07-10 16:44 ` [kvm-unit-tests PATCH 2/9] run_tests.sh: remove blank line from start of log Andrew Jones
2015-07-10 16:44 ` [kvm-unit-tests PATCH 3/9] run_tests.sh: add '-d' for dry-run Andrew Jones
2015-07-10 16:44 ` [kvm-unit-tests PATCH 4/9] run_tests.sh: allow default unittests.cfg override Andrew Jones
2015-07-10 16:44 ` [kvm-unit-tests PATCH 5/9] unittests.cfg: use double quotes Andrew Jones
2015-07-10 16:45 ` [kvm-unit-tests PATCH 6/9] arm/unittests.cfg: make test names more friendly Andrew Jones
2015-07-10 16:45 ` [kvm-unit-tests PATCH 7/9] scripts: introduce mk[all]standalone.sh Andrew Jones
2015-07-10 16:45 ` [kvm-unit-tests PATCH 8/9] Makefile: change 'make install' to install standalone tests Andrew Jones
2015-07-10 16:45 ` [kvm-unit-tests PATCH 9/9] standalone: add documentation to README Andrew Jones
2015-07-13  9:46 ` [kvm-unit-tests PATCH 0/9] Generate standalone tests Andrew Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1436546703-12258-1-git-send-email-drjones@redhat.com \
    --to=drjones@redhat.com \
    --cc=jen@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox