| commit | ff33d27189229d1b8895505b1d0d6ebdf0836f70 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Tue Apr 30 23:16:54 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Tue Apr 30 23:16:54 2024 +0000 |
| tree | 441740faf26afb9045263f16a15c9519476b5911 | |
| parent | a7d88a70c776da1b830f0313c046af612750768b [diff] | |
| parent | c414cfc192a21c19ec4d8fcded9c165f4de2f090 [diff] |
Snap for 11784291 from c414cfc192a21c19ec4d8fcded9c165f4de2f090 to 24Q3-release Change-Id: I29ebee81f2d79e4baa4694ab0b8726081398e27d
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, ], ); }