add testfw support for ConcurrentMap interface methods

[GoogleCodeExporter]

The test framework is thorough beyond belief for those interfaces that it
covers. Are there any plans for widening coverage to some of the more
specific collection framework interfaces? ConcurrentMap is the first that
springs to mind, NavigableMap, Deque, SortedSet and the like might be
useful too. Obviously, providing testing for the *concurrency* part of this
is a whole different ballgame, but it would be a great start to be able to
test at least the single-threaded behaviour.

More generally (perhaps this belongs in a separate issue), are there any
plans to make it easier to hook into the framework to test other types? As
a concrete example, I was playing with adding supplyIfAbsent(K,
Callable/Future<V>) to ConcurrentMap. To cleanly use the test framework
(after sorting out tests for the other four ConcurrentMap methods) it would
help to have some changes in, for example,
   * AbstractMapTester#getMap() to avoid the downcasts to my Map subtype
   * TestStringMapGenerator#create(Entry[]) for the same reason
   * MapTestSuiteBuilder#getTesters to make it easier to add testers to the
list, since Arrays#asList is inconveniently immutable.

Original issue reported on code.google.com by joe.kear...@gtempaccount.com on 14 Apr 2009 at 3:22

[GoogleCodeExporter]

Original comment by kevin...@gmail.com on 17 Sep 2009 at 5:57

• Added labels: Type-Enhancement

[GoogleCodeExporter]

Original comment by kevin...@gmail.com on 17 Sep 2009 at 6:02

• Added labels: Milestone-Post1.0

[GoogleCodeExporter]

This issue has been moved to the Guava project (keeping the same id number). 
Simply replace 'google-collections' with 'guava-libraries' in your address 
bar and it should take you there.

Original comment by kevinb@google.com on 5 Jan 2010 at 11:09

• Changed state: Moved