All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Petlan <mpetlan@redhat.com>
To: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Subject: [PATCH 0/3] introducing tools/perf/testsuite
Date: Thu, 22 Oct 2015 01:08:45 +0200	[thread overview]
Message-ID: <1445468925.12960.117.camel@Rudolf-RHEL-7> (raw)

Hi all,

in the following patches I introduce a skeleton of a testsuite for
perf tool. The idea of this testsuite is to primarily cover all the
sub-commands perf has and verify their functionality.

The testsuite is designed to be structured in order to be able to
keep an order in some amount of testcases. Each group of testcases
is located in a base_<something> dir with its init and cleanup
scripts and shell files test_<something>.sh that should carry the
testcases. Each testcase can have multiple assertions inside. The
base_skeleton and base_stat are an example. New tests are supposed
to be derived from them.

Since the testsuite is meant to be usable for both smoke and deeper
testing, it has some parametrization in common/parametrization.sh.

My idea is to add testcases for the other existing builtin commands
and then continue extending it for the upcoming ones.

How does it seem to you? Thoughts?

Michael


Michael Petlan (3):
  tools/perf/testsuite: Init commit
  tools/perf/testsuite: Adding a skeleton for future testcases
  tools/perf/testsuite: Adding a set of testcases for perf-stat

 tools/perf/testsuite/base_skeleton/cleanup.sh      |  16 +++
 tools/perf/testsuite/base_skeleton/settings.sh     |  10 ++
 tools/perf/testsuite/base_skeleton/setup.sh        |  16 +++
 tools/perf/testsuite/base_skeleton/test_01.sh      |  40 ++++++++
 tools/perf/testsuite/base_stat/cleanup.sh          |  20 ++++
 tools/perf/testsuite/base_stat/settings.sh         |  10 ++
 tools/perf/testsuite/base_stat/test_basic.sh       |  68 ++++++++++++
 tools/perf/testsuite/base_stat/test_hw.sh          |  50 +++++++++
 tools/perf/testsuite/base_stat/test_hwcache.sh     |  51 +++++++++
 .../testsuite/base_stat/test_powerpc_hv_24x7.sh    |  60 +++++++++++
 .../testsuite/common/check_all_lines_matched.pl    |  28 +++++
 .../testsuite/common/check_all_patterns_found.pl   |  30 ++++++
 .../testsuite/common/check_any_pattern_found.pl    |  14 +++
 tools/perf/testsuite/common/init.sh                |  50 +++++++++
 tools/perf/testsuite/common/parametrization.sh     |  18 ++++
 tools/perf/testsuite/common/patterns.sh            |  74 +++++++++++++
 tools/perf/testsuite/common/settings.sh            |  50 +++++++++
 tools/perf/testsuite/test_driver.sh                | 114 +++++++++++++++++++++
 18 files changed, 719 insertions(+)
 create mode 100755 tools/perf/testsuite/base_skeleton/cleanup.sh
 create mode 100644 tools/perf/testsuite/base_skeleton/settings.sh
 create mode 100755 tools/perf/testsuite/base_skeleton/setup.sh
 create mode 100755 tools/perf/testsuite/base_skeleton/test_01.sh
 create mode 100755 tools/perf/testsuite/base_stat/cleanup.sh
 create mode 100644 tools/perf/testsuite/base_stat/settings.sh
 create mode 100755 tools/perf/testsuite/base_stat/test_basic.sh
 create mode 100755 tools/perf/testsuite/base_stat/test_hw.sh
 create mode 100755 tools/perf/testsuite/base_stat/test_hwcache.sh
 create mode 100755 tools/perf/testsuite/base_stat/test_powerpc_hv_24x7.sh
 create mode 100755 tools/perf/testsuite/common/check_all_lines_matched.pl
 create mode 100755 tools/perf/testsuite/common/check_all_patterns_found.pl
 create mode 100755 tools/perf/testsuite/common/check_any_pattern_found.pl
 create mode 100644 tools/perf/testsuite/common/init.sh
 create mode 100644 tools/perf/testsuite/common/parametrization.sh
 create mode 100644 tools/perf/testsuite/common/patterns.sh
 create mode 100644 tools/perf/testsuite/common/settings.sh
 create mode 100755 tools/perf/testsuite/test_driver.sh

-- 
1.8.3.1

             reply	other threads:[~2015-10-21 23:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 23:08 Michael Petlan [this message]
2015-10-22 10:11 ` [PATCH 0/3] introducing tools/perf/testsuite 平松雅巳 / HIRAMATU，MASAMI
2015-10-22 12:16 ` [PATCH perf/core 0/2] perf/runtests: Add runtests.sh shellscript testcases for perf probe Masami Hiramatsu
2015-10-22 12:16   ` [PATCH perf/core 1/2] perf/runtests: Add runtests.sh shellscript testsuite Masami Hiramatsu
2015-10-22 12:16   ` [PATCH perf/core 2/2] perf/runtests: Add testcases for perf probe Masami Hiramatsu
2015-11-03  0:43   ` [PATCH perf/core 0/2] perf/runtests: Add runtests.sh shellscript " Michael Petlan
2015-11-03  3:24     ` 平松雅巳 / HIRAMATU，MASAMI
2015-11-03 15:45       ` Arnaldo Carvalho de Melo
2015-11-03 19:55         ` Michael Petlan

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=1445468925.12960.117.camel@Rudolf-RHEL-7 \
    --to=mpetlan@redhat.com \
    --cc=linux-perf-users@vger.kernel.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.