17 releases (6 breaking)

0.28.0 Jun 11, 2024
0.27.2 May 15, 2024
0.27.0 Mar 26, 2024
0.25.3 Dec 7, 2023
0.22.0 Dec 16, 2022

#156 in Testing

Download history 18080/week @ 2024-04-03 16050/week @ 2024-04-10 19848/week @ 2024-04-17 19339/week @ 2024-04-24 21947/week @ 2024-05-01 22501/week @ 2024-05-08 27834/week @ 2024-05-15 22524/week @ 2024-05-22 21927/week @ 2024-05-29 24247/week @ 2024-06-05 23150/week @ 2024-06-12 20888/week @ 2024-06-19 19271/week @ 2024-06-26 20441/week @ 2024-07-03 18462/week @ 2024-07-10 16822/week @ 2024-07-17

78,402 downloads per month
Used in 29 crates (2 directly)

MPL-2.0 license

9KB
125 lines

This crate contains helper code for testing bindings. Our general system is to generate bindings for the libraries from the examples and fixtures directories, then execute a script that tests the bindings.

Each bindings crate can do this in a different way, but the typical system is:

  • Construct a UniFFITestHelper struct to assist the process
  • Call UniFFITestHelper.create_out_dir() to create a temp directory to store testing files
  • Call UniFFITestHelper.copy_cdylibs_to_out_dir() to copy the dylib artifacts for the example/fixture library to the out_dir. This is needed because the bindings code dynamically links to or loads from this library.
  • Call UniFFITestHelper.get_compile_sources() to iterate over (udl_path, uniffi_config_path) pairs and generate the bindings from them. This step is specific to the bindings language, it may mean creating a .jar file, compiling a binary, or just copying script files over.
  • Execute the test script and check if it succeeds. This step is also specific to the bindings language.

Dependencies

~1.1–2MB
~40K SLoC