Call for Testing: WordPress for Android 14.1

WordPress for Android version 14.1-rc-1 is available for testing on the 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. channel. You can ask to join the Beta Program at Android App Testing on Google Play. Once you have been accepted, click the “Become a Tester” button at the same link.

To test with an apk, you can download wpandroid-14.1-rc-1-universal.apk.

Bugs & Feedback

If you find a bug or want to share a feature request after testing, you can comment on this post, pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” one of us in the #mobile room on WordPress.org Slack, or head straight GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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 be the repository owner. https://github.com/ and open an issue—please see “Where to Report” below.

What to Test

To prepare:

  • Go to My Site > Settings > Use 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. Editor to enable the block editor for new posts.
  • If you are comfortable testing in a language other than English, please test in that language.

To test:

  1. 11098 Start with a fresh installation so there are no posts in the DB, use a WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ site for testing, go to My Site > Posts (do not scroll at all), type a search query for a very old post or for a post in the trashTrash Trash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level (administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days.. Verify that the same search returns the same results using WordPress.com/sites > Posts > Search.
  2. 11099 Go to My Sites > Switch Site, tap and hold a Jetpack or Atomic site, verify that the “Remove Site” dialog is not shown and instead you are able to show/hide the site instead. Repeat the steps for a WordPress.com and a Self-hosted site and verify that only the Self-hosted site gets the option to “Remove site”.
  3. 19534 Create a new post in the block editor, add any shortcode, try to break the block. Try with 5 randomly chosen shortcodes.
  4. 992 Open a post that has many blocks and verify the padding between blocks isn’t unreasonably large.
  5. 10505 Create a post with 500-1,000 paragraph blocks, quickly scroll through the post for a while, verify you cannot crash the app even after a minute or so of scrolling. (53s)
  6. There is an open-ended ask to test every area of the editor with both and without the block editor turned on. A lot of changes to the saving/uploading logic were made which basically touched everything in the editor. Please test creating a few new posts and publishing them, at least one while you are online and one while you are offline plus one that’s scheduled to publish at a later time.

You can find more details about all of the updates for this releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. in the related PRs targeting WordPress-Android 14.1 and gutenberg-mobile 1.21.

Where to Report

  • WordPress-Android on GitHub for non-block-editor issues.
  • gutenberg-mobile on GitHub for block editor issues.
  • This post for questions, feedback, or issues you’re not sure how to report in GitHub.

Instructions for Reporting Issues

  • Search the GitHub repository first to see if the bug is a known issue.
  • For known issues, please leave a comment on the issue saying you were able to replicate the problem and include device name, iOSiOS The operating system used on iPhones and iPads. version, app version, and type of site you used for testing.
  • For new issues, please follow the template GitHub repository that shows up when creating a new issue.
  • Please be aware that a bot will ask for labels but you won’t have rights to add them. Know that labels will be added by someone on the triage team.
  • If you would like to send Activity Logs to help with debugging (this can be very useful!), you should first trigger the bug and then go to Profile > Help & Support > Application log and use the copy icon at top right to copy the logs. Next, go to Help & Support > Contact us, add a short note mentioning the bug report link, and paste the logs below the note. Please be aware that the Application log may contain tokens which should not be shared publicly, and that’s why logs should be sent through the Contact us form.

Thanks for testing! ❤️

#14-1, #android, #call-for-testing, #mobile