Voting starts in March for the Drupal Association Board election.
Last updated June 28, 2016.
On this page:
- Skills needed
- Detailed steps
- Background and reference information
- Next steps: moving beyond this task
- Notes for reviewers
To get help completing this task, see the Getting help completing your task page.
Manually test a patch (software fix) for a reported Drupal issue to verify that it resolves the issue and does not cause other regressions (new bugs).
Some familiarity with the module, theme, or task is helpful, but not required. You will also need to apply a patch to a test site.
- Install Git on your computer, if it is not already installed. See the installing git page for more information.
- Install Composer on your computer, if it is not already installed. See the Composer installation instructions for more information.
- If you don't have a Drupal site to test on, set up a local server. You probably do not want to use a live, production web site for this task.
- Install Drupal from Git on this local server. You will probably need to install the latest, in-development version of Drupal, as most testing and patching is done against that version (rather than the released version). For instructions on how to download Drupal from Git, see Drupal core version control instructions
- Install dependencies if you're working Drupal 8.1.x or higher you will need to run
composer installin the Drupal root to install all dependencies.
- Find issues for a Drupal project (search core link).
- Choose an issue marked "Needs review." For Drupal core, use the advanced search to find an issue marked "Needs Review" and tagged with the "Needs manual testing" tag.
- Make sure you can reproduce the issue on your test site. (If the steps to reproduce the issue are unclear, you can document them or add a comment asking for clarification. If you cannot figure out how to reproduce the issue, choose a different issue.)
- For Drupal core, some frontend issues should also be tested in all core themes, including Bartik, Seven, Stark, and (for Drupal 7) Garland.
- Your task is now to test the most recent patch and verify that it resolves the issue and does not cause any new bugs.
- Apply the patch to your local Drupal installation and clear the site cache. See the Background section below to find information about how to apply a patch.
- Follow the steps to reproduce the issue with the patch applied. Confirm whether the issue is resolved by the patch.
- If it is a frontend change, take a screenshot of the result with the patch applied.
- If you are testing multiple browsers, note the result in each.
- Add a comment to the issue documenting the results of your testing.
- Identify which browser(s) and theme(s) you used in your testing.
- Explain the result in some detail (not just "the patch worked" or "the patch didn't work").
- If you took screenshots, upload them as attachments to your comment, and embed them in the comment using an
- If the patch does not fix the issue, or if it caused new bugs, set the issue status to "Needs work."
- If the patch does resolve the issue and (if appropriate) has been tested in all supported browsers and/or all core themes, remove the "Needs manual testing" tag if it is present.
Background and reference information
- Git handbook (Git is the version control system that the Drupal project uses)
- Drupal core version control instructions
- List of supported browsers
- Contributor task: add screenshots has guidelines for good screenshots.
Next steps: moving beyond this task
- Manually test more issues in the same project or a different project, following the same steps as above.
- Review the patch code.
Notes for reviewers
Specific to this task:
- Reproduce the issue before applying the patch.
- Test after applying the patch to verify the fix.
- Document the exact steps used to test the patch (a numbered list).
- Indicate which browser/version and theme were used for testing.
- Attach screenshots to the comment (cropped to only the relevant portion of the screen and embedded with an <code></code> tag).