From 6f91734b0eb486a551d378d7fc6dd2b8b773b74e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yann=20C=C3=A9bron?= Date: Thu, 8 Apr 2021 15:47:28 +0200 Subject: [PATCH] light_and_heavy_tests.md: format --- topics/basics/testing_plugins/light_and_heavy_tests.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/topics/basics/testing_plugins/light_and_heavy_tests.md b/topics/basics/testing_plugins/light_and_heavy_tests.md index db0806bf8..c3d914c34 100644 --- a/topics/basics/testing_plugins/light_and_heavy_tests.md +++ b/topics/basics/testing_plugins/light_and_heavy_tests.md @@ -29,7 +29,8 @@ The standard way of writing a light test is to extend the following classes: When writing a light test, you can specify the project's requirements that you need to have in your test, such as the module type, the configured SDK, facets, libraries, etc. You do so by extending the [`LightProjectDescriptor`](upsource:///platform/testFramework/src/com/intellij/testFramework/LightProjectDescriptor.java) class and returning your project descriptor from `getProjectDescriptor()`. -Before executing each test, the project will be reused if the test case returns the same project descriptor (usually stored in static final field) as the previous one, or recreated if the descriptor is different (`equals() = false`). + +Before executing each test, the project instance will be reused if the test case returns the same project descriptor (usually stored in static final field) as the previous one, or recreated if the descriptor is different (`equals() = false`). ## Heavy Tests