Numerous unit test assertions when running DemoRunner

General JUCE discussion
1

Hi team,

Running the unit tests directly in the DemoRunner triggers many immediate assertions.

Tests such as ComponentTests, AudioProcessorTests, and AudioDeviceManagerTests all fail right away with JUCE_ASSERT_MESSAGE_THREAD and jassertfalse. This appears to stem from the TestRunnerThread environment rather than the tests themselves.

Reproducible on macOS Tahoe 26.0.1 with Xcode 16.4.0, desktop.

There are also a few assertions in the VST3 processor code (eg: getBlankBuffer) that get triggered.

Might be worth giving these a spin in the DemoRunner just to confirm they still behave as intended.

Thanks!

2

These should run as intended (please let us know if not), the assertions in this case can be safely ignored. For running tests under a debugger I suggest using the UnitTestRunner rather than the DemoRunner as then most of those assertions won’t hit. I would like to put some time into improving this in the future but we have some other priorities to get to first.

Thanks for reporting.

3

Noted and I totally understand. Thanks!