Re: Choosing a CR end date

I'm busy porting the "Element Get Text" tests from JS and Java to the test
suite. I agree that we're running a little close to the deadline with
these, but I also agree with David that we can get there.

I'll update the README.md to include a link to our coordinating spreadsheet
so that we don't trample each other :)

Simon

On Mon, Jul 31, 2017 at 9:27 PM, Jonathan Lipps <jlipps@saucelabs.com>
wrote:

> I also hope to contribute a section or two towards the end of August once
> I'm back from holiday.
>
> On Mon, Jul 31, 2017 at 8:03 AM, David Burns <dburns@mozilla.com> wrote:
>
>> I have been writing tests for a number of areas so that we can get a
>> decent test suite going. I have 3 sections worth of tests locally. I think
>> we can easily get the tests into place if people spend a couple hours a
>> week doing this.
>>
>> David
>>
>> On 26 July 2017 at 17:59, James Graham <james@hoppipolla.co.uk> wrote:
>>
>>> On 02/04/17 15:12, Simon Stewart wrote:
>>>
>>>> We've been rechartered until the end of September. 31st August gives us
>>>> 30
>>>> days for the review. Does that sound reasonable? I'd like to leave as
>>>> much
>>>> time for the conformance suite to be finished as possible.
>>>>
>>>
>>> 31st August is now 5 weeks away. Do we have any sense of our progress
>>> here? My feeling is:
>>>
>>> * We can probably resolve all spec issues if there is a person month or
>>> two of dedicated work on those issues.
>>>
>>> * I feel like we are a long way off with the testsuite, still. Many
>>> sections have no tests, and the tests that we do have are generally not
>>> covering all the corner cases. It's hard for me to tell if people aren't
>>> working on spec compliance, or aren't producing tests as part of that work.
>>>
>>> I know that there is interest in adding additional functionality to
>>> WebDriver, but I'm unclear what will happen to the group if we are unable
>>> to meet this extended deadline.
>>>
>>>
>>
>