All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/5] support/testing: add python-twisted tests
Date: Sat, 13 Oct 2018 14:48:02 +0200	[thread overview]
Message-ID: <20181013144802.72c8bf88@windsurf> (raw)
In-Reply-To: <1adacc2a-25dc-eee5-8688-47ce66aa080b@mind.be>

Hello,

On Thu, 11 Oct 2018 23:27:10 +0200, Arnout Vandecappelle wrote:

> > At some point, we will have to find a solution to store such
> > "artefacts" somewhere, instead of having them inline in their test
> > cases. I don't have a good idea about this.  
> 
>  I think it would be nice if we could add in the package directory a
> subdirectory with files to be copied to the target for the runtime test, and a
> python script for the test itself.
> 
>  As an in-between step, we can put the files-to-be-copied inside the
> support/testing directory and explicitly enumerate the files-to-be-copied in the
> test fixture.

I am still hesitant between putting the tests + fixtures near/in the
packages themselves, and keeping the whole test suite thing separate.
One issue with putting the tests+fixture near/in the packages is that a
number of tests aren't package-related, so where do we put them? Isn't
that also going to put a lot of mess/cruft in our packages?

I don't have a good answer to that. Perhaps for now it makes more sense
to have those test fixtures in support/testing/, and see where to go
from there.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-10-13 12:48 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26  2:55 [Buildroot] [PATCH 0/5] a few more runtime test cases for python packages - series 1/n Ricardo Martincoski
2018-09-26  2:55 ` [Buildroot] [PATCH 1/5] support/testing: add python-autobahn tests Ricardo Martincoski
2018-09-26  7:07   ` Yegor Yefremov
2018-09-26  2:55 ` [Buildroot] [PATCH 2/5] support/testing: add python-txaio tests Ricardo Martincoski
2018-09-26  7:08   ` Yegor Yefremov
2018-09-26  2:55 ` [Buildroot] [PATCH 3/5] support/testing: add python-txtorcon tests Ricardo Martincoski
2018-09-26  7:21   ` Yegor Yefremov
2018-09-26  2:55 ` [Buildroot] [PATCH 4/5] support/testing: add python-incremental tests Ricardo Martincoski
2018-09-26  7:09   ` Yegor Yefremov
2018-10-11 18:46   ` Thomas Petazzoni
2018-10-14 22:07     ` Ricardo Martincoski
2018-09-26  2:55 ` [Buildroot] [PATCH 5/5] support/testing: add python-twisted tests Ricardo Martincoski
2018-09-26  7:20   ` Yegor Yefremov
2018-09-29  5:35   ` Ricardo Martincoski
2018-10-11 18:48   ` Thomas Petazzoni
2018-10-11 21:27     ` Arnout Vandecappelle
2018-10-13 12:48       ` Thomas Petazzoni [this message]
2018-10-13 14:43       ` Yann E. MORIN
2018-10-14 22:11         ` Ricardo Martincoski
2018-10-14 22:08       ` Ricardo Martincoski
2018-10-11 18:42 ` [Buildroot] [PATCH 0/5] a few more runtime test cases for python packages - series 1/n Thomas Petazzoni
2018-10-11 18:53   ` Thomas Petazzoni
2018-11-16  3:57 ` [Buildroot] [next 00/15] a few more runtime test cases for python packages - series 2/n Ricardo Martincoski
2018-11-16  3:57   ` [Buildroot] [next 01/15] support/testing: add python-argh tests Ricardo Martincoski
2018-11-16  3:57   ` [Buildroot] [next 02/15] support/testing: add python-attrs tests Ricardo Martincoski
2018-11-16  3:57   ` [Buildroot] [next 03/15] support/testing: add python-automat tests Ricardo Martincoski
2018-11-16  3:57   ` [Buildroot] [next 04/15] support/testing: add python-bitstring tests Ricardo Martincoski
2018-11-16  3:57   ` [Buildroot] [next 05/15] support/testing: add python-cbor tests Ricardo Martincoski
2018-11-16  3:57   ` [Buildroot] [next 06/15] support/testing: add python-click tests Ricardo Martincoski
2018-11-16  3:57   ` [Buildroot] [next 07/15] support/testing: add python-constantly tests Ricardo Martincoski
2018-11-16  3:57   ` [Buildroot] [next 08/15] support/testing: add python-passlib tests Ricardo Martincoski
2018-11-16  3:57   ` [Buildroot] [next 09/15] support/testing: add python-pexpect tests Ricardo Martincoski
2018-11-16  3:57   ` [Buildroot] [next 10/15] support/testing: add python-pynacl tests Ricardo Martincoski
2018-11-16  3:57   ` [Buildroot] [next 11/15] support/testing: add python-pyyaml tests Ricardo Martincoski
2018-11-16  3:57   ` [Buildroot] [next 12/15] support/testing: add python-service-identity tests Ricardo Martincoski
2018-11-16  3:57   ` [Buildroot] [next 13/15] support/testing: add python-subprocess32 test Ricardo Martincoski
2018-11-16  3:57   ` [Buildroot] [next 14/15] support/testing: add python-treq tests Ricardo Martincoski
2018-11-16  3:57   ` [Buildroot] [next 15/15] support/testing: add python-ubjson tests Ricardo Martincoski
2018-11-23 21:09   ` [Buildroot] [next 00/15] a few more runtime test cases for python packages - series 2/n Thomas Petazzoni

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=20181013144802.72c8bf88@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.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 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.