All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Björn Stenberg" <bjst@enea.com>
To: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Discussion: Package testing
Date: Fri, 15 Jun 2012 10:23:27 +0200	[thread overview]
Message-ID: <20120615082326.GA28297@giant> (raw)
In-Reply-To: <CACW_hTYR8ceMLFg=cwhM0+ABjN6VndcddWQP8g01mfUDadU3rA@mail.gmail.com>

Frans Meulenbroeks wrote:
> a run-all-tests.sh script is somewhat problematic as
> different systems have different packages installed so different tests.

The idea is that the top level run-all script looks in the /opt/ptest directory and runs all package tests that are installed there. It has no built-in knowledge of any tests.

> I think testers are mainly interested in success (all tests give ok is
> good, if a test fails, it would be fine with me if I would have to go to a
> package specific place to find log files etc (or it could be written to a
> common log file)

While failing tests are the most interesting during development, keeping track of both failed and successful test cases is important for regression tracking and test development over time. Therefore we want to produce an output that clearly identifies each test case ran and its result.

> The only specific point I can think of is cleaning up after a test is run.

Good point, I forgot to mention that. It is the responsibility of the per-package "run-ptest" script to clean up after the test.

-- 
Björn


  reply	other threads:[~2012-06-15  8:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 13:26 Discussion: Package testing Björn Stenberg
2012-06-14 19:54 ` Frans Meulenbroeks
2012-06-15  8:23   ` Björn Stenberg [this message]
2012-06-18 11:43 ` Richard Purdie
2012-06-18 13:04   ` Fredrik Hugosson
2012-06-18 14:50     ` Björn Stenberg
2012-06-18 15:04   ` Björn Stenberg
2012-06-19 11:24     ` Burton, Ross
2012-06-21  8:50       ` Björn Stenberg

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=20120615082326.GA28297@giant \
    --to=bjst@enea.com \
    --cc=fransmeulenbroeks@gmail.com \
    --cc=yocto@yoctoproject.org \
    /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.