From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/5] support/testing: add python-twisted tests
Date: Sat, 13 Oct 2018 16:43:17 +0200 [thread overview]
Message-ID: <20181013144317.GF31509@scaer> (raw)
In-Reply-To: <1adacc2a-25dc-eee5-8688-47ce66aa080b@mind.be>
Arnout, All,
On 2018-10-11 23:27 +0200, Arnout Vandecappelle spake thusly:
> On 11/10/18 20:48, Thomas Petazzoni wrote:
> > Hello,
> >
> > On Tue, 25 Sep 2018 23:55:14 -0300, Ricardo Martincoski wrote:
> >
> >> +TEST_SCRIPT = """
> >> +from twisted.internet import protocol, reactor, endpoints
> >> +class F(protocol.Factory):
> >> + pass
> >> +endpoints.serverFromString(reactor, "tcp:1234").listen(F())
> >> +reactor.run()
> >> +"""
> >
> > 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.
I'm not sure that would answer the question, but I already worked on
moving the packages' tests files inside the packages directories:
https://git.buildroot.org/~ymorin/git/buildroot/log/?h=yem/package-tests
(Note that this branch is not entirely up-to-date, as I haven't updated
it since we added new package tests.)
Contrary to Thomas, I don't really mind that we have tests in two
locations. Per-paclages tests are, in y opinion, better to be
side-by-side with the package they test.
As for the test on the infra, they go where they make more sense: in the
test infra.
My 2cts.
Regards,
Yann E. MORIN.
> 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.
>
> Regards,
> Arnout
>
> --
> Arnout Vandecappelle arnout at mind be
> Senior Embedded Software Architect +32-16-286500
> Essensium/Mind http://www.mind.be
> G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-10-13 14:43 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
2018-10-13 14:43 ` Yann E. MORIN [this message]
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=20181013144317.GF31509@scaer \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox