diff --git a/src/test/java/org/apache/commons/collections4/BulkTest.java b/src/test/java/org/apache/commons/collections4/BulkTest.java index 257347737..ddf5172a5 100644 --- a/src/test/java/org/apache/commons/collections4/BulkTest.java +++ b/src/test/java/org/apache/commons/collections4/BulkTest.java @@ -22,13 +22,13 @@ import junit.framework.TestSuite; /** * A {@link TestCase} that can define both simple and bulk test methods. *
- * A simple test method is the type of test traditionally + * A simple test method is the type of test traditionally * supplied by {@link TestCase}. To define a simple test, create a public * no-argument method whose name starts with "test". You can specify * the name of simple test in the constructor of {@code BulkTest}; * a subsequent call to {@link TestCase#run} will run that simple test. *
- * A bulk test method, on the other hand, returns a new instance + * A bulk test method, on the other hand, returns a new instance * of {@code BulkTest}, which can itself define new simple and bulk * test methods. By using the {@link #makeSuite} method, you can * automatically create a hierarchical suite of tests and child bulk tests. @@ -88,7 +88,7 @@ import junit.framework.TestSuite; * simple test methods and no bulk test methods; {@code HashMapTest} * defines one simple test method and two bulk test methods. When * {@code makeSuite(HashMapTest.class).run} is executed, - * five simple test methods will be run, in this order:
+ * five simple test methods will be run, in this order:
* *
*
- * Note that if you want to use the bulk test methods, you must
+ * Note that if you want to use the bulk test methods, you must
* define your {@code suite()} method to use {@link #makeSuite}.
* The ordinary {@link TestSuite} constructor doesn't know how to
* interpret bulk test methods.
diff --git a/src/test/java/org/apache/commons/collections4/collection/AbstractCollectionTest.java b/src/test/java/org/apache/commons/collections4/collection/AbstractCollectionTest.java
index 0eaa37aae..31117ab06 100644
--- a/src/test/java/org/apache/commons/collections4/collection/AbstractCollectionTest.java
+++ b/src/test/java/org/apache/commons/collections4/collection/AbstractCollectionTest.java
@@ -314,11 +314,11 @@ public abstract class AbstractCollectionTest
+ * returned array must be an element in a full collection.
* The default implementation returns a heterogeneous array of
* objects with some duplicates. null is added if allowed.
* Override if you require specific testing elements. Note that if you
- * override {@link #makeFullCollection()}, you must override
+ * override {@link #makeFullCollection()}, you must override
* this method to reflect the contents of a full collection.
*/
@SuppressWarnings("unchecked")
@@ -389,7 +389,7 @@ public abstract class AbstractCollectionTest
* For tests on modification operations (puts and removes), fixtures are used to verify that that operation results in correct state for the map and its
* collection views. Basically, the modification is performed against your map implementation, and an identical modification is performed against a
- * confirmed map implementation. A confirmed map implementation is something like
*
- * The upshot of all that is that any test that modifies the map in any way will verify that all of the map's state is still correct,
+ * The upshot of all that is that any test that modifies the map in any way will verify that all of the map's state is still correct,
* including the state of its collection views. So for instance if a key is removed by the map's key set's iterator, then the entry set is checked to make sure
* the key/value pair no longer appears.
*
@@ -1845,7 +1845,7 @@ public abstract class AbstractMapTestjava.util.HashMap
, which is known to conform exactly to
+ * confirmed map implementation. A confirmed map implementation is something like java.util.HashMap
, which is known to conform exactly to
* the {@link Map} contract. After the modification takes place on both your map implementation and the confirmed map implementation, the two maps are compared
* to see if their state is identical. The comparison also compares the collection views to make sure they're still the same.
* equals
test is done on the maps and their collection views; their
* size and isEmpty
results are compared; their hashCodes are compared; and containsAll
tests are run on the collection views.
*/