ltp.lists.linux.it archive mirror
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] [RFC] tst_test: Add support for array of test functions
Date: Tue, 3 Oct 2017 14:59:58 +0200	[thread overview]
Message-ID: <20171003125958.GB11692@rei> (raw)
In-Reply-To: <860483630.25581747.1507017497043.JavaMail.zimbra@redhat.com>

Hi!
> What would be the benefits?

I was aiming to avoid the need to have a switch () in each testcase that
implements a similar tests but cannot be easily data driven (as we do
for most of tests that loop over an array of structures describing the
test data).

The question is, of course, if the interface is worth the effort.

-- 
Cyril Hrubis
chrubis@suse.cz

      reply	other threads:[~2017-10-03 12:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27  8:14 [LTP] [PATCH] [RFC] tst_test: Add support for array of test functions Cyril Hrubis
2017-10-02 13:16 ` Cyril Hrubis
2017-10-03  7:58 ` Jan Stancek
2017-10-03 12:59   ` Cyril Hrubis [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=20171003125958.GB11692@rei \
    --to=chrubis@suse.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).