| commit | 9540eb7d8856f5537c8836024832b01f3f0df18c | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Wed Feb 07 00:14:58 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Wed Feb 07 00:14:58 2024 +0000 |
| tree | 441740faf26afb9045263f16a15c9519476b5911 | |
| parent | d97a0370cf221aaf59c9d9f5060f2861ea0e479a [diff] | |
| parent | a7d88a70c776da1b830f0313c046af612750768b [diff] |
Snap for 11413328 from a7d88a70c776da1b830f0313c046af612750768b to 24Q2-release Change-Id: Ic5f929910f609a82cad549a1e8d88d9a19fa002b
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, ], ); }