On 08/03/2012 08:44 PM, Christopher Kula wrote:
> Yeah, this looks good. Especially the approach to asynchronous
> testing. Is there vendor buy-in to this testing framework?
>
> I'll take a swing at integrating this with the Node.js API mockup.
Also, here's more information on testharness.js (used by WebApps and
HTML WG):
http://w3c-test.org/resources/testharness.js
That file includes embedded documentation that should be very clear to
anybody who's accustomed to using JavaScript to automate test cases. The
sources are at http://dvcs.w3.org/hg/resources/
The work on WebDriver will supplement testharness.js for our purposes,
not to replace it. Specifics questions about testharness.js can be
answered in real-time on the #testing channel on irc.w3.org:6665. If
they prefer e-mail, the right list to take those kinds of questions to
is public-test-infra@w3.org.
So it seems that we should settle on testharness.js for test-cases if at
all possible.
hope this helps,
harry
>
> - Chris
>
> On Fri, Aug 3, 2012 at 1:05 AM, GALINDO Virginie
> <Virginie.GALINDO@gemalto.com <mailto:Virginie.GALINDO@gemalto.com>>
> wrote:
>
> Dear all, and people thinking about tests,
>
> Just had a quick chat with Robin Berjon, who strongly recommends
> any group uses testharness [1].
>
> If we want to make happy a TAG member, you know what we have to
> do. Just saying…
>
> Virginie
>
> Gemalto
>
> [1]
> http://darobin.github.com/test-harness-tutorial/docs/using-testharness.html
>
>
>
>
>
> --
> Christopher Kula
> cjkula@gmail.com <mailto:cjkula@gmail.com>
>