| <!-- |
| Licensed to the Apache Software Foundation (ASF) under one or more |
| contributor license agreements. See the NOTICE file distributed with |
| this work for additional information regarding copyright ownership. |
| The ASF licenses this file to You under the Apache License, Version 2.0 |
| (the "License"); you may not use this file except in compliance with |
| the License. You may obtain a copy of the License at |
| |
| http://www.apache.org/licenses/LICENSE-2.0 |
| |
| Unless required by applicable law or agreed to in writing, software |
| distributed under the License is distributed on an "AS IS" BASIS, |
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| See the License for the specific language governing permissions and |
| limitations under the License. |
| --> |
| <body> |
| <p>The Collections Test Framework is an extension to JUnit to enable quick and easy testing |
| of collections.</p> |
| |
| <h3>Apache Commons Collections Test Framework</h3> |
| |
| <p> |
| The Collections Test Framework is an extension to JUnit to enable quick and easy testing |
| of collections. The collections interfaces are large and complex to test thoroughly. |
| These classes do most of the testing for you, and offer configuration by overriding methods |
| when your collection bends the API. All you have to do is actually write the collection |
| and make it pass. |
| |
| <p> |
| The test framework does not depend on the main commons-collections jar file. |
| The only exception to this are the <code>Bag</code> tests, but if you are testing this |
| you must have the collections jar anyway. |
| |
| <p> |
| NOTE: The test framework is released to aid developers. |
| We will try to make changes backwards compatible. |
| However, if necessary changes will be made to the test framework to improve the tests. |
| |
| </body> |
