Kieran's trying to put together a testing sprint this spring. We should come up with an agenda of what we're going to need to cover:
Goals and Deadlines
The Drupal 7 development life cycle may be extended for as long at 4 months from June, to October, 2008. This is possible if Drupal 7 has solid test coverage including functional, unit, and JavaScript testing.
- Figure out core's test coverage using various tools: March 17, 2008 (Djun and Doug Green)
- Update the list of modules + test coverage: March 21, 2008 (boombatower)
- Figure out and document test naming/coding conventions + get them in Coder module so they're flagged. March 28, 2008 (boombatower, Doug Green?)
- Choose a unit testing framework(s) for Drupal core: March 21, 2008 (DriesB)
- Dojo session on SimpleTest and how to write tests, etc.: March 23, 2008 (cwgordon7)
- Update/Write SimpleTest API documentation: March 28, 2008 (defer to Amazon)
- Continuous unit testing framework for core: April 1, 2008 (Kevin Bridges)
- Full-on community push for unit tests. Let's make our testing push here.: April 1, 2008 (webchick)
- Testing sprint to get testing into HEAD: April 19, 2008
- Drupal 7 core must be 100% unit test covered by May 15, 2008 (All of us :))
Attendees
- Jimmy Berry
- Kevin Bridges
- Charlie Gordon
- Douglas Huber
- Karoly Negyesi
- Rok Zlender
- Miglius Alaburda
Travel details: Flight arrival and hotel arrangements
Jimmy: Arrive Friday 2:55 pm (local) staying at Hotel Acadia Opera, and will leave 12:50 pm (local) on Monday.
Charlie: Arrives Thursday morning, ~7-8 AM. Will likely be zonked at that time, though, as it will feel ~midnight. Staying with grandparents.
Douglas: Arrive Fri 825 AM. staying at Hotel Cyrnos, leave Monday 1:40PM
Dries:
Rok: Arrive Friday 9pm CDG staying at Hotel Acadia Opera, leave Monday 9.20pm CDG
Karoly: Arrive Friday 9pm CDG staying at Hotel Acadia Opera, leave Monday 8:20pm CDG
Kevin: Arrive Friday 11:05 AM CDG. staying at Hotel Cyrnos, leave Monday 12:55 PM CDG
Miglius: Arrive Friday 18:55 CDG. staying at Hotel Cyrnos, leave Monday 23:35 CDG
Fundraising & Event coordination
- suggested location: co-locate with DrupalCamp Paris, April 19th
- Sponsors include: Acquia, Google, McDean's OpenBand division, pingVision, NowPublic
- Ori is on the ground in Paris
Background info
- We need three forms of testing:
- Browser-based testing
- JavaScript testing
- Unit testing
- Tools to determine what 100% coverage is
- PHPCoverage
- XDebug
- Build into Coder module?
- Stats from Djun and Doug, who are working on figuring out what other open source projects are using for test coverage calculation
- Pick a unit testing framework for Drupal: Lime, Watir, PHPUnit...? -- i thought simpletest can do unit tests too. -chx
- Written tutorials
- Dojo session by Charlie Gordon on SimpleTest.
- API documentation for Simpletest
Logistics
- Kieran will be contributing by helping to ensure this is an effective event and an important part of ensuring testing is part of D7. Kieran and Djun will also help to raise funds to get the participants travel and accommodations covered.
Problems to cover
My [chx] biggest concerns currently are logistics so to say. We need to gather a hell lot of code quick from a lot of people and put them to the right place. The mechanics of this needs discussion.
Questions to cover for the simpletest sprint
Note: Please add stuff here!
- What will the sprinters accomplish in Paris?
-
We have a list of tests that need to be written! However, our priority will not be on actually writing the tests, but rather giving those there the ability to continue writing the tests after the sprint. In the process, though, it would be nice to see about half our list of tests completed.
- Why do they need to be together for three days in Paris?
-
We need to teach them how to write SimpleTests! SimpleTest is no piece of cake, especially if you have no prior experience with OOP in PHP. This will be a constructive learning environment from which people will emerge confident that they can write SimpleTests for Drupal.
- What is being done in advance to ensure this is an effective event?
-
We are compiling a list of tests that need to be written. We are documenting the SimpleTest API so that we will have an easy reference. In essence, we're finding things that need to be done, and making it easy to do them. :)