Last updated by finn lewis on Thu, 2013-11-07 20:58
Wednesday 6th November 2013
These are rough notes from our meetup last night. Do feel free to edit or add to this if you were there.
Draft Agenda
- 19:00 - Introductions / news / announcements
- 19:30 - A tour of www.qualitywatch.org.uk (Johan Gant)
- 20:00 - Test Driven Development in Drupal: discuss.
- 20:30 - Q and A / share your issues
- 21:00 - Drinks and further Drupal chat at a local pub
Who’s here
- Finn Lewis (Agile Collective)
- Dave Balch(Oxford Uni?)
- J-P (Torchbox / Freelance)
- Tanc (Agile Collective)
- Steven Cox (Oxford Uni)
- Hubert Matthews (Independent systems architect and trainer)
- Steven Stose (Open University)
- Johan Gant (Torchbox)
- Mike (Timber Windows)
- Roger (Versantus)
- Nik Roberts (Versantus)
- Graeme Hunter (Nominet)
- Matt Trow (Nominet)
- Tim Huckvale (freelance / part time Drupalist)
- Jon Parsons (Global Canopy Programme)
- Iain Emsley (OeRC)
- Simon (Freelance designer and frontend developer)
News / notices
DrupalCamp Northwest. Be there!
http://camp2013.nwdrupal.org.uk/
For those that don’t know, DrupalCamps are a great place to meet other Drupal people, find out more about particular modules, processes, methodologies, and how to get more involved in the community whether by committing code, helping in the forums and issue queues or organising events.
http://www.qualitywatch.org.uk/
Johan Gant from Torchbox gave us a great tour of the recently launched http://www.qualitywatch.org.uk/
I didn’t make notes as he was using my computer, but highlights included:
- design in the browser
- a nicely responsive design (mobile first),
- use of high charts http://www.highcharts.com/ to embed charts into nodes,
- use of Display Suite’s block field to inject a social media sharing block into the content between fields
Question:
Does anyone use Test Driven Development while developing with Drupal?
The idea of TDD was defined as writing a number of test to define how the code should work, before developing any code. Then developing code to make the tests pass.
TDD: tends to refer to tests at the smaller level - unit tests - testing individual functions and classes..
ATDD: Acceptance test driven development - refers to testing the higher level acceptance tests as defined by the client or product owner.
BDD: Behaviour Driven Development : testing user behaviours. See Behat and https://drupal.org/project/drupalextension
Much discussion ensued, culminating the the consensus that to have thorough test coverage of all code and functionality, you really need unit tests and behavioural tests.
Question: What IDEs do people use?
A quick poll around the room revealed the following:
- Netbeans https://netbeans.org/
- Sublime Text
- Vim - see practical vim (book)
- Emacs
- Aptana http://www.aptana.com/
- PHP Storm
- Zend Studio
- Coda http://panic.com/coda/
Some interesting modules:
http://www.zivtech.com/blog/zivtech%E2%80%99s-13-obscure-drupal-modules
To the pub!