15 unstable releases (5 breaking)

new 0.27.2 May 15, 2024
0.27.0 Mar 26, 2024
0.25.3 Dec 7, 2023
0.25.2 Nov 20, 2023
0.22.0 Dec 16, 2022

#159 in Testing

Download history 14448/week @ 2024-01-24 17176/week @ 2024-01-31 16913/week @ 2024-02-07 15520/week @ 2024-02-14 16221/week @ 2024-02-21 16895/week @ 2024-02-28 17617/week @ 2024-03-06 16732/week @ 2024-03-13 18735/week @ 2024-03-20 12616/week @ 2024-03-27 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 17479/week @ 2024-05-08

81,714 downloads per month
Used in 27 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
~41K SLoC