| commit | ae37a296205c9f94caa4a6fef82ac8fac0d89615 | [log] [tgz] |
|---|---|---|
| author | James Farrell <[email protected]> | Wed Aug 07 22:47:53 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Wed Aug 07 22:47:53 2024 +0000 |
| tree | 81c83f451cc39c213a239fa658e4f5a351e8bff4 | |
| parent | 8de54872804f68b7043516685a1f0ae67cd3fea1 [diff] | |
| parent | 9d456d0b79454ab8c7b8576dce256d5463d24eeb [diff] |
Update Android.bp by running cargo_embargo am: 9d456d0b79 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/serde_test/+/3208435 Change-Id: I4f0e90a5dad7d2fd8cf83de7cb1716547f2d81e2 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, ], ); }