17 releases (6 breaking)

0.28.0 Jun 11, 2024
0.27.2 May 15, 2024
0.27.0 Mar 26, 2024
0.25.3 Dec 7, 2023
0.22.0 Dec 16, 2022

#149 in Testing

Download history 16241/week @ 2024-02-26 17857/week @ 2024-03-04 16716/week @ 2024-03-11 19633/week @ 2024-03-18 13136/week @ 2024-03-25 16653/week @ 2024-04-01 15867/week @ 2024-04-08 17908/week @ 2024-04-15 20532/week @ 2024-04-22 21035/week @ 2024-04-29 20545/week @ 2024-05-06 28255/week @ 2024-05-13 23816/week @ 2024-05-20 21641/week @ 2024-05-27 22918/week @ 2024-06-03 24762/week @ 2024-06-10

94,003 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