From: Ido Schimmel <idosch@idosch.org>
To: Harald Welte <laforge@gnumonks.org>
Cc: osmocom-net-gprs@lists.osmocom.org, netdev@vger.kernel.org,
Pablo Neira Ayuso <pablo@gnumonks.org>,
Andreas Schultz <aschultz@tpip.net>,
jiri@mellanox.com, olichtne@redhat.com
Subject: Re: RFC: unit tests for kernel GTP module
Date: Fri, 17 Feb 2017 12:22:22 +0200 [thread overview]
Message-ID: <20170217102222.GA5566@splinter.mtl.com> (raw)
In-Reply-To: <20170216220801.o3fajacj4sx3iere@nataraja>
Hi,
On Thu, Feb 16, 2017 at 11:08:01PM +0100, Harald Welte wrote:
> Also, if netdev folks have some ideas/pointers about possible
> frameworks/tools for this kind of testing [it must exist for at least
> some other kernel networking code?]: Please let me know. I'd be
> interested to have a look if there's something that can be used as a
> basis (starting network namespaces, sending/transmitting packets, test
> case startup/teardown, ...)
I'm not sure it meets all your needs, but we use LNST [1] to test our
code. You can see the tests (recipes) here [2]. You can create network
namespaces, send / receive packets, run arbitrary shell commands and
use existing test modules (e.g., ping, netperf) which return pass /
fail.
Adding Jiri and Ondrej, who is currently in the process of refactoring
the code and also familiar with more LNST use cases, such as those
employed by Redhat.
1. https://github.com/jpirko/lnst
2. https://github.com/jpirko/lnst/tree/master/recipes/
next prev parent reply other threads:[~2017-02-17 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 22:08 RFC: unit tests for kernel GTP module Harald Welte
2017-02-17 10:22 ` Ido Schimmel [this message]
2017-02-17 15:02 ` Andreas Schultz
2017-02-17 18:03 ` Harald Welte
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=20170217102222.GA5566@splinter.mtl.com \
--to=idosch@idosch.org \
--cc=aschultz@tpip.net \
--cc=jiri@mellanox.com \
--cc=laforge@gnumonks.org \
--cc=netdev@vger.kernel.org \
--cc=olichtne@redhat.com \
--cc=osmocom-net-gprs@lists.osmocom.org \
--cc=pablo@gnumonks.org \
/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.