Re: WebDriver Test Suite

Hi all,

I'm new to the correspondence here and don't really know what's at stake. Are these tests browser-specific? (I.e., tests of an implementation of the spec in a certain browser) Or are they somehow more general tests of the algorithms defined in the spec, in a browser-agnostic fashion? I did a bit of digging but couldn't find an existing suite to look at---presumably that's why you're all discussing how to get started!

I'm happy to jump in and help with some test-writing if it's feasible. Or if Sauce Labs's webdriver cloud infrastructure can be of use, I can see what I can do about that as well.

--
Jonathan Lipps
Director of Open Source
Twitter: @jlipps <http://twitter.com/jlipps> 
GitHub: @jlipps <https://github.com/jlipps>
Sauce Labs <http://saucelabs.com/> | Sauce blog <http://sauceio.com/>

> On Mar 30, 2017, at 9:29 AM, Andreas Tolfsen <ato@mozilla.com> wrote:
> 
> Also sprach Simon Stewart <simon.m.stewart@gmail.com>:
> 
>> 4/ (Most importantly): who has tests to commit or areas that
>> they're interested in working on?
> 
> In the short-term I am ready to commit to writing tests for the Get
> Title command, as I recently happened to extend Marionette’s test
> suite for this.
> 
> It’s a very small contribution, but gets the ball rolling.
> 
>