Great news! The Awesome Testing Party session was accepted at Drupalcon Szeged! Woohoo!! It'll be at 9am on August 28th, but people should probably be there a bit earlier, like 8:30am.
There's lots to prepare, and very little time to do it in! We had a discussion today in #drupal to talk over logistics. Here's where we stand. Please strike things as you get them done. Thanks!
Stuff for lead-up to the event
- Write a testing hand-out that summarizes stuff from the intro to testing session (flobruit)
Do a PR blitz to Drupal Planet about the party, talk about its benefits and goals, how it's going to work, and ask Szeged attendees to bring a box of chocolate with them(webchick) - http://webchick.net/awesome-testing-partyRe-run test coverage scripts to see where we stand(catch) - http://coverage.ca.tchpole.net/coverage/html/1- Do a screencast about how to write tests (sdboyer)
- Create a .test template that people can copy/paste from (webchick)
- Create issues for each candidate test and title them TestingParty08: Description of test" (boombatower and catch) - list here
- Write up a hand-out describing how testing party will work for participants (webchick)
Stuff for the day of the event
- Look into getting Hungarian pancakes for breakfast ;) (chx)
- Make lots of photocopies of the testing handout to bring with (webchick)
Go buy some index cards and write all the TestingParty08 issue Node IDs on them(webchick) - they're even multicoloured!- Bring chocolate for the big "chocolate stash" at the front of the room (everyone!)
Agenda/workflow
- Pancake bar as people come in
- 5-10 demonstration on how to do testing
- Pair up testing veterans with testing newbies
- Do test cases for the rest of the time:
- Get pancakes
- Get a testing issue
- Solve and eat testing issue and pancakes, respectively.
- Submit patch for review.
- Claim a new task/pancake if you have no tasks at cnw, otherwise tidy up those issues.
- Repeat.
- Chocolate fits in here somewhere too.
"Volunteers"
- cwgordon7
- webchick
- sdboyer
- chx
- boombatower
- catch
- flobruit
- damz
If you see anything missing from this list, or would like to volunteer to help with any of these items, feel free to edit away. :)
Post-event
To make it easier to Dries to commit the tests and to ensure the quality of the tests the patches should be reviewed by those involved in testing development.
- Aggregate testing party patches into bulk patches related to each file/module they test instead of small tasks. (Without "TestingParty08" prefix)
- Review the tests while aggregating and ensure that they all at least pass.
- Create issues for the bulk patches or fill in existing ones.