From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/5] support/testing: add core tests
Date: Wed, 22 Mar 2017 09:25:31 +0100 [thread overview]
Message-ID: <20170322092531.2b299231@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LV-OfyZsEoX0Ja8KndLoA5MM=OyuwMTAvi9ptUP1SvzXQ@mail.gmail.com>
Hello,
On Wed, 22 Mar 2017 09:17:59 +0100, Thomas De Schampheleire wrote:
> Two minor comments:
>
> I think it would be cleaner to move support files for tests, like the
> post-build.sh and post-image.sh and rootfs-overlays, to a subdirectory
> instead of in the same location as the tests.
Can you suggest a name for this subdirectory ? :-)
> Also, I would argue that the rootfs-overlays do not need to be real
> files in git but can be generated on the fly during the test.
I tried to do that, but:
1. It complicates quite a bit the test scenario.
2. There are plenty of other test cases where we will really need some
data that cannot be generated: a set of patches to test if patches
on packages are properly applied, a set of dummy BR2_EXTERNAL
trees, etc. So we will anyway have some "supporting" artifacts in
the tree, and therefore I thought it wasn't worth the effort making
this test more complicated.
Yann did the exact same comment while reviewing the previous version,
so I tried generating the files automatically, and went through this
reasoning before giving up and keeping things as they are.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-22 8:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 20:36 [Buildroot] [PATCH v3 0/5] Runtime testing infrastructure Thomas Petazzoni
2017-03-20 20:36 ` [Buildroot] [PATCH v3 1/5] support/testing: core " Thomas Petazzoni
2017-03-22 8:11 ` Thomas De Schampheleire
2017-03-23 3:02 ` Ricardo Martincoski
2017-03-23 8:07 ` Thomas Petazzoni
2017-03-24 2:19 ` Ricardo Martincoski
2017-03-26 21:54 ` Luca Ceresoli
2017-05-07 21:07 ` Luca Ceresoli
2017-05-07 21:38 ` Thomas Petazzoni
2017-03-20 20:36 ` [Buildroot] [PATCH v3 2/5] support/testing: add core tests Thomas Petazzoni
2017-03-22 8:17 ` Thomas De Schampheleire
2017-03-22 8:25 ` Thomas Petazzoni [this message]
2017-03-22 8:35 ` Thomas De Schampheleire
2017-03-20 20:36 ` [Buildroot] [PATCH v3 3/5] support/testing: add fs tests Thomas Petazzoni
2017-05-07 20:55 ` Luca Ceresoli
2017-03-20 20:36 ` [Buildroot] [PATCH v3 4/5] support/testing: add package tests Thomas Petazzoni
2017-03-22 8:26 ` Thomas De Schampheleire
2017-03-22 13:08 ` Thomas Petazzoni
2017-03-20 20:36 ` [Buildroot] [PATCH v3 5/5] support/testing: add toolchain tests Thomas Petazzoni
2017-03-26 21:53 ` Luca Ceresoli
2017-03-22 8:30 ` [Buildroot] [PATCH v3 0/5] Runtime testing infrastructure Thomas De Schampheleire
2017-05-07 20:09 ` Thomas Petazzoni
2017-05-07 20:41 ` Luca Ceresoli
2017-05-07 21:10 ` 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=20170322092531.2b299231@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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.