diff --git a/lucene/test-framework/src/java/org/apache/lucene/util/LuceneTestCase.java b/lucene/test-framework/src/java/org/apache/lucene/util/LuceneTestCase.java index 82cfda014a4..5639c318ed7 100644 --- a/lucene/test-framework/src/java/org/apache/lucene/util/LuceneTestCase.java +++ b/lucene/test-framework/src/java/org/apache/lucene/util/LuceneTestCase.java @@ -56,11 +56,11 @@ import com.carrotsearch.randomizedtesting.rules.SystemPropertiesInvariantRule; *
* The preferred way to specify class (suite-level) setup/cleanup is to use * static methods annotated with {@link BeforeClass} and {@link AfterClass}. Any - * code in these methods us executed withing the test framework's control and + * code in these methods is executed within the test framework's control and * ensure proper setup has been made. Try not to use static initializers * (including complex final field initializers). Static initializers are - * executed before any setup rules can be executed and may cause you (or - * somebody else) headaches. + * executed before any setup rules are fired and may cause you (or somebody + * else) headaches. * *
* For instance-level setup, use {@link Before} and {@link After} annotated @@ -91,14 +91,14 @@ import com.carrotsearch.randomizedtesting.rules.SystemPropertiesInvariantRule; * just dump the stack trace of all threads and you'll see the seed), *
There is a number of other facilities tests can use, like: *