From: Cyril Hrubis <chrubis@suse.cz>
To: Jiri Jaburek <jjaburek@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] network namespaces tests cleanup
Date: Tue, 17 Feb 2015 15:04:58 +0100 [thread overview]
Message-ID: <20150217140458.GA25756@rei> (raw)
In-Reply-To: <54E33EE9.9000302@redhat.com>
Hi!
> Alternatively, you could approach it a bit differently - test the
> actual kernel namespacing functionality using unshare/setns in
> *kernel*/containers/ and verify that iproute2 uses it in
> network/iproute/ (or perhaps commands/ip/ ?).
Right what needs to be tested is the kernel functionality and that the
tools call correct syscall with correct paramters, these are two
different things. But still as far as I can see the easiest way is to
run the whole test and switch between the tool it uses which is just a
few lines of code.
How do you plan to test that ip does what it should? Run it under strace
and grep for the syscall and check the parameters? That sound fragile to
me. Or is there a better way?
> The idea being that you don't exactly need to "brute force" test
> everything everytime - the kernel functionality doesn't change
> based on what utility uses the unshare() syscall.
> I (in ltp-unrelated activities) found out that this approach gives
> the best coverage / time / maintenance ratio.
Agree that the kernel functionality is the same. But how does having two
different testcases one for kernel functionality and one for ip decrease
maintenance ratio? This soulution would IMHO be more complicated. The
coverate should be same. The only aspect in which this solution is
likely better is test runtime, but that shouldn't be a problem because
these testcases does not take long time. Or am I mistaken?
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2015-02-17 14:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <789026778.7588485.1423581396876.JavaMail.zimbra@redhat.com>
[not found] ` <1688764619.7589818.1423581433749.JavaMail.zimbra@redhat.com>
2015-02-12 11:03 ` [LTP] network namespaces tests cleanup Cyril Hrubis
[not found] ` <980241572.9316983.1423749665613.JavaMail.zimbra@redhat.com>
[not found] ` <54E33EE9.9000302@redhat.com>
2015-02-17 14:04 ` Cyril Hrubis [this message]
[not found] ` <54E35175.20807@redhat.com>
2015-02-17 15:20 ` Cyril Hrubis
2015-02-18 16:54 ` Jiri Jaburek
2015-02-18 17:35 ` Jiri Jaburek
2015-02-19 15:04 ` Cyril Hrubis
[not found] ` <54EC5053.4060005@redhat.com>
2015-02-25 12:35 ` Cyril Hrubis
[not found] ` <54EDC5B4.9050806@redhat.com>
2015-02-25 13:05 ` 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=20150217140458.GA25756@rei \
--to=chrubis@suse.cz \
--cc=jjaburek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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