Last updated April 16, 2011.

Help us test patches for core! There are many important core initiatives going on that need to be reviewed and tested. You can help with this important task even if you don't know how to code.

How do I start?

Your first order of business is to get a development environment up and running. Next, you should read the instructions on how to test out patches and how to review them. Also, see the resources section at the bottom of this page.

Where do I jump in?

Please see Drupal core community initiatives for a list of current efforts going on and places to jump in, including various Internationalization improvements and more.

What do I do if I find a bug while testing a patch?

Try to reproduce the bug on a 'clean' copy of Drupal HEAD. For patches without database changes, you can "reverse" apply a patch to remove it:

patch -p1 -R < patchfile.patch

For patches that make changes to the database, you'll need a clean checkout elsewhere to compare against.

Check to see if the bug manifests itself without the patch. And note: don't forget to re-apply afterwards:

patch -p1 < patchfile.patch

If not, it's usually safe to assume it's caused by the current patch. Mark the issue "code needs work" and describe in detail what you experienced and how the developer can re-produce the steps.

If so, then there is a deeper problem with core... see if someone has already reported a bug on it by searching the issue queue. If not, feel free to file a bug.


Here is a list of general resources for applying and testing patches.