21 releases

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

#136 in Testing

Download history 25368/week @ 2024-10-27 25544/week @ 2024-11-03 23409/week @ 2024-11-10 24482/week @ 2024-11-17 20658/week @ 2024-11-24 25905/week @ 2024-12-01 24711/week @ 2024-12-08 27689/week @ 2024-12-15 9869/week @ 2024-12-22 12618/week @ 2024-12-29 26527/week @ 2025-01-05 30458/week @ 2025-01-12 31093/week @ 2025-01-19 31512/week @ 2025-01-26 33005/week @ 2025-02-02 30802/week @ 2025-02-09

127,532 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.1–2.1MB
~42K SLoC