`sweettest` - HackMD

# `sweettest` Ergonomic test framework for testing Holochain DNAs in Rust _by @maackle_ --- ## `sweettest` vs. `tryorama` ---- - `tryorama` - tests are written in JS - spawns a separate Conductor process, and talks to it over a Websocket using the Conductor API - `sweettest` - tests are written in pure Rust - runs a Conductor in-process and talks to it using simple function calls - this means you can use the Rust types defined in your Zome directly ---- ## What does sweettest provide that tryorama doesn't? - You can write tests in terms of types from zome code, rather than using JSON-serialized representations - Your test code is more likely to stay in sync with your zome code, since they are both type-checked together - You can define an on-the-fly `InlineZome` in Rust to mix in to your normal Dna - There is no ergonomic way to do this yet, but it can be done! ---- ## Inline Zomes ```rust= let entry_def = EntryDef::default_with_id("entrydef"); InlineZome::new_unique(vec![entry_def.clone()]) .callback("create", move |api, ()| { let entry_def_id: EntryDefId = entry_def.id.clone(); let entry = Entry::app(().try_into().unwrap()).unwrap(); let hash = api.create(CreateInput::new( entry_def_id, entry, ChainTopOrdering::default(), ))?; Ok(hash) }) .callback("read", |api, hash: HeaderHash| { api.get(vec![GetInput::new(hash.into(), GetOptions::default())]) .map(|e| e.into_iter().next().unwrap()) .map_err(Into::into) }) ``` --- ## Migrating to sweettest This example explains a lot of the translation needed [tryorama](https://github.com/holochain/elemental-chat/blob/sweettest-example/tests/src/basic-chatting.ts) → [sweettest](https://github.com/holochain/elemental-chat/blob/sweettest-example/zomes/chat/tests/basic_chatting.rs) ---- ## [sweettest docs](https://docs.rs/holochain/0.0.109/holochain/sweettest/index.html) --- have a sweet day :lollipop: