From: Andreas Ziegler <br025@umbiko.net>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot@buildroot.org, Marcus Hoffmann <buildroot@bubu1.eu>
Subject: Re: [Buildroot] [PATCH v2 00/11] add runtime test for mpd
Date: Sun, 12 Jul 2026 02:54:33 +0000 [thread overview]
Message-ID: <6bcdaf687d3e8f1ad510222635953536@umbiko.net> (raw)
In-Reply-To: <c06472fc-be68-49ce-9a8f-a8411be6d520@gmx.de>
Hi Fiona,
On 2026-07-11 10:24, Fiona Klute wrote:
> Hi Andreas,
>
> thank you for working on these tests!
>
> Am 09.07.26 um 13:08 schrieb Andreas Ziegler:
>> Testing MPD in a real world situation is fairly straightforward:
>> build,
>> deploy, play some music. Representing this simple test within a test
>> framework is quite complex.
>>
>> I tried to break down my simple test case into a few atomic steps that
>> interact with MPD via the built-in protocol. The necessary test data
>> was
>> generated with ffmpeg and imagemagick and is royalty-free :-D
>>
>> In good old usenet tradition, test data had to be split in archive
>> chunks, to overcome the limitations of the mailing list. The data will
>> be re-combined in a post-build script.
>
> I don't like the idea of adding a bunch of binary test data to the
> repository. Why not generate it as part of the test or build? Sure,
> adding ffmpeg/imagemagick to the config would make the build heavier,
> but having a clearly visible generation command and no binary data in
> the repository seems more important to me.
No, I do not recommend to add test data generation to the test.
Both ffmpeg and imagemagick are highly complex applications, in at least
the same order of complexity as MPD. Adding them to the test would
introduce additional points of failure, which are not relevant to the
actual test objective. Test data should be invariant; if it changes with
every test, results might not be comparable.
Buildroot has a mirror somewhere for supplying source packages. Could
the test data be put there? If all else fails, I might put the data in
some repository, and download it during build.
Kind regards,
Andreas
> Best regards,
> Fiona
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-07-12 2:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 11:08 [Buildroot] [PATCH v2 00/11] add runtime test for mpd Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 01/11] package/mpd: install provided sample configuration file as mpd.conf Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 02/11] package/mpd: remove duplicated dependencies from sub-options Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 03/11] package/mpd: reorder config items based on order in meson_options.txt Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 04/11] support/testing: add test data for mpd (1/6) Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 05/11] support/testing: add test data for mpd (2/6) Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 06/11] support/testing: add test data for mpd (3/6) Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 07/11] support/testing: add test data for mpd (4/6) Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 08/11] support/testing: add test data for mpd (5/6) Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 09/11] support/testing: add test data for mpd (6/6) Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 10/11] support/testing: add runtime test for mpd Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 11/11] DEVELOPERS: add entry for test_mpd Andreas Ziegler
2026-07-11 10:24 ` [Buildroot] [PATCH v2 00/11] add runtime test for mpd Fiona Klute via buildroot
2026-07-12 2:54 ` Andreas Ziegler [this message]
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=6bcdaf687d3e8f1ad510222635953536@umbiko.net \
--to=br025@umbiko.net \
--cc=buildroot@bubu1.eu \
--cc=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
/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