21 releases

new 0.29.0 Feb 6, 2025
0.28.3 Nov 14, 2024
0.28.2 Oct 8, 2024
0.28.0 Jun 11, 2024
0.22.0 Dec 16, 2022

#138 in Testing

Download history 30946/week @ 2024-10-21 25225/week @ 2024-10-28 25661/week @ 2024-11-04 23740/week @ 2024-11-11 24506/week @ 2024-11-18 20791/week @ 2024-11-25 25605/week @ 2024-12-02 24500/week @ 2024-12-09 27512/week @ 2024-12-16 9836/week @ 2024-12-23 12794/week @ 2024-12-30 26626/week @ 2025-01-06 30507/week @ 2025-01-13 31729/week @ 2025-01-20 31097/week @ 2025-01-27 31966/week @ 2025-02-03

126,143 downloads per month
Used in 35 crates (via uniffi_bindgen)

MPL-2.0 license

10KB
138 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.2–2.1MB
~42K SLoC