AGENTS.md: async_test::test for async unit tests
What the developer wrote
Authored by Marko Bencun
AGENTS.md: async_test::test for async unit tests
What changed, and why it matters
This commit adds a single coding-style guideline to the project's AGENTS.md file, instructing developers to use a specific Rust attribute for asynchronous unit tests. It does not change any source code, tests, build scripts, or configuration that could affect device behavior or security.
No security action required. This is a non-functional documentation change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a one-line addition to AGENTS.md recommending #[async_test::test] async fn test_... for Rust unit tests involving futures. It is purely documentation/coding-convention guidance with no functional, cryptographic, or build-system changes.
Changed components
AGENTS.md (developer guidelines documentation)Inspect captured patch +1 / −0
diff --git a/AGENTS.md b/AGENTS.md
index 712f0e7..0d7bdbf 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -71,6 +71,7 @@ security-sensitive areas.
- in Rust unit tests, prefer .unwrap() over .expect().
- In Rust unit tests, if testing a function foo, name the test `test_foo` (or `test_foo_xyz` if it
needs qualifiers).
+- if a Rust unit test involves futures, use `#[async_test::test] async fn test_...`.
- in Rust unit tests, prefer .as_slice() instead of `&*` for wrapped/zeroized Vec<u8>.
- in Rust unit tests, prefer `hex!` literals for byte arrays/constants.
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.