Use track caller in test documentation

1 files changed, 1 insertions, 1 deletions

diff --git a/docs/dev/architecture.md b/docs/dev/architecture.md
index 01063824f36..081ee5b9d90 100644
--- a/docs/dev/architecture.md
+++ b/docs/dev/architecture.md
@@ -372,11 +372,11 @@ Tests which directly call various API functions are a liability, because they ma
 So most of the tests look like this:
 
 ```rust
+#[track_caller]
 fn check(input: &str, expect: expect_test::Expect) {
     // The single place that actually exercises a particular API
 }
 
-
 #[test]
 fn foo() {
     check("foo", expect![["bar"]]);