fluidsynth/test
2019-09-29 01:16:42 +02:00
..
CMakeLists.txt add test of fluid_zone_check_mod() 2019-07-28 03:15:21 +02:00
README.md remove cmake option enable-tests 2018-08-05 20:50:41 +02:00
test.h Suppress abort() dialog on windows (#549) 2019-08-06 17:29:49 +02:00
test_fluid_zone_check_mod.c More comments in test_fluid_zone_check_mod.c 2019-09-15 22:28:42 +02:00
test_modulator_amount.c fix random unit test failure 2019-08-06 17:36:25 +02:00
test_modulator_links.c Replace space by underscore in list name 2019-09-29 01:16:42 +02:00
test_pointer_alignment.c enforce coding style guide 2018-06-24 13:13:18 +02:00
test_preset_sample_loading.c fix building CoreAudio on OSX 10.4 2019-02-15 17:55:02 +01:00
test_sample_cache.c fix building CoreAudio on OSX 10.4 2019-02-15 17:55:02 +01:00
test_sample_rate_change.c fix building CoreAudio on OSX 10.4 2019-02-15 17:55:02 +01:00
test_seqbind_unregister.c Fix memory leak in test_seqbind_unregister 2019-07-10 17:01:01 +02:00
test_sf3_sfont_loading.c fix building CoreAudio on OSX 10.4 2019-02-15 17:55:02 +01:00
test_sfont_loading.c fix building CoreAudio on OSX 10.4 2019-02-15 17:55:02 +01:00
test_snprintf.c fix building CoreAudio on OSX 10.4 2019-02-15 17:55:02 +01:00
test_synth_chorus_reverb.c enforce coding style guide 2018-06-24 13:13:18 +02:00
test_synth_process.c fix build with MSVC 2019-04-17 19:20:36 +02:00

This directory contains small executables to verify fluidsynths correct behaviour, i.e. unit tests.

Do not blindly use the tests as template for your application!

Although some tests might serve as educational demonstration of how to use certain parts of fluidsynth, they are not intended to do so! It is most likely that those tests will consist of many hacky parts that are necessary to test fluidsynth (e.g. including fluidsynth's private headers to access internal data types and functions). For user applications this programming style is strongly discouraged! Keep referring to the documentation and code examples listed in the API documentation.

Developers

To add a unit test just duplicate an existing one, give it a unique name and update the CMakeLists.txt by

  • adding a call to ADD_FLUID_TEST() and
  • a dependency to the custom check target.

Execute the tests via make check. Unit tests should use the VintageDreamsWaves-v2.sf2 as test soundfont. Use the TEST_SOUNDFONT macro to access it.