From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] new shell library
Date: Tue, 4 Oct 2016 04:23:03 -0400 (EDT) [thread overview]
Message-ID: <2007222752.190298.1475569383933.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20161003145835.GD7583@rei.suse.cz>
----- Original Message -----
> From: "Cyril Hrubis" <chrubis@suse.cz>
> To: ltp@lists.linux.it
> Cc: "Jan Stancek" <jstancek@redhat.com>
> Sent: Monday, 3 October, 2016 4:58:35 PM
> Subject: new shell library
>
> Hi!
> I've played bit with the shell test library in order to make it more
> aligned with the C library, have a look at:
>
> https://github.com/metan-ucw/ltp
>
> So far I've converted all testcases in commands/ directory, you can have
> a look at last 12 commits in the repo to see how the new shell library
> and testcases looks like. I would love to get someone to review the code
> before I attempt to convert more testcases.
Hi,
As a person who sees this first time, my immediate concern was,
how do I know what variables functions names are reserved
(without need to read entire tst_test.sh) and what happens if
I make a typo?
It also forces me to use specific names as the names
of my functions (e.g. "test", which presumably shadows test(1)).
And there's now requirement on when you can include new library,
it has to be at the end of file, because there are side-effects
(it starts the test on inclusion).
So, I was thinking:
. tst_test.sh
...
tst_def TID="du01"
tst_def TCNT=23
tst_def TST_SETUP mysetup
tst_def TST_CLEANUP mycleanup
tst_def TST_TESTFUNC mytest
tst_def TST_NEEDS_TMPDIR=1
tst_def TST_NEEDS_CMDS="dd du stat"
tst_start
tst_def - makes it clear that this variable defines something for tst_test,
checks for potential typos, doesn't allow non-existent ones,
is a single place in tst_test.sh where I can see all possible variables together
TST_TESTFUNC - allows me to give test function any name
tst_start - starts the test
allows us to keep all includes at one place
IMO all of these would make the interface between tst_test.sh and actual
test more apparent and it's still in the spirit of C counter-part.
Regards,
Jan
>
> --
> Cyril Hrubis
> chrubis@suse.cz
>
next prev parent reply other threads:[~2016-10-04 8:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 14:58 [LTP] new shell library Cyril Hrubis
2016-10-04 8:23 ` Jan Stancek [this message]
2016-10-04 8:45 ` Cyril Hrubis
2016-10-04 9:02 ` Jan Stancek
2016-10-04 9:35 ` Cyril Hrubis
2016-10-04 9:54 ` Jan Stancek
2016-10-04 11:50 ` Cyril Hrubis
2016-10-12 10:08 ` Cyril Hrubis
2016-10-12 10:32 ` Jan Stancek
2016-10-12 12:36 ` Cyril Hrubis
2016-10-12 13:17 ` Cyril Hrubis
2016-10-12 14:54 ` Jan Stancek
2016-10-12 15:06 ` Cyril Hrubis
2016-10-13 15:43 ` Cyril Hrubis
2016-10-27 14:58 ` Cyril Hrubis
2016-10-31 10:03 ` Jan Stancek
2016-10-31 10:39 ` Cyril Hrubis
2016-11-14 13:12 ` Cyril Hrubis
2016-11-22 6:50 ` Cyril Hrubis
2016-11-22 7:54 ` Jan Stancek
2016-11-22 8:02 ` Cyril Hrubis
2016-11-22 10:47 ` Jan Stancek
2016-11-22 11:21 ` Cyril Hrubis
-- strict thread matches above, loose matches on Subject: below --
2016-11-22 12:20 Jan Stancek
2016-11-22 13:27 ` Cyril Hrubis
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=2007222752.190298.1475569383933.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--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