Write a Call for Testing

If you are working on a feature project or a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing., you may want to post a call for testing to see if you can find some volunteers who will test your work. When posting a call for testing, it’s good to:

  • Explain the feature or update briefly
  • Provide a short list of specific testing steps
  • List known issues (if any)
  • Mention how to provide feedback
  • Include a date for the completion of the testing

After testing has been completed, review and respond to feedback and makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). sure to thank people for testing. When replying to commenters, it’s best to be patient and say thank you without offering specific fixes or promising certain fixes right away. This will give you time to reflect on the feedback and weigh it properly.

Last updated: