From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Ana Rey <anarey@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [v3 nft 0/7] tests: Automated regression testing
Date: Thu, 18 Sep 2014 13:02:09 +0200 [thread overview]
Message-ID: <20140918110209.GA12058@salvia> (raw)
In-Reply-To: <1411036761-26825-1-git-send-email-anarey@gmail.com>
On Thu, Sep 18, 2014 at 12:39:14PM +0200, Ana Rey wrote:
> This is a new version of the automated regression testing of nftables.
>
> There is no infrastructure to allow us to check all options/features in
> nft. So, if anyone sends a patch, we cannot check if it breaks something.
>
> I send in this patchset the nftables automated regression tests. It
> contains a python script (nft-add.py) and a set of test files.
>
> This allow us to check the input of rules of nft-tool from the
> command-line and the output from nft-tool of this rule. Then, it
> compares if the rule input matches the rule output automatically.
>
> We also have plans to add automated regression testing in the packet
> path in the future, which should come in a follow up step.
>
> Comments welcome, thanks
Finally :-). Series applied, thanks Ana.
prev parent reply other threads:[~2014-09-18 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 10:39 [v3 nft 0/7] tests: Automated regression testing Ana Rey
2014-09-18 10:39 ` [v3 nft 1/7] tests: Add automated " Ana Rey
2014-09-18 10:39 ` [v3 nft 2/7] tests: Add ip folder with test files Ana Rey
2014-09-18 10:39 ` [v3 nft 3/7] tests: Add ip6 " Ana Rey
2014-09-18 10:39 ` [v3 nft 4/7] tests: Add inet " Ana Rey
2014-09-18 10:39 ` [v3 nft 5/7] tests: Add arp " Ana Rey
2014-09-18 10:39 ` [v3 nft 6/7] tests: Add bridge " Ana Rey
2014-09-18 10:39 ` [v3 nft 7/7] tests: Add any " Ana Rey
2014-09-18 11:02 ` Pablo Neira Ayuso [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=20140918110209.GA12058@salvia \
--to=pablo@netfilter.org \
--cc=anarey@gmail.com \
--cc=netfilter-devel@vger.kernel.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 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).