All of lore.kernel.org
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: ltp@lists.linux.it
Subject: [LTP] Number of testcases per releases - LTP
Date: Tue, 13 Sep 2016 16:04:17 +0530	[thread overview]
Message-ID: <CA+G9fYuF8y8Hr_RfnJUtbFVMnsMdJVr4dOugwmN=Mb0Yas_nmg@mail.gmail.com> (raw)

Hi Jonatas,

> I`m a PhD student interested in run some studies with the different LTP
> releases. I would like to know how can I identify tests inside LTP releases
> (i.e. number of testcases and module)
> Should I consider all .c files as tests in testcases folder?
No.

> Should I consider all .sh files in testcases folder?
No.

> If not, how should I identify a valid test case

All test cases listed in runtest/ directory. each file in side it
contains the list of test cases. those test cases divided logically
for full test suite execution, part of Linux sub system test cases and
long running stress tests.

Please walk through runtest directory. You may find repeated test
cases. you have to count it only once.

Example:
$ grep "shmget01 shmget01"  *
ltplite:shmget01 shmget01
stress.part3:shmget01 shmget01
syscalls:shmget01 shmget01
syscalls-ipc:shmget01 shmget01

Try to run each subset of test cases,
./runltp -f mm
./runltp -f math
./runltp -f syscalls
./runltp -f timers

- Naresh Kamboju

>
> --
> Jonatas Bastos

             reply	other threads:[~2016-09-13 10:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 10:34 Naresh Kamboju [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-09-13  2:18 [LTP] Number of testcases per releases - LTP Jonatas Bastos
2016-09-13 13:29 ` Carlos Hernandez

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='CA+G9fYuF8y8Hr_RfnJUtbFVMnsMdJVr4dOugwmN=Mb0Yas_nmg@mail.gmail.com' \
    --to=naresh.kamboju@linaro.org \
    --cc=ltp@lists.linux.it \
    /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.