Call for testing

When a feature is ready for a beta audience, post a call for testing to make/core. Use this handy template and checklist when creating your post. Or, skip all of this. Publishing anything and tagging it #needs-testing is sufficient and better than not posting.

Template Template

What is it? What is it?

Describe the feature. Include screenshots. Describe any goals and gating criteria, such as parity requirements.

Top ↑

Where is it? Where is it?

Describe how to get to the feature. Direct links are good.

Top ↑

What to test What to test

Describe the primary flows to test. Consider using bulleted flow or a visual record.

Top ↑

What to expect What to expect

List known issues and shortcomings (bug tracker links are helpful). Set expectations.

Top ↑

How to report How to report

Provide trac or github links, include the component.

Top ↑

Timeline for testing Timeline for testing

Express urgency and priority. If there are target dates, provide them.

Top ↑

Checklist Checklist

  • Introduce yourself
  • Explain the feature or update
  • Link to the feature
  • List known issues
  • Provide a short list of testing steps
  • Mention how to provide feedback
  • Include a date for the completion of the testing
  • Include screenshots from multiple devices
  • Keep a beta testing audience in mind
  • Tag the post #needs-testing