| commit | 85bae9eb1bee718d24ff3db354398a0d0c30d934 | [log] [tgz] |
|---|---|---|
| author | Treehugger Robot <[email protected]> | Wed Aug 07 22:54:12 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Wed Aug 07 22:54:12 2024 +0000 |
| tree | e330bb756c4ccc8d008aafd42935517a1a61a24d | |
| parent | ae37a296205c9f94caa4a6fef82ac8fac0d89615 [diff] | |
| parent | 56810a4810aa8c453a95dcf7c4fc7a337071587d [diff] |
Merge "Create patch from LICENSE file" into main am: 56810a4810 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/serde_test/+/3211921 Change-Id: Iad2511d3025f085c11ed33011af227b8edc115d0 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, ], ); }