W3C home > Mailing lists > Public > public-testtwf-planning@w3.org > April 2014

Re: Suggestion for structure of TestTWF events

From: Robin Berjon <robin@berjon.com>
Date: Fri, 18 Apr 2014 09:53:03 +0200
Message-ID: <5350D9DF.9080801@berjon.com>
To: Daniel Davis <ddavis@w3.org>, public-testtwf-planning@w3.org
Hi Daniel,

On 18/04/2014 08:52 , Daniel Davis wrote:
> What about a format that covers the same content and preparation but in
> smaller chunks? E.g.:
> 1. Git basics
> 2. Help participants setup git
> 3. Repository basics
> 4. Help participants setup testing repository (including python, whatever)
> 5. Test basics
> 6. Help participants run existing tests
> 7. Test writing

I think that's a great suggestion, though I'd do it slightly 
differently. How about:

1. Step by step full setup
    This takes people through all the steps needed to get up and 
running, with experts walking around the room helping. Doing it first 
ensures people are listening. Once that's done everyone is ready to work.
2. Run a few tests to check all is good
3. Test basics
4. Test writing

The first step might feel like a waste of time, but I think we might 
gain a lot of time afterwards.

-- 
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Friday, 18 April 2014 07:53:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:37:04 UTC