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

Suggestion for structure of TestTWF events

From: Daniel Davis <ddavis@w3.org>
Date: Fri, 18 Apr 2014 15:52:22 +0900
Message-ID: <5350CBA6.2080606@w3.org>
To: public-testtwf-planning@w3.org
Hi all,

As a helper at TestTWF events, a lot of time is spent repeating what
speakers have talked about because participants have forgotten. Some of
this seems to be because there are many talks back-to-back.

The current TestTWF structure is mostly:
1. Introductory talks and howtos
2. Participant preparation
3. Test writing

During the talks, participants hear a lot of info that they try to
retain. By the time they're ready to start, perhaps the next morning,
they've forgotten a lot of it. It then takes considerable individual
hand-holding to get everyone ready to code.

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

Just a thought...

Daniel Davis
Received on Friday, 18 April 2014 06:53:35 UTC

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