From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [conntrack-tools PATCH 1/3] tests: introduce new python-based framework for running tests
Date: Mon, 1 Feb 2021 18:05:51 +0100 [thread overview]
Message-ID: <20210201170551.GA28275@salvia> (raw)
In-Reply-To: <949b08b1-d7c7-c040-7218-9df63562c032@netfilter.org>
On Mon, Feb 01, 2021 at 11:49:02AM +0100, Arturo Borrero Gonzalez wrote:
> On 2/1/21 4:31 AM, Pablo Neira Ayuso wrote:
[...]
> > * Missing yaml dependency in python in my test machine
> >
> > Traceback (most recent call last):
> > File "cttools-testing-framework.py", line 36, in <module>
> > import yaml
> > ModuleNotFoundError: No module named 'yaml'
> >
> > this is installed from pip, right? Just a note in the commit message
> > is fine.
>
> It was already present in the commit message.
>
> I made it more clear:
>
> === 8< ===
> On Debian machines, it requires the *python3-yaml* package to be installed
> as a dependency
> === 8< ===
Sorry, I overlook this.
> > * Would it be possible to define the scenario in shell script files?
> > For example, to define the "simple_stats" scenario, the YAML file
> > looks like this:
> >
> > - name: simple_stats
> > - script: shell/simple_stats.sh
> >
> > The shell script takes "start" or "stop" as $1 to set up the scenario.
> > For developing more test, having the separated shell script might be
> > convenient.
> >
>
> This is already supported:
>
> === 8< ===
> - name: myscenario
> start:
> - ./script.sh start
> stop:
> - ./script.sh stop
> === 8< ===
Ok, I've sent a patch to move the netns network setup to a shell
script:
https://patchwork.ozlabs.org/project/netfilter-devel/patch/20210201170015.28217-1-pablo@netfilter.org/
> > Thanks !
> >
>
> Thanks for the review. I made the changes you requested and pushed it to the
> repository.
>
> I plan to follow up soon with more tests.
>
> Question: I have a few testcases that trigger bugs, segfaults etc. Would it
> be OK to create something like 'failingtestcases.yaml' and register all
> those bugs there until the get fixed? That way we have reproducible bugs
> until we can fix them.
That's fine, but before we add more tests, please let's where to move
more inlined configurations in the yaml files to independent files
that can be reused by new tests.
Thanks.
next prev parent reply other threads:[~2021-02-01 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 0:22 [conntrack-tools PATCH 1/3] tests: introduce new python-based framework for running tests Arturo Borrero Gonzalez
2021-01-24 0:25 ` [conntrack-tools PATCH 2/3] tests: introduce some basic testcases for the new conntrack-tools testing framework Arturo Borrero Gonzalez
2021-01-24 0:29 ` [conntrack-tools PATCH 3/3] tests: introduce replicating scenario and simple icmp test case Arturo Borrero Gonzalez
2021-02-01 3:31 ` [conntrack-tools PATCH 1/3] tests: introduce new python-based framework for running tests Pablo Neira Ayuso
2021-02-01 10:49 ` Arturo Borrero Gonzalez
2021-02-01 17:05 ` Pablo Neira Ayuso [this message]
2021-02-02 10:23 ` Arturo Borrero Gonzalez
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=20210201170551.GA28275@salvia \
--to=pablo@netfilter.org \
--cc=arturo@netfilter.org \
--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 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.