From: Cyril Hrubis <chrubis@suse.cz>
To: Cui Bixuan <cuibixuan@huawei.com>
Cc: zhuyanpeng@huawei.com, ltp-list@lists.sourceforge.net,
zhanyongming@huawei.com
Subject: Re: [LTP] [PATCH 2/5] iptables/iptables_tests.sh: Add new testcases for iptables -c
Date: Tue, 9 Jun 2015 16:01:22 +0200 [thread overview]
Message-ID: <20150609140121.GD27378@rei.suse.de> (raw)
In-Reply-To: <5565177B.7080308@huawei.com>
Hi!
> +test07()
> +{
> + local logcnt=0
> + tst_resm TINFO "iptables -c test."
> +
> + iptables -A INPUT -s 127.0.0.1 -j DROP -c 10 500 \
> + > tst_iptables.out 2>&1
> + if [ $? -ne 0 ]; then
> + tst_resm TFAIL "iptables command failed to append new rule."
> + cat tst_iptables.out
> + return
> + fi
> +
> + logcnt=`iptables -L -v |grep localhost |awk '{print $2}'` \
> + > tst_iptables.out 2>&1
grep can do regular expressions as well, why can't we
match this with single grep command?
i.e.
if iptables -L -v |grep -q ".*10.*500.*localhost.*"; then
PASSED
else
FAILED
fi
> + if [ $logcnt -ne 500 ]; then
> + tst_resm TFAIL "iptables -c 10 500 failed."
> + cat tst_iptables.err
^
Where is this file created?
> + return
> + fi
> +
> + logcnt=`iptables -L -v |grep localhost |awk '{print $1}'` \
> + > tst_iptables.out 2>&1
> + if [ $logcnt -ne 10 ]; then
> + tst_resm TFAIL "iptables -c 10 500 failed."
> + cat tst_iptables.err
> + return
> + fi
> +
> + tst_resm TINFO "Deleting rule."
> + iptables -D INPUT 1 > tst_iptables.out 2>&1
> + if [ $? -ne 0 ]; then
> + tst_resm TFAIL "iptables did not remove the rule."
This should rather be TBROK, but that is minor.
> + cat tst_iptables.out
> + return
> + fi
> +
> + tst_resm TPASS "iptables -c test succeed."
> +}
> +
> init
> TST_CLEANUP=cleanup
>
> @@ -419,5 +459,6 @@ test03
> test04
> test05
> test06
> +test07
>
> tst_exit
> --
> 1.6.0.2 .
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2015-06-09 14:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 0:59 [LTP] [PATCH 1/5] iptables/iptables_tests.sh: Add test cases for iptables -L Cui Bixuan
2015-05-27 1:01 ` [LTP] [PATCH 2/5] iptables/iptables_tests.sh: Add new testcases for iptables -c Cui Bixuan
2015-06-09 14:01 ` Cyril Hrubis [this message]
2015-05-27 1:02 ` [LTP] [PATCH 3/5] iptables/iptables_tests.sh: Add new testcases for iptables -o Cui Bixuan
2015-06-09 14:13 ` Cyril Hrubis
2015-06-09 14:17 ` Cyril Hrubis
2015-05-27 1:03 ` [LTP] [PATCH 4/5] iptables/iptables_tests.sh: Add new testcases for iptables -N/E Cui Bixuan
2015-05-27 1:04 ` [LTP] [PATCH 5/5] iptables/iptables_tests.sh: Add new testcases for iptables -R Cui Bixuan
2015-06-09 13:33 ` [LTP] [PATCH 1/5] iptables/iptables_tests.sh: Add test cases for iptables -L Cyril Hrubis
2015-06-09 13:38 ` 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=20150609140121.GD27378@rei.suse.de \
--to=chrubis@suse.cz \
--cc=cuibixuan@huawei.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=zhanyongming@huawei.com \
--cc=zhuyanpeng@huawei.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