1
0

Standardize on American English spelling of 'behavior'.

This commit is contained in:
Gary Gregory
2020-03-30 15:07:28 -04:00
parent 9f99a007cf
commit 7c70d1a180
12 changed files with 27 additions and 27 deletions

View File

@@ -21,7 +21,7 @@ import junit.framework.TestCase;
import java.util.Hashtable;
/**
* Tests behaviour when the property is misconfigured.
* Tests behavior when the property is misconfigured.
*/
public class BadHashtablePropertyTestCase extends TestCase {

View File

@@ -94,7 +94,7 @@ import junit.framework.TestSuite;
* settings.
* <p>
* The effect of using this approach in a system that uses junit's
* "reloading classloader" behaviour is unknown. This junit feature is
* "reloading classloader" behavior is unknown. This junit feature is
* intended for junit GUI apps where a test may be run multiple times
* within the same JVM - and in particular, when the .class file may
* be modified between runs of the test. How junit achieves this is

View File

@@ -256,7 +256,7 @@ public class ChildFirstTestCase extends TestCase {
// ClassLoader.getResources is final it isn't possible for PathableClassLoader
// to override this. So even when child-first is enabled the resource order
// is still (parent-resources, child-resources). This test verifies the expected
// behaviour - even though it's not the desired behaviour.
// behavior - even though it's not the desired behavior.
resources = childLoader.getResources("org/apache/commons/logging/impl/Log4JLogger.class");
urls = toURLArray(resources);

View File

@@ -35,7 +35,7 @@ import org.apache.commons.logging.PathableTestSuite;
/**
* Tests for logging with a security policy that allows JCL access to everything.
* <p>
* This class has only one unit test, as we are (in part) checking behaviour in
* This class has only one unit test, as we are (in part) checking behavior in
* the static block of the LogFactory class. As that class cannot be unloaded after
* being loaded into a classloader, the only workaround is to use the
* PathableClassLoader approach to ensure each test is run in its own

View File

@@ -38,7 +38,7 @@ import org.apache.commons.logging.PathableTestSuite;
* messages on failure requires certain security permissions. If the security manager
* blocks these, then the test can fail without the error messages being output.
* <p>
* This class has only one unit test, as we are (in part) checking behaviour in
* This class has only one unit test, as we are (in part) checking behavior in
* the static block of the LogFactory class. As that class cannot be unloaded after
* being loaded into a classloader, the only workaround is to use the
* PathableClassLoader approach to ensure each test is run in its own