Thoughts on client storage testing

[Cantor, Scott]

On 9/9/15, 12:35 PM, "dev on behalf of Tom Zeller" <dev-bounces at shibboleth.net on behalf of tzeller at dragonacea.biz> wrote:

>The idea is to run the existing tests with (a) local storage toggled on|off on the server and (b) local storage toggled on|off on the client. I don’t think the term “decision table” is correct, but I am thinking that (a) + (b) result in running 4 tests.

Yes, I think that's the ideal if we can do it. Obviously three of them end up with the same storage outcome.

>The ServerData object would, I guess, have a single field : idp.home.  Test methods would look like :

Or possibly a specific set of overridden properties? But I guess in theory we might need to specialize more of the configuration.

>If the DataProvider route is not the right one, another option is to use Java inheritance as the implementation of the “configuration dimension” of the IdP.

That probably would be too limiting, and Java doesn't handle mixins very well.

I'm not familiar with the DataProvider feature, so I don't have much of an opinion, but it sounds fine.

-- Scott