java-idp-integration-tests and idp-flow-tests ?

[Tom Zeller]

>>After botching the commit of the Selenium status servlet test last
>>Friday, I realized it is not a good idea to mix integration tests with
>>unit tests, especially with Selenium's dependency on Xalan/Xerces.
>
> They really are off base with
> that code, they shouldn't be depending on any classes specific to Xerces.
> Even we never did that.

Hmm, maybe I'm wrong. Nonetheless, a separate project for integration
tests seems the right thing to do.

>>I also would like to pull the flow tests out of the testbed
>>eventually, and I suggest a new idp module 'idp-flow-tests'.
>
> I'm torn just because it seems odd to have tests as a separate module in
> the main project, but maybe that doesn't matter.
>
> Or maybe we could make them tests of idp-conf? I often find myself
> flipping back and forth and accidentally running idp-conf by mistake
> because I'm usually testing changes in that module.

Flow unit tests in idp-conf was my second but near-first choice, only
because I wanted to keep idp-conf "clean", but I do not think that
matters much. Of course, we can start there and move to a separate
module if it gets messy for some reason.