| commit | 8de54872804f68b7043516685a1f0ae67cd3fea1 | [log] [tgz] |
|---|---|---|
| author | James Farrell <[email protected]> | Wed May 22 23:45:04 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Wed May 22 23:45:04 2024 +0000 |
| tree | 14b382e40033abb0437ddc432233761e8dbf2567 | |
| parent | c414cfc192a21c19ec4d8fcded9c165f4de2f090 [diff] | |
| parent | ba1d3b5ff7c0d9bc2e64b03b0cc378166d065ad1 [diff] |
Update Android.bp by running cargo_embargo am: f1a20a4599 am: ba1d3b5ff7 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/serde_test/+/3096360 Change-Id: Id470924b4e86d65623d5d663126344e907d76c1f Signed-off-by: Automerger Merge Worker <[email protected]>
This crate provides a convenient concise way to write unit tests for implementations of Serialize and Deserialize.
The Serialize impl for a value can be characterized by the sequence of Serializer calls that are made in the course of serializing the value, so serde_test provides a [Token] abstraction which corresponds roughly to Serializer method calls. There is an [assert_ser_tokens] function to test that a value serializes to a particular sequence of method calls, an [assert_de_tokens] function to test that a value can be deserialized from a particular sequence of method calls, and an [assert_tokens] function to test both directions. There are also functions to test expected failure conditions.
Here is an example from the linked-hash-map crate.
use linked_hash_map::LinkedHashMap; use serde_test::{assert_tokens, Token}; #[test] fn test_ser_de_empty() { let map = LinkedHashMap::<char, u32>::new(); assert_tokens( &map, &[ Token::Map { len: Some(0) }, Token::MapEnd, ], ); } #[test] fn test_ser_de() { let mut map = LinkedHashMap::new(); map.insert('b', 20); map.insert('a', 10); map.insert('c', 30); assert_tokens( &map, &[ Token::Map { len: Some(3) }, Token::Char('b'), Token::I32(20), Token::Char('a'), Token::I32(10), Token::Char('c'), Token::I32(30), Token::MapEnd, ], ); }