Keywords: {0}
there are some key aspects of the bug report that make it very helpful for contributors, not only testers, who should be able to reproduce the issue to validate and make sure that this isn’t something that’s unique, unique to a plugin, to a custom theme or snippet that you dropped into your functions PHP.
But, also for the actual Core contributors, who then need to be able to understand what is happening so that they can fix the right thing. And some of those items are the information about your testing environment.
[Brian Alexander 00:11:34]
So that could be your browser, your server, the type, whether it’s Apache, Nginx, et cetera, the operating system you’re running, what version of PHP you’re running, the version of WordPress, very critical, and…
[Josepha Haden Chomphosy 00:11:49]
Super important.
[Brian Alexander 00:11:51]
Any themes and plugins that you’re using. And that kind of information helps set the stage, and then other people will be able to set up their environment similarly if they’re going to try to test it.
After you have provided the environmental information, the steps required to reproduce the issue should be as detailed as possible. You may not have realized that clicking this caused such and such to happen, so just try to remember, or maybe even walk through if it’s something you can repeat multiple times, walk through a couple of times and write down everything that you’re doing.
[Brian Alexander 00:12:30]
So that you’re sure, hey, this is the way that I can reproduce this bug. And then those steps will be very helpful for other contributors when they’re reviewing it. And then it’s also very helpful if you have video, screenshots, debug logs, any of those other kinds of resources that you could refer to because not all bugs are easy to explain.
https://wordpress.org/news/2022/10/episode-40-all-things-testing-with-special-guests-anne-mccarthy-and-brian-alexander
Top Design 