Hi,
I just tried to use the AbstractTestList and found that testListAddByIndex adds
one more element than getFullElements().length. Is this behaviour intended?
It could be a problem for fixed sized lists.
Another problem I saw is that the documentation of List in the JDK 1.4.2 states
that a
We use AbstractTestList to test our own FixedSizeList. Simply override
isAddSupported() to return false in order to block the test.
Stephen
- Original Message -
From: Joerg Schmuecker [EMAIL PROTECTED]
I just tried to use the AbstractTestList and found that testListAddByIndex
adds
one
On Thu, 2003-10-02 at 02:12, Henri Yandell wrote:
I'm a bit confused with Collections atm.
'ant test' calls src/test/org/apache/commons/collections/TestAll.java.
However this does not list tests in sub-packages that I can see [though I
imagine things like the iterators package could be
On Thu, 2003-10-02 at 16:42, Henri Yandell wrote:
On 2 Oct 2003, Janek Bogucki wrote:
On Thu, 2003-10-02 at 02:12, Henri Yandell wrote:
I'm a bit confused with Collections atm.
'ant test' calls src/test/org/apache/commons/collections/TestAll.java.
However this does not list
On 2 Oct 2003, Janek Bogucki wrote:
On Thu, 2003-10-02 at 16:42, Henri Yandell wrote:
Why should both not do the same?
When I type 'ant test' and 'maven test', they should be equivalent. Unless
we decide to drop ant or maven support.
The outcome of my suggested changes was meant
I'm a bit confused with Collections atm.
'ant test' calls src/test/org/apache/commons/collections/TestAll.java.
However this does not list tests in sub-packages that I can see [though I
imagine things like the iterators package could be tested through
TestIteratorUtils.
Anyone know what the
Okay, this is a cumulative patch; it includes the previous two.
The point of this patch is that TestMap is now hardcore. It
fully tests its collection views, by running through the tests
defined in TestSet and TestCollection on keySet(), entrySet()
and values().
It also fully tests that
