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
`Fairy` object should not be used concurrently by multiple threads. It is recommended to create `Fairy` instance for each thread.
106
-
107
-
Some methods are not thread-safe when multiple threads share the same `Fairy` object. For other methods it is still recommended to create a separate `Fairy` object, because `Random` object utilized underneath does not perform well when used concurrently by multiple threads.
108
-
109
-
## Other samples
110
+
`Fairy` objects are not designed for concurrent use by multiple threads.
111
+
It is recommended to create a separate `Fairy` instance for each thread.
110
112
111
-
Look into [code samples](https://github.com/SkillPanel/jfairy/tree/master/src/test/groovy/snippets/)
113
+
While some methods might appear safe, the underlying `Random` implementation can lead to contention and poor performance. Creating dedicated instances ensures both thread safety and optimal execution speed.
112
114
113
115
## JUnit 5 Extension
114
116
115
-
If you use JUnit 5, check out [jfairy-junit-extension](https://github.com/SkillPanel/jfairy-junit-extension) — a JUnit 5 extension that allows injecting jFairy-generated objects directly into test method parameters.
117
+
If you use JUnit 5, check out [jfairy-junit-extension](https://github.com/SkillPanel/jfairy-junit-extension) — an extension that allows injecting jFairy-generated objects directly into test method parameters.
116
118
117
119
## Building
118
120
119
-
This project can be built using maven command:
121
+
This project uses Maven and can be built using the provided wrapper:
0 commit comments