By highermath on

Code freeze begins September 1st. During this period, we fix bugs and when Drupal 7 is stable, we release. In the past, we have done manual testing. This time we have an automated testing framework and already a large number of tests. In an ideal world, we would only release when all code is touched by tests. While this won't guarantee that Drupal will be bug free, every test contributes to the overall quality of Drupal.

Two weeks before the code freeze, we will gather in Los Angeles to write tests. This will take us into the darker corners of core, so we also get the chance to fix bugs and, because this precedes the code freeze, we have greater freedom in how to fix them.

Since this sprint is so close to the code freeze, it's an excellent time to raise the test coverage ratio as there will be little new development in the final two weeks.

Please join us! Go to the sprint sign-up page at http://groups.drupal.org/node/22652

Food, beverages, power, IP and chocolate will be provided by our sponsors, Causecast and the The Cherry Hill Company.

Organizers:

⋅ Categories: Drupal 7.x

Comments

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

Looking forward to seeing the results! :D

boombatower’s picture

boombatower commented

Looking forward to taking part.

senpai’s picture

senpai commented

I claim the first hotline IRC pipe to boombatower during the sprint!

$first;

****
Joel "Senpai" Farris | certified to rock score

zhangx1a0’s picture

zhangx1a0 commented

Great News!

can't wait to use D7

peterx’s picture

peterx commented

Los Angeles is a bit far for me to drive for that event and the Pacific a touch too deep for my car but I would like to contribute to the range of testing ideas. Does the testing involve different entry points. I am thinking of logging in when my new theme is broken. example.com/user uses the site theme instead of the admin theme and the site theme might be broken. Cases like that are important. Can they be programmed in to the testing?

Recovering from a newly installed module breaking the system is another problem. Can you test an emergency uninstall process for module updates and add on modules that block normal access?

Using the backup module then successfully restoring is another situation worth testing. Backup d7.x then apply d7.x+1 update with a deliberate error then restore to d7.x and compare the restored d7.x to the original d7.x.

petermoulding.com/web_architect

priyanka raichand’s picture

priyanka raichand commented

how to give web address or url to website?? I have made a drupal based website and access it through http://lopcalhost/drupal. want to give address to website so that others can also access that. please please help help.....

Forage’s picture

Forage commented

This is totally not the page, nor the website to ask such questions. You basically have two options: 1) host it from you own PC or 2) find yourself a hosting provider to host it for you. Make Google (or whatever search engine you prefer) your best friend by looking for 'How to host a website' (http://www.google.com/search?q=how+to+host+a+website) and you'll get the answers to how to do one of both.

Anodonta’s picture

Anodonta commented

This is good news :)

glen201’s picture

glen201 commented

IMHO PLEASE dedicate a handful of code sprinters to documentation. There are too many people left in 5.x currently because of a lack of documentation on how to get to 6.x. Witness the lack of Views 1 to Views 2 documentation for developers, when it should be simple for "those in the know" to put down their IDEs and just write a little doc for the rest of us.

Thanks for listening,
--glen