Thoughts on client storage testing

[Brent Putman]

On 9/25/15 3:26 PM, Tom Zeller wrote:
>> DataProvider ... I've also used it in some Selenium integration and load-testing use cases for our GU LMS, to pass in some of the same data as you are, like browser/version/OS, as well as test different users authenticated with different credentials.
> Just curious, what did you name that data ? and/or how did you orchestrate the Object[][]s returned by the DataProvider ?

This was a short notice, under-the-gun project so I didn't spend any
time thinking about elegance.  I didn't create any classes/structs to
hold the data, each bit was just stuffed straight into each Object[].

Because I was loading user data from files, I did use the variant where
the @DataProvider returns an Iterator<Object[]>, rather than an
Object[][].  Like:
       
    List<Object[]> data = new ArrayList<>();
       
    for (UserData user : userData) {
        data.add( new Object[] { browser, version, Platform.ANY,
user.getUsername(), user.getPassword() } );
    }

and then the data provider method itself just returns data.iterator().


> I’m going with Object[ServerConfig][BrowserConfig].
>
> For future reasons, I’m wondering if ServerConfig and BrowserConfig should extend BaseContext.

I don't know what all you are, or will be, doing with this, but that
sounds pretty involved to me.  Unless you have this scattered all over
lots of classes, you can always just change it later. It is tests,
after all.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20150925/83be104f/attachment.html>