[Collections] Bring Abstract* tests into it's own test jar

[Rohan Suri <ro...@gmail.com>]

Hi,

The Abstract* tests for collections seem pretty useful to be in a separate
jar so that they could be reused by anyone wanting to test a new map
implementation.
If the idea seems fine, I'd be happy to take up the task and discuss the
required changes in pom, etc.

Rohan.

Re: [Collections] Bring Abstract* tests into it's own test jar

[Claude Warren <cl...@xenei.com>]

If you are looking for tests for interfaces take a look at contract testing
(https://github.com/Claudenw/junit-contracts)



On Fri, Sep 20, 2019 at 9:40 AM Rohan Suri <ro...@gmail.com> wrote:

> Apologies I wasn't aware the test jars are being released as well.
> Adding "classifier: tests" when specifying the dependency does the job.
>
>
> On Fri, Sep 20, 2019 at 1:05 AM Rohan Suri <ro...@gmail.com> wrote:
>
> > Hi,
> >
> > The Abstract* tests for collections seem pretty useful to be in a
> separate
> > jar so that they could be reused by anyone wanting to test a new map
> > implementation.
> > If the idea seems fine, I'd be happy to take up the task and discuss the
> > required changes in pom, etc.
> >
> > Rohan.
> >
>


-- 
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren

Re: [Collections] Bring Abstract* tests into it's own test jar

[Rohan Suri <ro...@gmail.com>]

Apologies I wasn't aware the test jars are being released as well.
Adding "classifier: tests" when specifying the dependency does the job.


On Fri, Sep 20, 2019 at 1:05 AM Rohan Suri <ro...@gmail.com> wrote:

> Hi,
>
> The Abstract* tests for collections seem pretty useful to be in a separate
> jar so that they could be reused by anyone wanting to test a new map
> implementation.
> If the idea seems fine, I'd be happy to take up the task and discuss the
> required changes in pom, etc.
>
> Rohan.
>