ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Amit Kucheria <amit.kucheria@linaro.org>
To: Shuah Khan <shuahkhan@gmail.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Fwd: Rough notes from testing unconference
Date: Fri, 22 Aug 2014 23:38:37 +0530	[thread overview]
Message-ID: <CAP245DWYCLR43pL1joowpwc=97ypdT_Q8xbw4e7rxd4czP489w@mail.gmail.com> (raw)
In-Reply-To: <CAKocOOMG91D7Qam5PLY0Dd7bR07GMHHYsRCqUMYQGCR-hB2+=w@mail.gmail.com>

On Fri, Aug 22, 2014 at 11:29 PM, Shuah Khan <shuahkhan@gmail.com> wrote:
> Shuah Khan:
>
> - Work on putting a basic framework for tests: Pass, Fail, Skip to start with.
> - update existing tests in tools/testing/selftests to use the
> framework to serve as an
>   example for future tests. As we discussed and decided on output will
> continue to go to
>   stdio. This will help these tests being used in other scripts that
> run tests in cross
>   environments.
> - Define profiles for short and longer time tests
> - Add install target in addition to the existing kselftest target at
> the top level Makefile
>
> I will maintain the test framework - will take care of the logistics
> of MAINTAINER
> file updates for this and creating a git tree. Individual test
> maintainers (we have
> several in MAINTAINERS file) will continue to own and maintain their tests.
>
> Fixes to known cross-build failures and new tests are welcome. Please
> send patches to linux-api mailing list
>

Hi Shuah,

At the Linaro power management working group, we've created a simple
repository of pass/fail *functional* tests for various areas of
interest in power management - cpuidle, cpufreq, hotplug. We call it
PM-QA[1]

Some of our members have found PM-QA useful to exercise the various
sysfs interfaces and get rid of the obvious issues (missing Kconfig
options, basic exercising of cpufreq drivers being a couple of
examples).

Let me know if these are useful and in the right format to seed your
library of testcases.

Regards,
Amit
[1] https://git.linaro.org/power/pm-qa.git

  reply	other threads:[~2014-08-22 18:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140819163621.GA15109@linux.vnet.ibm.com>
2014-08-22 14:19 ` Grant Likely
2014-08-22 17:59   ` Shuah Khan
2014-08-22 18:08     ` Amit Kucheria [this message]
2014-08-28 21:54       ` Shuah Khan
2014-08-23 13:35     ` Bird, Tim
2014-08-23 21:12       ` Grant Likely
2014-08-30  1:09       ` [Ksummit-discuss] [kselftest] kselftest wiki (was RE: Fwd: Rough notes from testing unconference) Bird, Tim
2014-08-30  2:55         ` Shuah Khan
2014-08-30  5:15           ` Konstantin Ryabitsev
2014-08-23  8:12   ` [Ksummit-discuss] Fwd: Rough notes from testing unconference Fengguang Wu
2014-08-24 17:12     ` Grant Likely
2014-08-24 18:14       ` Guenter Roeck
2014-08-25  9:23         ` Grant Likely
2014-08-25 10:43           ` Guenter Roeck
2014-08-24 18:15       ` Geert Uytterhoeven
2014-08-24 18:37         ` Guenter Roeck
2014-08-24 18:47           ` Olof Johansson
2014-08-24 19:14             ` Jason Cooper
2014-08-24 19:16               ` Jason Cooper

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='CAP245DWYCLR43pL1joowpwc=97ypdT_Q8xbw4e7rxd4czP489w@mail.gmail.com' \
    --to=amit.kucheria@linaro.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=shuahkhan@gmail.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