From cb2e40a9b265707feb627d853abfef4b70503610 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yann=20C=C3=A9bron?= Date: Tue, 25 Mar 2025 14:04:10 +0100 Subject: [PATCH] testing_plugins.md: fix link --- topics/basics/testing_plugins/testing_plugins.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/topics/basics/testing_plugins/testing_plugins.md b/topics/basics/testing_plugins/testing_plugins.md index b02da5c6d..2f135e11f 100644 --- a/topics/basics/testing_plugins/testing_plugins.md +++ b/topics/basics/testing_plugins/testing_plugins.md @@ -1,4 +1,4 @@ - + # Testing Overview @@ -23,7 +23,7 @@ Another consequence of our testing approach is that we do not provide a recommen We have a few tests in our codebase that use JMock. Still, in general, we find it difficult to mock all the interactions with IntelliJ Platform components that your plugin class will need to have. We recommend working with real components instead. -See also [](testing_faq.md#how-to-replace-componentservice-in-tests) and [](testing_faq.md#how-to-replace-extension-points-in-tests). +See also [](testing_faq.md#how-to-replace-a-componentservice-in-tests) and [](testing_faq.md#how-to-replace-extension-points-in-tests). ### Integration and UI Tests