All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Jones <drjones@redhat.com>, kvm@vger.kernel.org
Cc: mtosatti@redhat.com, jen@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2 0/6] Generate standalone tests
Date: Wed, 29 Jul 2015 15:51:37 +0200	[thread overview]
Message-ID: <55B8DA69.7000306@redhat.com> (raw)
In-Reply-To: <1436806983-29783-1-git-send-email-drjones@redhat.com>



On 13/07/2015 19:02, Andrew Jones wrote:
> 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.

This is pretty wicked, but it's indeed useful.  Applied. :)

Paolo

> Thanks,
> drew
> 
> v2:
> - dropped several changes to run_tests.sh [drew]
> - pass DRYRUN through env, not config [drew]
> - share "run_all", rather than duplicating it [drew]
> - rewrote the script, improving it, and reducing ugliness
>   (well, a bit) [drew]
> 
> Andrew Jones (6):
>   run_tests.sh: share run_all as for_each_unittest
>   run: check DRYRUN
>   scripts: Introduce mkstandalone.sh
>   arm/unittests.cfg: changes to be more standalone friendly
>   Makefile: change 'make install' to install standalone tests
>   standalone: add documentation to README
> 
>  .gitignore                   |   1 +
>  Makefile                     |  10 +++-
>  README                       |  10 ++++
>  arm/run                      |  12 ++--
>  arm/unittests.cfg            |  10 ++--
>  config/config-arm-common.mak |   2 -
>  config/config-x86-common.mak |   2 -
>  run_tests.sh                 |  46 +--------------
>  scripts/functions.bash       |  42 ++++++++++++++
>  scripts/mkstandalone.sh      | 131 +++++++++++++++++++++++++++++++++++++++++++
>  x86/run                      |  11 ++--
>  11 files changed, 212 insertions(+), 65 deletions(-)
>  create mode 100644 scripts/functions.bash
>  create mode 100755 scripts/mkstandalone.sh
> 

      parent reply	other threads:[~2015-07-29 13:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 17:02 [kvm-unit-tests PATCH v2 0/6] Generate standalone tests Andrew Jones
2015-07-13 17:02 ` [kvm-unit-tests PATCH v2 1/6] run_tests.sh: share run_all as for_each_unittest Andrew Jones
2015-07-13 17:02 ` [kvm-unit-tests PATCH v2 2/6] run: check DRYRUN Andrew Jones
2015-07-13 17:03 ` [kvm-unit-tests PATCH v2 3/6] scripts: Introduce mkstandalone.sh Andrew Jones
2015-07-13 17:03 ` [kvm-unit-tests PATCH v2 4/6] arm/unittests.cfg: changes to be more standalone friendly Andrew Jones
2015-07-13 17:03 ` [kvm-unit-tests PATCH v2 5/6] Makefile: change 'make install' to install standalone tests Andrew Jones
2015-07-13 17:03 ` [kvm-unit-tests PATCH v2 6/6] standalone: add documentation to README Andrew Jones
2015-07-29 13:51 ` Paolo Bonzini [this message]

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=55B8DA69.7000306@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=drjones@redhat.com \
    --cc=jen@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.