From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pablo Neira Ayuso Subject: Re: [PATCH nft v2 0/6] tests: Automated regression testing Date: Thu, 18 Sep 2014 10:52:33 +0200 Message-ID: <20140918085233.GA4094@salvia> References: <1410785230-8498-1-git-send-email-anarey@gmail.com> <20140917221033.GA29146@acer.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Ana Rey , netfilter-devel@vger.kernel.org To: Patrick McHardy Return-path: Received: from mail.us.es ([193.147.175.20]:38990 "EHLO mail.us.es" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755109AbaIRIvq (ORCPT ); Thu, 18 Sep 2014 04:51:46 -0400 Content-Disposition: inline In-Reply-To: <20140917221033.GA29146@acer.localdomain> Sender: netfilter-devel-owner@vger.kernel.org List-ID: On Thu, Sep 18, 2014 at 12:10:33AM +0200, Patrick McHardy wrote: > On Mon, Sep 15, 2014 at 02:47:04PM +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 > > I think it's great to have this and would suggest pulling it into the > tree now and continue the work there. > > So if you don't have any objections, I'll apply the series. Please wait, she's going to send a final v3. Thanks.