From 2394c83b889665eae6d8eecd8a55cd356aeaf665 Mon Sep 17 00:00:00 2001 From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com> Date: Fri, 2 May 2025 09:44:53 -0400 Subject: [PATCH] docs: fix dead link in 16-testing.md (backport #24643) (#24644) Co-authored-by: GarmashAlex --- docs/docs/build/building-modules/16-testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/build/building-modules/16-testing.md b/docs/docs/build/building-modules/16-testing.md index 4b1d005eba..81f5a25a1b 100644 --- a/docs/docs/build/building-modules/16-testing.md +++ b/docs/docs/build/building-modules/16-testing.md @@ -9,7 +9,7 @@ These tests have different goals and are used at different stages of the develop We advice, as a general rule, to use tests at all stages of the development cycle. It is adviced, as a chain developer, to test your application and modules in a similar way than the SDK. -The rationale behind testing can be found in [ADR-59](https://docs.cosmos.network/main/architecture/adr-059-test-scopes.html). +The rationale behind testing can be found in [ADR-59](https://docs.cosmos.network/main/build/architecture/adr-059-test-scopes). ## Unit Tests