Title: testing – Make WordPress Core

---

#  Tag Archives: testing

 [  ](https://profiles.wordpress.org/adamsilverstein/) [Adam Silverstein](https://profiles.wordpress.org/adamsilverstein/)
2:35 pm _on_ February 2, 2023     
Tags: [core-performance ( 139 )](https://make.wordpress.org/core/tag/core-performance/),
[performance ( 404 )](https://make.wordpress.org/core/tag/performance/), testing

# 󠀁[Automated performance monitoring in WordPress core](https://make.wordpress.org/core/2023/02/02/automated-performance-monitoring-in-wordpress-core/)󠁿

Gathering performance metrics automatically is a way to track performance over time
and ensure that WordPress continues to improve.  Automated performance tooling will
also help the coreCore Core is the set of software required to run WordPress. The
Core Development Team builds WordPress. team identify issues and resolve them with
less effort.

## **Why add automated performance testing?**

Adding automated performance testing will help us monitor performance changes in
WordPress core continuously. It gives us a track record to capture how core performance
is being enhanced over time, and it allows us to catch regressions early and accurately
identify underlying causes. Similar to our unit testunit test Code written to test
a small piece of code or functionality within a larger application. Everything from
themes to WordPress core have a series of unit tests. Also see [regression](https://make.wordpress.org/core/tag/testing/?output_format=md#regression).
suite, automated performance testing would help protect core from introducing large
performance regressions by catching problems immediately and tracking performance
over time. Automating testing also means saving contributor effort by replacing 
a time consuming manual process.

The core performance team is focused on improving core performance. Examples of 
this work include introducing changes that reduce the number of database queries
or improve caching. Each new performance team feature must show **measurable** gains,
and each new WordPress release is performance tested by the team. In the 6.1 release
cycle, this led to the discovery of some significant performance regressions, e.
g. in [this Gutenberg issue](https://github.com/WordPress/gutenberg/issues/44772)
or [this Trac ticket](https://core.trac.wordpress.org/ticket/39210#comment:66). 
Automated testing would catch this type of regressionregression A software bug that
breaks or degrades something that previously worked. Regressions are often treated
as critical bugs or [blockers](https://make.wordpress.org/core/tag/testing/?output_format=md#blocker).
Recent regressions may be given higher priorities. A "3.6 regression" would be a
bug in 3.6 that worked as intended in 3.5. as soon as it was introduced, making 
it much easier to resolve.

It is worth noting that GutenbergGutenberg The Gutenberg project is the new Editor
Interface for WordPress. The editor improves the process and experience of creating
new content, making writing rich content much simpler. It uses ‘blocks’ to add richness
rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
has already done [extensive work on performance](https://make.wordpress.org/core/2021/03/23/core-editor-improvement-performance-matters/),
tracking metrics with each commit and publicizing details with each release.  

## **What automated performance testing would do in core**

Similar to Gutenberg, WordPress core would gather a set of automated performance
metrics along with the existing test runs (e.g. unit tests, coding standards) we
already have for each new commit. These metrics can be used to identify the exact
point a performance regression is introduced into core. At milestones like a major
releasemajor release A release, identified by the first two numbers (3.6), which
is the focus of a full release cycle and feature development. WordPress uses decimaling
count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable
in scope., the metrics can be compared against the previous release to gauge progress.

## **Goals for the initial version**

The scope of the  initial version of automated performance testing is intentionally
kept limited so we can deliver more quickly, then we can iterate. 

The initial version will include the following features:

 * For each core commit a GitHubGitHub GitHub is a website that offers online implementation
   of git repositories that can easily be shared, copied and modified by other developers.
   Public repositories are free to host, private repositories require a paid subscription.
   GitHub introduced the concept of the ‘pull request’ where code changes done in
   branches by contributors can be reviewed and discussed before being merged by
   the repository owner. [https://github.com/](https://github.com/) action will 
   run a set of automated performance tests, collecting key data points about how
   WordPress is performing (such as total load time and total query time) on blockBlock
   Block is the abstract term used to describe units of markup that, composed together,
   form the content or layout of a webpage using the WordPress editor. The idea 
   combines concepts of what in the past may have achieved with shortcodes, custom
   HTML, and embed discovery into a single consistent API and user experience. and
   classic themes. 
 * The system will collect server timing metrics using the standard WordPress environment
   and current [recommended](https://wordpress.org/about/requirements/) version 
   of PHPPHP The web scripting language in which WordPress is primarily architected.
   WordPress requires PHP 7.4 or higher.  

## **Future Enhancements**

Several areas of work are considered out of scope for the initial implementation,
primarily to keep the focus limited for the initial release — not because they aren’t
good ideas! Once we build a solid foundation for tests and are confident in the 
metrics we are collecting, we can consider additional improvements.

 * Collecting additional metrics: initially we will focus on key server timing metrics
 * Collecting metrics for other contexts: initial metrics will only measure the 
   home page of the latest core block and classic themes with their default demo
   content.
 * SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
   The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
   or ticketticket Created for both bug reports and feature development on the bug
   tracker. reporting: initial work will focus only on collecting and recording 
   metrics at each commit. 

## **FAQ**

**Will the data be stable enough to be useful?**

Performance results can vary in a CI environment, making regressions harder to detect.
To mitigate this, the system will run several iterations and use the median value.

**What metrics will be collected exactly?**

Initially we will only collect a few key metrics to keep the dashboard simple, focused
on the total load time. Once we have established the new tool, we can consider including
additional metrics, or adding hooksHooks In WordPress theme and development, hooks
are functions that can be applied to an action or a Filter in WordPress. Actions
are functions performed when a certain event occurs in WordPress. Filters allow 
you to modify certain functions. Arguments used to hook both filters and actions
look the same. to make the test runs extensibleExtensible This is the ability to
add additional functionality to the code. Plugins extend the WordPress core software..

**What about testing older PHP versions?**

To reduce the time/cost associated with running these tests, they will be limited
to the current recommended version of PHP. Unlike unit tests, performance tests 
are unlikely to produce significantly different deltas for different PHP versions:
regressions are likely to be across PHP versions.

**Why not test wp-adminadmin (and super admin) or more routes?**

In order to keep the time and cost of running these tests low, and the dashboard
simplified, initial testing is intentionally being kept somewhat minimal. In the
future it would be good to consider adding other common routes such as the wp-admin
dashboard and single post page.

---

Thanks to [@tweetythierry](https://profiles.wordpress.org/tweetythierry/) [@flixos90](https://profiles.wordpress.org/flixos90/)
[@joemcgill](https://profiles.wordpress.org/joemcgill/) [@mukesh27](https://profiles.wordpress.org/mukesh27/)
for reviewing this post and to [@youknowriad](https://profiles.wordpress.org/youknowriad/)
for the inspiration (and foundation) of the Gutenberg performance metrics.

[#core-performance](https://make.wordpress.org/core/tag/core-performance/), [#performance](https://make.wordpress.org/core/tag/performance/),
[#testing](https://make.wordpress.org/core/tag/testing/)

 [  ](https://profiles.wordpress.org/boniu91/) [Piotrek Boniu](https://profiles.wordpress.org/boniu91/)
6:30 pm _on_ May 24, 2021     
Tags: [core-test ( 12 )](https://make.wordpress.org/core/tag/core-test/),
testing   

# 󠀁[Test scrub for WordPress 5.8](https://make.wordpress.org/core/2021/05/24/test-scrub-for-wordpress-5-8-2/)󠁿

We’ll be hosting test scrub for WordPress 5.8 on [2021-05-28 13:15](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210528T1315)
in the [core-test](https://app.slack.com/client/T024MFP4J/C02RQBWTW) channel. 
The
following tickets will be manually tested:

 * https://core.trac.wordpress.org/ticket/52555
 * https://core.trac.wordpress.org/ticket/51189

If we’ll have enough time and volunteers, we’ll also test the WidgetWidget A WordPress
Widget is a small block that performs a specific function. You can add these widgets
in sidebars also known as widget-ready areas on your web page. WordPress widgets
were originally created to provide a simple and easy-to-use way of giving design
and structure control of the WordPress theme to the user. Editor:

> [Help Test the Widgets Editor for WordPress 5.8](https://make.wordpress.org/core/2021/05/12/help-test-the-widgets-editor-for-wordpress-5-8/)

 **What you need**

 * [WordPress Develop environment](https://meta.trac.wordpress.org/ticket/5581#comment:3)
 * WordPress BetaBeta A pre-release of software that is given out to a large group
   of users to trial under real conditions. Beta versions have gone through alpha
   testing in-house and are generally fairly close in look, feel and function to
   the final product; however, design changes often occur as part of the process.
   Tester 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/](https://wordpress.org/plugins/)
   or can be cost-based plugin from a third-party. for the second ticketticket Created
   for both bug reports and feature development on the bug tracker.

## 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`

    ```wp-block-preformatted
    npm run grunt patch:35449
    ```

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

    ```wp-block-preformatted
    git fetch upstream pull/828/head:pr-828git checkout pr-828
    ```

or for PR:

    ```wp-block-preformatted
    npm run grunt patch:https://github.com/WordPress/wordpress-develop/pull/828
    ```

Check the handbook for more ways to [test patches](https://make.wordpress.org/core/handbook/testing/patch/).

See you very soon! 👋

[#core-test](https://make.wordpress.org/core/tag/core-test/), [#testing](https://make.wordpress.org/core/tag/testing/)

 [  ](https://profiles.wordpress.org/andraganescu/) [Andrei Draganescu](https://profiles.wordpress.org/andraganescu/)
10:26 am _on_ May 12, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[call for testing ( 5 )](https://make.wordpress.org/core/tag/call-for-testing/),
[customizer ( 6 )](https://make.wordpress.org/core/tag/customizer/), [feature-widgets-block-editor ( 8 )](https://make.wordpress.org/core/tag/feature-widgets-block-editor/),
[gutenberg ( 537 )](https://make.wordpress.org/core/tag/gutenberg/), testing, [widgets ( 26 )](https://make.wordpress.org/core/tag/widgets/)

# 󠀁[Help Test the Widgets Editor for WordPress 5.8](https://make.wordpress.org/core/2021/05/12/help-test-the-widgets-editor-for-wordpress-5-8/)󠁿

![](https://lh5.googleusercontent.com/B6YW1JYazSi_bYz8_7iCLsE4KRO9PDaeTz7kioa6OpWNJSYeBamM8atObkUVXD9siqlSofFgkAo3kefKVGk0scUBFiMXdhP0_9vv-
oOUvFihfW9FoZEwtloxSfE80krsglIa_FU)

Remember the blockBlock Block is the abstract term used to describe units of markup
that, composed together, form the content or layout of a webpage using the WordPress
editor. The idea combines concepts of what in the past may have achieved with shortcodes,
custom HTML, and embed discovery into a single consistent API and user experience.
based Widgets Editor? In case you missed it, this new feature had both a previous
[call for testing](https://make.wordpress.org/core/2020/09/30/call-for-testing-the-widgets-screen-in-gutenberg-9-1/)
and a [merge proposal](https://core.trac.wordpress.org/ticket/51506) ahead of WordPress
5.6. After months of hard work, it’s back and better than ever! For a quick refresher,
the block based Widgets Editor is an upgrade to the widgetWidget A WordPress Widget
is a small block that performs a specific function. You can add these widgets in
sidebars also known as widget-ready areas on your web page. WordPress widgets were
originally created to provide a simple and easy-to-use way of giving design and 
structure control of the WordPress theme to the user. areas provided by WordPress
through themes, that enables users to add blocks right next to widgets to their 
headers, footers, sidebars and other widget areas.

## Help test this feature

This is a call for testing for the new block based Widgets Editor. Please report
your findings on GithubGitHub GitHub is a website that offers online implementation
of git repositories that can easily be shared, copied and modified by other developers.
Public repositories are free to host, private repositories require a paid subscription.
GitHub introduced the concept of the ‘pull request’ where code changes done in branches
by contributors can be reviewed and discussed before being merged by the repository
owner. [https://github.com/](https://github.com/) in the [Gutenberg repository](http://github.com/wordpress/gutenberg)
as issues or in the comments below. If you have triagetriage The act of evaluating
and sorting bug reports, in order to decide priority, severity, and other factors.
access, labeling any issue with [[Feature] Widgets Screen](https://github.com/WordPress/gutenberg/issues?q=is%3Aopen+is%3Aissue+label%3A%22%5BFeature%5D+Widgets+Screen%22)
or [[Feature] Widgets Customizer, ](https://github.com/WordPress/gutenberg/issues?q=is%3Aopen+is%3Aissue+label%3A%22%5BFeature%5D+Widgets+Customizer%22)
depending on the issue, would be very helpful. Alternatively, you can simply include“[
Widgets Screen]” in the title to help those who can set the labels appropriately.
Check out the instructions below for more detailed information.

## What’s new?

![](https://lh5.googleusercontent.com/0w0gYs1hckAcKewh8-xmwSruORkpSQExKPdpybRs8fhoIKsMvqOnT3nM79kwdC-
wEzcK3sAK0MUcFrOkCTWs76ORGtWkOdHVvLEGYbDwqQciFxuquG63KhlaBciP812zt7JkRwA)

The most important addition since the last call for testing is that the CustomizerCustomizer
Tool built into WordPress core that hooks into most modern themes. You can use it
to preview and modify many of your site’s appearance settings. now supports editing
blocks and widgets in widget areas with live preview. Compared to the first iteration
of this project, where the widget areas in the Customizer were read only, now you
can add widgets and blocks with live preview, scheduling and sharing right from 
the Customizer.

The main benefit of upgrading the widgets functionality to blocks comes from the
ability to directly edit widgets using the familiar block interaction that you use
when editing a page or post on your site.  Being able to use blocks opens up tons
of new creative possibilities, from no-code mini layouts to tapping into the vast
library of coreCore Core is the set of software required to run WordPress. The Core
Development Team builds WordPress. and 3rd party blocks to create content. 

For developers, unlocking blocks in widget areas also offers a core path to upgrade
widgets to blocks and get ready for the future. With more aspects of content creation
and management moving to blocks, including the upcoming block based theme format,
this also helps bring consistency to the user experience. 

### Is it ready?

This is currently betaBeta A pre-release of software that is given out to a large
group of users to trial under real conditions. Beta versions have gone through alpha
testing in-house and are generally fairly close in look, feel and function to the
final product; however, design changes often occur as part of the process. software
and it has a host of [known bugs](https://github.com/wordPress/gutenberg/projects/27).
But it is also intended to be merged into core for the 1st beta of [WordPress 5.8](https://make.wordpress.org/core/5-8/).
As a merge candidate the goal of the testing is not to discover 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. free feature, but to observe if there are blockers for merging. During
WordPress 5.8 beta releases, the bug list will be prioritized ahead of the release
candidaterelease candidate One of the final stages in the version release cycle,
this version signals the potential to be a final release to the public. Also see
[alpha (beta)](https://make.wordpress.org/core/tag/testing/?output_format=md#alpha-beta)..

## What to test:

Please keep in mind that it’s recommended that you test this feature on a development
siteDevelopment Site You can keep a copy of your live site in a separate environment.
Maintaining a development site is a good practice that can let you make any changes
and test them without affecting the live/production environment. rather than a production
siteProduction Site A production site is a live site online meant to be viewed by
your visitors, as opposed to a site that is staged for development or testing.. 
For information about how to set up a development site, please refer to the [Setting Up a Development Environment documentation.](https://developer.wordpress.org/themes/getting-started/setting-up-a-development-environment/)

Test using the [WordPress Beta Tester Plugin](https://wordpress.org/plugins/wordpress-beta-tester/)
and set it to:

– Update channel to “Bleeding edgebleeding edge The latest revision of the software,
generally in development and often unstable. Also known as [trunk](https://make.wordpress.org/core/tag/testing/?output_format=md#trunk).”

– Stream options to “Beta/RCrelease candidate One of the final stages in the version
release cycle, this version signals the potential to be a final release to the public.
Also see [alpha (beta)](https://make.wordpress.org/core/tag/testing/?output_format=md#alpha-beta).
only”

You can install the WordPress 5.8 Beta 1 in two ways:

 * Install and activate the [WordPress Beta Tester](https://wordpress.org/plugins/wordpress-beta-tester/)
   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/](https://wordpress.org/plugins/)
   or can be cost-based plugin from a third-party. (select the “Bleeding edge” channel
   and “Beta/RC Only” stream).
 * Direct download the [beta version here (zip)](https://wordpress.org/wordpress-5.8-beta1.zip).

#### **For users:**

**Migrating from classic widgets**

 1.  Be on the latest version of WordPress (5.7.1)
 2.  Go to Appearance > Themes
 3.   * [Install and activate a theme that has support for sidebars](https://wordpress.org/themes/tags/left-sidebar+right-sidebar+footer-widgets/)(
        e.g. TwentyTwenty).
 4.  Go to Plugins > Add new
 5.   * Install and activate a plugin that provides widgets
 6.  Go to Appearance > Widgets
 7.   * Add some core widgets. For example, Search or Recent Posts.
      * Add some 3rd party widgets (aka widgets provided by a plugin)
 8.  Go to Plugins > Add new
 9.   * Install and activate the latest version of the GutenbergGutenberg The Gutenberg
        project is the new Editor Interface for WordPress. The editor improves the 
        process and experience of creating new content, making writing rich content
        much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom
        HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
        plugin
 10. Go to Gutenberg > Experiments
 11.  * Check “Enable Widgets screen in Customizer”
 12. Go to Appearance > Widgets
 13.  * Are all the widgets you added there?
      * Can you customize their settings?
      * Can you drag and drop widgets to different places?
 14. Go to Appearance > Customize > Widgets
 15.  * Are all the widgets you added there?
      * Can you customize their settings?

---

**Adding blocks next to widgets**

 1.  Be on the latest version of WordPress (5.7.1)
 2.  Go to Appearance > Themes
 3.   * Install and activate a theme that has support for sidebars
 4.  Go to Appearance > Widgets
 5.   * Add some core widgets.  For example, Search or Recent Posts.
 6.  Go to Plugins > Add new
 7.   * Install and activate the latest version of the Gutenberg plugin
 8.  Go to Gutenberg > Experiments
 9.   * Check “Enable Widgets screen in Customizer”
 10. Go to Appearance > Widgets
 11.  * Click the inserter plus button in the top bar
      * Add some blocks
         - Do they work?
      * Save
         - Are they published on the front end next to the widgets?
 12. Go to Appearance > Customize > Widgets
 13.  * Click the inserter plus button in the top bar
      * Add some blocks
         - Do they work?
      * Edit some of the block contents
         - Does the preview update accordingly?
      * Edit some of the classic widget’s contents
         - Does the preview update accordingly?
      * Publish
         - Are they published on the front end next to the widgets?

---

**Opting out of the new widgets screen**

 1. Be on the latest version of WordPress (5.7.1)
 2. Go to Plugins > Add new
 3.  * Install and activate the Gutenberg plugin
     * Install and activate the [Classic Widgets plugin](https://wordpress.org/plugins/classic-widgets/)
 4. Go to Appearance > Widgets
 5.  * Is the classic interface present?
 6. Go to Appearance > Customize > Widgets
 7.  * Is the classic interface present?

---

**What to notice:**

 * Did it crash?
 * If it worked, did the editor perform as expected?
 * Was it intuitive for you to add blocks and third party widgets (ie from other
   plugins)?
 * Were you able to properly customize widgets as you wanted? 
 * Did it work using Keyboard only?
 * Did it work using a screen reader?

**For developers:**

Make sure to go through the [general “How to” documentation](https://github.com/WordPress/gutenberg/tree/trunk/docs/how-to-guides/widgets)
available in the Gutenberg codebase for specific instructions. 

**Test upgrading classic widgets to blocks.**

 * The new block based widget editor introduces a new filterFilter Filters are one
   of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks).
   They provide a way for functions to modify data of other functions. They are 
   the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated
   manner, and should never have side effects such as affecting global variables
   and output. `widgets_to_exclude_from_legacy_widget_block`. It is used to hide
   widgets that have block equivalents.
 * We now have a [documented way](https://github.com/WordPress/gutenberg/blob/trunk/docs/how-to-guides/widgets/legacy-widget-block.md#allowing-migration-to-a-block)
   to upgrade widgets to blocks via block transforms.The transform may be added 
   to the legacy widget via typical block extending. This in turn enables users 
   to migrate widgets they already have configured to new block equivalents  provided
   by plugins.

---

**Test enabling and disabling theme support**

 * Test widget areas provided by themes, particularly “dynamic” sidebars, which 
   appear depending on other factors.

---

**Test 3rd party widgets compatibility.**

 * The most common case is for widgets that work in the Customizer but not in the
   stand alone widgets editor. Previously, developers opted to present the widget
   UXUX User experience differently in the widgets screen compared to the Customizer.
   However, the best practices are preserved in the Customizer.
 * We’re having [an audit](https://github.com/WordPress/gutenberg/issues/31126) 
   of extension points and how well supported they are. Please add missing things
   that you may find.

### Considerations around Opt-in vs Opt-out

Because there is not enough data and stories, a decision has not yet been made on
whether the block based Widgets Editor will be opt-out by default or an option for
each theme to opt into. Currently, we’re providing the following options for opting
out:

 * The [Classic Widgets plugin](https://wordpress.org/plugins/classic-widgets/) 
   which allows users to easily opt out of the new blocks in widget areas feature
   and see the classic widget editor only.
 * The `widgets-block-editor` theme supports which allows theme authors to opt out
   of supporting blocks in widget areas. This also reverts WordPress adminadmin (
   and super admin) to the classic widget editor.
 * The `gutenberg_use_widgets_block_editor` filter which allows administrators to
   opt out of supporting blocks in widget areas in cases where this is required.
   Like the two above, this also reverts WordPress admin to the classic widget editor.

A [recent discussion](https://make.wordpress.org/core/2021/05/06/editor-chat-summary-5th-may-2021/)
in the Core Editor chat is a good summary on why we’re opting out via a plugin for
users. Briefly, it seems to be the cleanest and least prone to maintenance requirements
mode possible, versus settings in other plugins or user settings.

This is a difficult decision to make since supporting blocks in widget areas is 
an important part of the roadmap of WordPress and it will eventually be the default
experience. Today, it’s important to determine the impact and significance of the
current work on backwards compatibility.

### Thank you!

Thank you for helping with testing the new Widgets Editor! Since it is one of the
major focuses of WordPress 5.8 any help in this early stage is immensely valuable
as it will help determine how viable it is for merging.

Later updates

**Monday, May 17th** – updated the instruction steps for the user section and added
a step to enable the Customizer widgets block editor. This is essential to test 
the most important addition, adding blocks to widget areas using the Customizer.

**Monday, June 14th** – updated the instruction steps with newer recommended versions
for testing ([WordPress 5.8 Beta 1](https://wordpress.org/wordpress-5.8-beta1.zip)
and [Gutenberg Plugin 10.8](https://github.com/WordPress/gutenberg/releases/tag/v10.6.0)).
Thanks to all the testers and all the feedback below. It was instrumental in advancing
the state of the editor, and it’s now better than ever.

Friday, June 25th – updated the instructions to test using the [WordPress Beta Tester Plugin](https://wordpress.org/plugins/wordpress-beta-tester/).

[#5-8](https://make.wordpress.org/core/tag/5-8/), [#call-for-testing](https://make.wordpress.org/core/tag/call-for-testing/),
[#customizer](https://make.wordpress.org/core/tag/customizer/), [#feature-widgets-block-editor](https://make.wordpress.org/core/tag/feature-widgets-block-editor/),
[#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#testing](https://make.wordpress.org/core/tag/testing/),
[#widgets](https://make.wordpress.org/core/tag/widgets/)

 [  ](https://profiles.wordpress.org/boniu91/) [Piotrek Boniu](https://profiles.wordpress.org/boniu91/)
6:54 pm _on_ May 6, 2021     
Tags: [core-test ( 12 )](https://make.wordpress.org/core/tag/core-test/),
testing   

# 󠀁[Test scrub for WordPress 5.8](https://make.wordpress.org/core/2021/05/06/test-scrub-for-wordpress-5-8/)󠁿

As a part of the 5.8 release, we’ll be hosting test scrub for WordPress 5.8 on [2021-05-07 13:15](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210507T1315)
in the [core-test](https://app.slack.com/client/T024MFP4J/C02RQBWTW) channel. 
We’ll
do manual testing of the below tickets: https://core.trac.wordpress.org/ticket/43697https://
core.trac.wordpress.org/ticket/50866 We’ll appreciate your participation and feedback!**
What you need**

 * [WordPress Develop environment](https://meta.trac.wordpress.org/ticket/5581#comment:3),
   PHP8 will be an advantage

## 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. ticketticket Created for both bug reports
and feature development on the bug tracker., for example `35449`

    ```wp-block-preformatted
    npm run grunt patch:35449
    ```

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

    ```wp-block-preformatted
    git fetch upstream pull/828/head:pr-828git checkout pr-828
    ```

or for PR:

    ```wp-block-preformatted
    npm run grunt patch:https://github.com/WordPress/wordpress-develop/pull/828
    ```

Check the handbook for more ways to [test patches](https://make.wordpress.org/core/handbook/testing/patch/).

Looking forward to seeing you!

[#core-test](https://make.wordpress.org/core/tag/core-test/), [#testing](https://make.wordpress.org/core/tag/testing/)

 [  ](https://profiles.wordpress.org/boniu91/) [Piotrek Boniu](https://profiles.wordpress.org/boniu91/)
7:00 pm _on_ April 12, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[test ( 16 )](https://make.wordpress.org/core/tag/test/), testing   

# 󠀁[Early test scrub for WordPress 5.8](https://make.wordpress.org/core/2021/04/12/early-test-scrub-for-wordpress-5-8-2/)󠁿

In the previous week we didn’t run the test scrub. That’s why the agenda stays the
same for this week. Early test scrub for WordPress 5.8 will take place on [2021-04-16 13:30](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210416T1330)
in the [core-test](https://app.slack.com/client/T024MFP4J/C02RQBWTW) channel.

We’ll do manual testing of the below tickets, making sure there are no regressions:

[https://core.trac.wordpress.org/ticket/32579](https://core.trac.wordpress.org/ticket/32579)
[https://core.trac.wordpress.org/ticket/52226](https://core.trac.wordpress.org/ticket/52226)
[https://core.trac.wordpress.org/ticket/52521](https://core.trac.wordpress.org/ticket/52521)
[https://core.trac.wordpress.org/ticket/52662](https://core.trac.wordpress.org/ticket/52662)
[https://core.trac.wordpress.org/ticket/40570](https://core.trac.wordpress.org/ticket/40570)
[https://core.trac.wordpress.org/ticket/39108](https://core.trac.wordpress.org/ticket/39108)

**We’ll appreciate your participation and feedback!**
**What you need**

 * WordPress environment
 * WordPress 5.8 alpha release, try the [WordPress Beta Tester plugin](https://wordpress.org/plugins/wordpress-beta-tester/)(
   choose the “Bleeding edgebleeding edge The latest revision of the software, generally
   in development and often unstable. Also known as [trunk](https://make.wordpress.org/core/tag/testing/?output_format=md#trunk).”
   channel and BetaBeta A pre-release of software that is given out to a large group
   of users to trial under real conditions. Beta versions have gone through alpha
   testing in-house and are generally fairly close in look, feel and function to
   the final product; however, design changes often occur as part of the process./
   RCrelease candidate One of the final stages in the version release cycle, this
   version signals the potential to be a final release to the public. Also see [alpha (beta)](https://make.wordpress.org/core/tag/testing/?output_format=md#alpha-beta).
   Only” stream options)
 * Two of the tickets are not merged yet. To test them we’ll need to set up the 
   Testing Environment by following the steps listed here – [https://meta.trac.wordpress.org/ticket/5581#comment:3](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. ticketticket Created for both bug reports
and feature development on the bug tracker., for example `35449`

    ```wp-block-preformatted
    npm run grunt patch:35449
    ```

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

    ```wp-block-preformatted
    git fetch upstream pull/828/head:pr-828git checkout pr-828
    ```

or for PR:

    ```wp-block-preformatted
    npm run grunt patch:https://github.com/WordPress/wordpress-develop/pull/828
    ```

Check the handbook for more ways to [test patches](https://make.wordpress.org/core/handbook/testing/patch/).

Looking forward to seeing you!

[#5-8](https://make.wordpress.org/core/tag/5-8/), [#test](https://make.wordpress.org/core/tag/test/),
[#testing](https://make.wordpress.org/core/tag/testing/)

 [  ](https://profiles.wordpress.org/boniu91/) [Piotrek Boniu](https://profiles.wordpress.org/boniu91/)
12:50 pm _on_ April 7, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[test ( 16 )](https://make.wordpress.org/core/tag/test/), testing   

# 󠀁[Early test scrub for WordPress 5.8](https://make.wordpress.org/core/2021/04/07/early-test-scrub-for-wordpress-5-8/)󠁿

As a part of the 5.8 release, we’ll be hosting early test scrub for WordPress 5.8
on [2021-04-09 13:30](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210409T1330)
in the [core-test](https://app.slack.com/client/T024MFP4J/C02RQBWTW) channel.
We’ll
do manual testing of the below tickets, making sure there are no regressions:[https://core.trac.wordpress.org/ticket/32579](https://core.trac.wordpress.org/ticket/32579)
[https://core.trac.wordpress.org/ticket/52226](https://core.trac.wordpress.org/ticket/52226)
[https://core.trac.wordpress.org/ticket/52521](https://core.trac.wordpress.org/ticket/52521)
[https://core.trac.wordpress.org/ticket/52662](https://core.trac.wordpress.org/ticket/52662)
[https://core.trac.wordpress.org/ticket/40570](https://core.trac.wordpress.org/ticket/40570)
[https://core.trac.wordpress.org/ticket/39108](https://core.trac.wordpress.org/ticket/39108)
We’ll appreciate your participation and feedback!**What you need**

 * WordPress environment
 * WordPress 5.8 alpha release, try the [WordPress Beta Tester plugin](https://wordpress.org/plugins/wordpress-beta-tester/)(
   choose the “Bleeding edgebleeding edge The latest revision of the software, generally
   in development and often unstable. Also known as [trunk](https://make.wordpress.org/core/tag/testing/?output_format=md#trunk).”
   channel and BetaBeta A pre-release of software that is given out to a large group
   of users to trial under real conditions. Beta versions have gone through alpha
   testing in-house and are generally fairly close in look, feel and function to
   the final product; however, design changes often occur as part of the process./
   RCrelease candidate One of the final stages in the version release cycle, this
   version signals the potential to be a final release to the public. Also see [alpha (beta)](https://make.wordpress.org/core/tag/testing/?output_format=md#alpha-beta).
   Only” stream options)
 * Two of the tickets are not merged yet. To test them we’ll need to set up the 
   Testing Environment by following the steps listed here – [https://meta.trac.wordpress.org/ticket/5581#comment:3](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. ticketticket Created for both bug reports
and feature development on the bug tracker., for example `35449`

    ```wp-block-preformatted
    npm run grunt patch:35449
    ```

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

    ```wp-block-preformatted
    git fetch upstream pull/828/head:pr-828git checkout pr-828
    ```

or for PR:

    ```wp-block-preformatted
    npm run grunt patch:https://github.com/WordPress/wordpress-develop/pull/828
    ```

Check the handbook for more ways to [test patches](https://make.wordpress.org/core/handbook/testing/patch/).

Looking forward to seeing you!

[#test](https://make.wordpress.org/core/tag/test/), [#testing](https://make.wordpress.org/core/tag/testing/)

[#5-8](https://make.wordpress.org/core/tag/5-8/)

 [  ](https://profiles.wordpress.org/monikarao/) [Monika Rao](https://profiles.wordpress.org/monikarao/)
7:51 am _on_ February 5, 2021     
Tags: [5.7 ( 67 )](https://make.wordpress.org/core/tag/5-7/),
[test ( 16 )](https://make.wordpress.org/core/tag/test/), testing   

# 󠀁[Test scrub for WordPress 5.7 Beta 1 and office hours](https://make.wordpress.org/core/2021/02/05/test-scrub-for-wordpress-5-7-beta-1-and-office-hours/)󠁿

As part of the 5.7 release, we’ll be hosting a ** BetaBeta A pre-release of software
that is given out to a large group of users to trial under real conditions. Beta
versions have gone through alpha testing in-house and are generally fairly close
in look, feel and function to the final product; however, design changes often occur
as part of the process. 1 focused test scrub** on [February 5, 2021 13:30 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210205T1330)
in the [#core](https://app.slack.com/client/T024MFP4J/C02RQBWTW) channel on SlackSlack
Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/).

In particular, we will focus on user testing and discuss all improvements. Since
there are no use-cases listed, we will take the opportunity also to start writing
down common actions users perform, so we can build up testing scenarios.

Please join us and share your valuable feedback.

You can read more about Beta 1 on its announcement post.
[https://wordpress.org/news/2021/02/wordpress-5-7-beta-1/](https://wordpress.org/news/2021/02/wordpress-5-7-beta-1/)**
What you need**– Test website– WordPress 5.7 Beta 1:– Try the [WordPress Beta Tester plugin](https://wordpress.org/plugins/wordpress-beta-tester/)(
choose the “Bleeding edgebleeding edge The latest revision of the software, generally
in development and often unstable. Also known as [trunk](https://make.wordpress.org/core/tag/testing/?output_format=md#trunk).”
channel and Beta/RCrelease candidate One of the final stages in the version release
cycle, this version signals the potential to be a final release to the public. Also
see [alpha (beta)](https://make.wordpress.org/core/tag/testing/?output_format=md#alpha-beta).
Only” stream options)– Or [download the release candidate here (zip).](https://wordpress.org/wordpress-5.7-beta1.zip)

Looking forward to testing with you!
[#test](https://make.wordpress.org/core/tag/test/),
[#testing](https://make.wordpress.org/core/tag/testing/)

[#5-7](https://make.wordpress.org/core/tag/5-7/), [#test](https://make.wordpress.org/core/tag/test/),
[#testing](https://make.wordpress.org/core/tag/testing/)

 [  ](https://profiles.wordpress.org/monikarao/) [Monika Rao](https://profiles.wordpress.org/monikarao/)
10:19 am _on_ January 28, 2021     
Tags: [5.7 ( 67 )](https://make.wordpress.org/core/tag/5-7/),
[core ( 720 )](https://make.wordpress.org/core/tag/core/), [test ( 16 )](https://make.wordpress.org/core/tag/test/),
testing   

# 󠀁[Test Scrub for WordPress 5.7 and office hours](https://make.wordpress.org/core/2021/01/28/test-scrub-for-wordpress-5-7-and-office-hours-2/)󠁿

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](https://make.wordpress.org/core/tag/core/)
channel on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/).

[https://core.trac.wordpress.org/ticket/51812](https://core.trac.wordpress.org/ticket/51812https://core.trac.wordpress.org/ticket/51941https://core.trac.wordpress.org/ticket/52355https://core.trac.wordpress.org/ticket/48562https://core.trac.wordpress.org/ticket/47912)

[https://core.trac.wordpress.org/ticket/51941](https://core.trac.wordpress.org/ticket/51812https://core.trac.wordpress.org/ticket/51941https://core.trac.wordpress.org/ticket/52355https://core.trac.wordpress.org/ticket/48562https://core.trac.wordpress.org/ticket/47912)
[https://core.trac.wordpress.org/ticket/52355](https://core.trac.wordpress.org/ticket/51812https://core.trac.wordpress.org/ticket/51941https://core.trac.wordpress.org/ticket/52355https://core.trac.wordpress.org/ticket/48562https://core.trac.wordpress.org/ticket/47912)
[https://core.trac.wordpress.org/ticket/48562](https://core.trac.wordpress.org/ticket/51812https://core.trac.wordpress.org/ticket/51941https://core.trac.wordpress.org/ticket/52355https://core.trac.wordpress.org/ticket/48562https://core.trac.wordpress.org/ticket/47912)
[https://core.trac.wordpress.org/ticket/47912](https://core.trac.wordpress.org/ticket/51812https://core.trac.wordpress.org/ticket/51941https://core.trac.wordpress.org/ticket/52355https://core.trac.wordpress.org/ticket/48562https://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](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`

    ```wp-block-preformatted
    npm run grunt patch:35449
    ```

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

    ```wp-block-preformatted
    git fetch upstream pull/828/head:pr-828git checkout pr-828
    ```

or for PR:

    ```wp-block-preformatted
    npm run patch https://github.com/WordPress/wordpress-develop/pull/828
    ```

Check the handbook for more ways to [test patches](https://make.wordpress.org/core/handbook/testing/patch/).

## 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/](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](https://make.wordpress.org/core/tag/5-7/), [#test](https://make.wordpress.org/core/tag/test/),
[#testing](https://make.wordpress.org/core/tag/testing/)

[#5-7](https://make.wordpress.org/core/tag/5-7/), [#test](https://make.wordpress.org/core/tag/test/),
[#testing](https://make.wordpress.org/core/tag/testing/)

 [  ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/)
11:57 am _on_ January 22, 2021     
Tags: [5.7 ( 67 )](https://make.wordpress.org/core/tag/5-7/),
[test ( 16 )](https://make.wordpress.org/core/tag/test/), testing   

# 󠀁[Test Scrub for WordPress 5.7 and office hours](https://make.wordpress.org/core/2021/01/22/test-scrub-for-wordpress-5-7-and-office-hours/)󠁿

As part of the 5.7 release, we’ll be hosting a** **focused test scrub for tickets
listed in [this report](https://core.trac.wordpress.org/query?keywords=~needs-testing+-needs-testing-info+-needs-refresh+-needs-unit-tests+-2nd-opinion+-dev-feedback&id=!37110&milestone=5.7&col=id&col=summary&col=keywords&col=owner&col=type&col=status&col=priority&col=component&col=changetime&order=type),
later today, Friday Janury 22, 2021 13:30 UTC in the [#core](https://app.slack.com/client/T024MFP4J/C02RQBWTW)
channel on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/).

The report will show tickets that

Have `needs-testing` label

Don’t have

 * `needs-testing-info`
 * `needs-refresh`
 * `needs-unit-tests`
 *  `2nd-opinion`
 * `dev-feedback`

labels.

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.

## **Testing Environment**

 1.  Open the Terminal app
 2.  Install [homebrew](https://brew.sh/) by pasting /`bin/bash -c "$(curl -fsSL https://
     raw.githubusercontent.com/Homebrew/install/master/install.sh)"` – You might be
     asked if you want to install the Xcode Command Line Tools, confirm.
 3.  Install GitGit Git is a free and open source distributed version control system
     designed to handle everything from small to very large projects with speed and
     efficiency. Git is easy to learn and has a tiny footprint with lightning fast 
     performance. Most modern plugin and theme development is being done with this 
     version control system. [https://git-scm.com/](https://git-scm.com/) by typing`
     brew install Git`
 4.  Install Docker by typing `brew cask install Docker`.
 5.   * If you get an error you can try `brew install cask Docker` or install [Docker Desktop](https://www.docker.com/products/docker-desktop)
 6.  Install Node by typing `brew install Node`
 7.  Open the Docker app in your computer and ignore the welcome screen that tells 
     you to create a container
 8.  Clone the GitHubGitHub GitHub is a website that offers online implementation of
     git repositories that can easily be shared, copied and modified by other developers.
     Public repositories are free to host, private repositories require a paid subscription.
     GitHub introduced the concept of the ‘pull request’ where code changes done in
     branches by contributors can be reviewed and discussed before being merged by 
     the repository owner. [https://github.com/](https://github.com/) repository with
     the [wordpress-development environment](https://github.com/WordPress/wordpress-develop)
     by typing `git clone` and the URLURL A specific web address of a website or web
     page on the Internet, such as a website’s URL www.wordpress.org you get when you
     click on the green button on the top of the GitHub repo that says `Code`. Pick
     the HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS
     is the secure version of HTTP, the protocol over which data is sent between your
     browser and the website that you are connected to. The 'S' at the end of HTTPS
     stands for 'Secure'. It means all communications between your browser and the 
     website are encrypted. This is especially helpful for protecting sensitive data
     like banking information. URL.
 9.  Go to the directory where you cloned the repo (you can use `cd wordpress-develop`
     to locate it)
 10. Now type these 4 commands
 11.  a. `npm install`
      b. `npm run build:dev`
      c. `npm run env:start`
      d. `npm run env:install`
 12. You should be able to access the development version of WordPress at [http://localhost:8889/](http://localhost:8889/).
     You can access it with username `admin` and password `password`

## 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`

    ```wp-block-code
    npm run grunt patch:35449
    ```

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

    ```wp-block-code
    git fetch upstream pull/828/head:pr-828git checkout pr-828
    ```

or for PR:

    ```wp-block-code
    npm run grunt patch:https://github.com/WordPress/wordpress-develop/pull/828
    ```

Check the handbook for more ways to [test patches](https://make.wordpress.org/core/handbook/testing/patch/).

## 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/](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](https://make.wordpress.org/core/tag/5-7/), [#test](https://make.wordpress.org/core/tag/test/),
[#testing](https://make.wordpress.org/core/tag/testing/)

 [  ](https://profiles.wordpress.org/monikarao/) [Monika Rao](https://profiles.wordpress.org/monikarao/)
5:54 am _on_ January 15, 2021     
Tags: [5.7 ( 67 )](https://make.wordpress.org/core/tag/5-7/),
[test ( 16 )](https://make.wordpress.org/core/tag/test/), testing   

# 󠀁[Test Scrub for WordPress 5.7](https://make.wordpress.org/core/2021/01/15/test-scrub-for-wordpress-5-7/)󠁿

As part of the 5.7 release, we’ll be hosting test scrubs focused on the tickets 
milestoned for 5.7 on Friday, [January 12, 2021 at 13:30 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210112T1330)
in the [#core](https://app.slack.com/client/T024MFP4J/C02RQBWTW) channel on SlackSlack
Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/).

Following are the tickets going to be discussed in the scrub

 * [https://core.trac.wordpress.org/ticket/52073](https://core.trac.wordpress.org/ticket/52073)
 * [https://core.trac.wordpress.org/ticket/52038](https://core.trac.wordpress.org/ticket/52038)
 * [https://core.trac.wordpress.org/ticket/49245](https://core.trac.wordpress.org/ticket/49245)

## **Testing Environment**

 1.  Open the Terminal app
 2.  Install [homebrew](https://brew.sh/) by pasting /`bin/bash -c "$(curl -fsSL https://
     raw.githubusercontent.com/Homebrew/install/master/install.sh)"` – You might be
     asked if you want to install the Xcode Command Line Tools, confirm.
 3.  Install GitGit Git is a free and open source distributed version control system
     designed to handle everything from small to very large projects with speed and
     efficiency. Git is easy to learn and has a tiny footprint with lightning fast 
     performance. Most modern plugin and theme development is being done with this 
     version control system. [https://git-scm.com/](https://git-scm.com/) by typing`
     brew install Git`
 4.  Install Docker by typing `brew cask install Docker`
 5.  Install Node by typing `brew install Node`
 6.  Open the Docker app in your computer and ignore the welcome screen that tells 
     you to create a container
 7.  Clone the GitHubGitHub GitHub is a website that offers online implementation of
     git repositories that can easily be shared, copied and modified by other developers.
     Public repositories are free to host, private repositories require a paid subscription.
     GitHub introduced the concept of the ‘pull request’ where code changes done in
     branches by contributors can be reviewed and discussed before being merged by 
     the repository owner. [https://github.com/](https://github.com/) repository with
     the [wordpress-development environment](https://github.com/WordPress/wordpress-develop)
     by typing `git clone` and the URLURL A specific web address of a website or web
     page on the Internet, such as a website’s URL www.wordpress.org you get when you
     click on the green button on the top of the GitHub repo that says `Code`. Pick
     the HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS
     is the secure version of HTTP, the protocol over which data is sent between your
     browser and the website that you are connected to. The 'S' at the end of HTTPS
     stands for 'Secure'. It means all communications between your browser and the 
     website are encrypted. This is especially helpful for protecting sensitive data
     like banking information. URL.
 8.  Go to the directory where you cloned the repo (you can use cd wordpress-develop
     to locate it)
 9.  Now type these 4 commands
 10.  a. npm install
      b. npm run build:dev
      c. npm run env:start
      d. npm run env:install
 11. You should be able to access the development version of WordPress at [http://localhost:8889/](http://localhost:8889/).
     You can access it with username `admin` and password `password`

## Do you have a ticketticket Created for both bug reports and feature development on the bug tracker. you want to bring up for testing?

Fantastic!

In order to allow testers to manually test the 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 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/](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](https://make.wordpress.org/core/tag/5-7/), [#test](https://make.wordpress.org/core/tag/test/),
[#testing](https://make.wordpress.org/core/tag/testing/)

# Post navigation

[← Older posts](https://make.wordpress.org/core/tag/testing/page/2/?output_format=md)