Test Scrub for WordPress 5.7 and office hours

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

As part of the 5.7 release, we’ll be hosting a focused test scrub for the below-listed tickets, Tomorrow, Friday 29/01/2021 13:30 UTC in the #core channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

https://core.trac.wordpress.org/ticket/51812
https://core.trac.wordpress.org/ticket/51941
https://core.trac.wordpress.org/ticket/52355
https://core.trac.wordpress.org/ticket/48562
https://core.trac.wordpress.org/ticket/47912

The ticketticket Created for both bug reports and feature development on the bug tracker. is ready to be considered for commit but needs testing/QA.

To set up the Testing Environment follow the steps listed here – https://meta.trac.wordpress.org/ticket/5581#comment:3

How to apply 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.

TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket, for example 35449

npm run grunt patch:35449

How to fetch and then checkout a PR, for example, PR 828

git fetch upstream pull/828/head:pr-828
git checkout pr-828

or for PR:

npm run patch https://github.com/WordPress/wordpress-develop/pull/828

Check the handbook for more ways to test patches.

Do you have a ticket you want to bring up for testing?

Fantastic!

In order to allow testers to manually test the patch, you should include the following information:

What are the steps to reproduce the problem?
What are the steps to test?
Are there any testing dependencies such as a pluginPlugin 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?

#5-7, #test, #testing

Peter Wilson 3:38 am on January 29, 2021
It would be helpful if the latest 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. for #5272 could be tested.

To recreate the bugbug 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. in 5.6:
- Create a private post
- Determine the post ID from the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org of the edit screen in the dashboard (post=47 will be in the URL for post number 47).
- Visit http://localhost:8889/?p=47 while logged out, you will redirected to the proper page (http://localhost:8889/2021/01/my-private-post) and get a file not found error
After applying the patch visiting the URL while logged out should not redirect.

Items to check:
- Ensure that child pages in a hierarchy still have valid URLs/don’t result in a file not found error
- Ensure that the attachment page links still work from a public and private post/page (see the steps detailed in #51776 which prompted a revert of #5272 prevously)
- Ensure attachments uploaded to a private post/page are also private, they should not redirect by attachment ID either. http://localhost:8889/?attachment_id=48 (for attachment number 48 that is 😉
Thanks folks.

Comments are closed.

Welcome!

Communication

How to apply 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.

Do you have a ticket you want to bring up for testing?

Share this: