During the release cycle of WordPress 5.6, the focus lead, @monikarao, together with other people in the cohort, brainstormed ideas to encourage more testing.
One of the ideas is to add a template to Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. so that when a new ticket Created for both bug reports and feature development on the bug tracker. is created the reporter is prompted to add information about the testing steps, not only the bug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. or the enhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. proposed.
Right now tickets are opened without instruction on how and what to test. During triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions, scrubbers sometimes add the request manually, but the process could be automated.
Add a template
When reporters create new tickets they will be prompted to add these information:
- List the exact steps necessary to reproduce the problem.
- Specify the environment details where you reproduced the issue, e.g. WordPress version, PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher version, browser & version, operating system & version, plugins installed, and their versions.
- Paste any relevant error messages.
- Are there any workarounds for this issue?
- How can this issue be tested to ensure it’s fixed? Apply the patch 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.? Check the console? Check the front-end before and after? etc…
- Are there any testing dependencies, such as a plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party or script?
- What is the expected behavior after applying the patch?
Write a short page that explains every one of those prompts, with examples and explanations on why it is important to test. Add the link to new tickets.
Notify core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-test
If the tickets is high-priority, notify the #core-test channel in Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
What do you think?
I opened a ticket in Meta for this, and @dd32 encouraged me to discuss it here first, so here I am 🙂
Do you think having a template is useful? For every new ticket? What about stale tickets? Do you think notifying the core-test channel is necessary? What do you think should be the flow?