You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/UtUtilsClass.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -12,11 +12,11 @@ Previously UnitTestBot generated _utility methods_ for each test class when they
12
12
13
13
For now UnitTestBot provides a special `UtUtils` class containing all _utility methods_ if at least one test class needs some of them. This class is generated once and the specific methods are imported from it if necessary. No need for _utility methods_ — no `UtUtils` class is generated.
14
14
15
-
We create a separate `UtUtils` class for each supported codegen language (is this class is required).
15
+
We create a separate `UtUtils` class for each supported codegen language (if this class is required).
16
16
17
17
## What does it look like
18
18
19
-
Here is as example of documentation comment inherent to every `UtUtils` class:
19
+
Here is an example of documentation comment inherent to every `UtUtils` class:
20
20
21
21

22
22
@@ -41,7 +41,7 @@ rely on the proper methods from `UtUtils` class.
41
41
42
42
## Where to find it
43
43
44
-
`UtUtils` class is usually located in the chosen **Test sources root** near the generated test classes, it's package is named after the selected codegen language.
44
+
`UtUtils` class is usually located in the chosen **Test sources root** near the generated test classes. The corresponding package name mentions the language of the generated tests: e.g. `org.utbot.runtime.utils.java`.
0 commit comments