#uni-ffi #helper

uniffi_testing

a multi-language bindings generator for rust (testing helpers)

22 releases

0.29.1 Mar 18, 2025
0.28.3 Nov 14, 2024
0.28.0 Jun 11, 2024
0.27.0 Mar 26, 2024
0.22.0 Dec 16, 2022

#187 in Testing

Download history 9171/week @ 2024-12-24 15069/week @ 2024-12-31 27950/week @ 2025-01-07 29031/week @ 2025-01-14 33526/week @ 2025-01-21 31226/week @ 2025-01-28 32679/week @ 2025-02-04 29487/week @ 2025-02-11 31230/week @ 2025-02-18 31967/week @ 2025-02-25 28409/week @ 2025-03-04 25784/week @ 2025-03-11 27194/week @ 2025-03-18 29238/week @ 2025-03-25 24977/week @ 2025-04-01 25772/week @ 2025-04-08

111,874 downloads per month
Used in 35 crates (2 directly)

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
~41K SLoC