19 unstable releases (6 breaking)

0.28.2 Oct 8, 2024
0.28.0 Jun 11, 2024
0.27.0 Mar 26, 2024
0.25.3 Dec 7, 2023
0.22.0 Dec 16, 2022

#181 in Testing

Download history 19271/week @ 2024-06-26 20441/week @ 2024-07-03 18462/week @ 2024-07-10 21460/week @ 2024-07-17 22661/week @ 2024-07-24 21230/week @ 2024-07-31 24534/week @ 2024-08-07 19107/week @ 2024-08-14 21191/week @ 2024-08-21 20928/week @ 2024-08-28 21937/week @ 2024-09-04 23087/week @ 2024-09-11 21537/week @ 2024-09-18 30496/week @ 2024-09-25 26488/week @ 2024-10-02 22241/week @ 2024-10-09

105,642 downloads per month
Used in 31 crates (2 directly)

MPL-2.0 license

10KB
131 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.2MB
~44K SLoC