| commit | f1a20a4599a714ea5cb47c74e384c7c84fe24de7 | [log] [tgz] |
|---|---|---|
| author | James Farrell <jamesfarrell@google.com> | Tue May 21 19:08:41 2024 +0000 |
| committer | James Farrell <jamesfarrell@google.com> | Tue May 21 19:08:41 2024 +0000 |
| tree | 14b382e40033abb0437ddc432233761e8dbf2567 | |
| parent | a420137dc48e96c90d2e846f2741de771c1aee60 [diff] |
Update Android.bp by running cargo_embargo Test: ran cargo_embargo Change-Id: If2493b62cb2f9016ae3b0fc5b84a23050f888466
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, ], ); }