зеркало из https://github.com/mozilla/gecko-dev.git
aff73c9027
Updated uniffi-bindgen-gecko-js to work with UniFFI 0.25.2: - Use `config.toml` to list UniFFI sources. This makes it easier to associate data with them, for example the `crate_name` field that's now required to generate the sources. - Enable the `extern-rustbuffer` feature on `uniffi_core` - Updated the external types fixture to work around https://github.com/mozilla/uniffi-rs/issues/1872 Ran mach vendor and mach cargo vet to update the Rust crates. Differential Revision: https://phabricator.services.mozilla.com/D195163 |
||
|---|---|---|
| .. | ||
| src | ||
| .cargo-checksum.json | ||
| Cargo.toml | ||
| README.md | ||
README.md
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
UniFFITestHelperstruct 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 theout_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.