Hi Mark
On Wed, Feb 4, 2026 at 2:38 PM Mark Cave-Ayland
<[email protected]> wrote:
>
> On 23/01/2026 07:49, [email protected] wrote:
>
> > From: Marc-André Lureau <[email protected]>
> >
> > Start a simple test program that will exercise the QEMU audio APIs.
> >
> > It is meant to run manually for now, as it accesses the sound system and
> > produces sound by default, and also runs for a few seconds. We may want
> > to make it silent or use the "none" (noaudio) backend by default though,
> > so it can run as part of the automated test suite.
>
> I wonder if it makes sense to have some kind of qtest audio backend that
> can write the resulting data to a file for tests like this without
> generating audio?
Yes, we could have some tests using the "wav" backend. Although I
think this is pretty limited. I'd rather leave that for now.
>
> > +
> > +# manual audio test - not part of automated test suite
> > +# as it relies on audio system
> > +executable('test-audio',
> > + sources: files('test-audio.c', 'audio-stubs.c'),
> > + dependencies: [audio, qemuutil, spice, modinfo_dep],
>
> Does this test really need spice to function?
>
> > + build_by_default: false)
>
> It took me a few seconds to see why the test-audio executable wasn't
> being produced, even if it has to be run manually. Is there any reason
> it shouldn't be built by default?
No, I thought if it is manual it should perhaps be that way, but
that's also not a good idea. I will change it.
btw, I also fixed the test so it can run with -a wav,file=output.wav
(the test currently requires input handling, which is not handled by
wav)
