Call for Testing: WordPress for Android 14.0

WordPress for Android version 14.0-rc-1 is available for testing on the Beta 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.0-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, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see “Where to Report” below.

What to Test

To prepare:

  • Go to My Site > Settings > Use Block 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. 1631 On the web, create a draft with aligned images. In the app, open an empty post (to load the js from the metro bundler), go to Blog Posts > Drafts, turn on airplane mode, open the draft, make sure images have placeholder images.
  2. 1701 In the block editor in the app, add a paragraph block, type some characters, undo changes until the block is removed. Repeat if necessary. App should not crash.
  3. 11074 Check that the profile icon is at top right and no longer in the bottom menu. Tap on the profile icon, make sure everything loads normally, tap the back arrow, make sure you are taken back to the My Site screen.
  4. 11074 Go to My Site and tap the “+” button at bottom right to open a selector, the tooltip should go away at that point, select one of the options, make sure editor opens, create a post/page and tap on the back arrow, confirm you are taking back to the main screen and you see a notice that the post was saved, check the new created post or page was created and available in the correct list (Published/Draft).
  5. 11074 Create a new site from the app and tap Accept on the dialog below to get access to the Quick Start tutorials. Go through the tutorials and check that everything works as expected, especially the Publish Post step.
  6. Last, there is an open-ended ask to test every area of the editor with both Aztec and Gutenberg. A lot of changes to the saving/uploading logic were made which basically touched everything in the editor.

You can find more details about all of the updates for this release in the related PRs targeting WordPress-Android 14.0 and gutenberg-mobile 1.20.

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.

Thanks for testing! ❤️

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

Call for Testing: WordPress for Android 13.9

WordPress for Android version 13.9-rc-1 is available for testing on the Beta 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-13.9-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, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see “Where to Report” below.

What to Test

To prepare:

  • Go to My Site > Settings > Use Block 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. 1498 Add a gallery block to a post or page and try to break it: add images, remove images, change the number of columns, crop images, add captions, rotate the device while interacting with the block
  2. 1615 Add a preformatted block to a post or page and used some text with various types of white space. Add another preformatted block and merge the two blocks.
  3. 1619 Add a list block, change it to an ordered list (numbered), change the start value of the list and make the numbering go in reverse order.
  4. 1601 Add a video block, tap on the settings icon (cog), change each one of the video settings, save changes, and verify the settings are each working as expected.
  5. 10717 From a WordPress.com site that has a domain credit available, start the domain registration process, pick a domain that you know is not available, verify you see an error if the domain is taken or invalid.
  6. 10833 Go to My Sites > Switch Site > + > Add self-hosted site, enter an address, when you see the username and password prompt minimize the app and wait an hour then go back to the app and verify the app does not crash.
  7. 10833 Go to the Log In screen and input incorrect credentials, minimize the app, go back to the app and verify you can log in using the correct credentials.
  8. 10479 Add a QuickPress widget, switch to a different blog in the app, click on the widget. The app should not crash.
  9. We improved accessibility via TalkBack in Sign up and login, the editor and the empty view screens. If you are a TalkBack user, please tell us if this helps you navigating the app.

You can find more details about all of the updates for this release in the related PRs targeting WordPress-Android 13.9 and gutenberg-mobile 1.19.

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.

Thanks for testing! ❤️

#13-9, #android, #call-for-testing, #mobile

Call for Testing: WordPress for Android 13.8

WordPress for Android version 13.8-rc-1 is available for testing on the Beta 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-13.8-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, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see “Where to Report” below.

What to Test

To prepare:

  • Go to My Site > Settings > Use Block 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. 10817 Add a spacer block to any post. Try to break it. View results on various screen sizes, including desktop, and make sure the block works as expected.
  2. 10837 Go to My Sites > Blog Posts and search for various posts including published, drafts, scheduled, and trashed. Can you find what you’re looking for?
  3. 10763 Add images and videos to any post or page. Try rotating the screen during editing. Switch to HTML during editing. Try with both the classic and block editors. Leave the editor then edit again and make sure media appears as expected. See additional testing ideas here.
  4. Create and publish a new post with as many blocks as possible.
  5. Try tapping on push notifications to launch the app, does it crash?
  6. There were 26 unique crash and bug fixes included in this release! In general, can you figure out any ways to crash the app?

You can find more details about all of the updates for this release in the related PRs targeting WordPress-Android 13.8 and gutenberg-mobile 1.18.

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.

Thanks for testing! ❤️

#13-8, #android, #call-for-testing, #mobile

Call for Testing: WordPress for Android 13.7

WordPress for Android version 13.7-rc-1 is available for testing on the Beta 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-13.7-rc-1-universal.apk from here.

Bugs & Feedback

If you find a bug or want to share a feature request after testing, you can comment on this post, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see “Where to Report” below.

What to Test

To prepare:

  • Go to My Site > Settings > Use Block 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. 1533 On the web, create and publish a post with as many different block types as you can. Open the post in the mobile app and check that the titles of the blocks are accurate.
  2. 1542 Start a new post, tap the “+” button to insert a new block, and confirm you can see the “Add New Block” indicator when there are no blocks at all and when at the last block.
  3. 1537 Copy a URL from Safari or elsewhere, select some text in a post, tap the link button, confirm that the URL field is automatically populated using the link from the clipboard. Edit an already existing link and check that the link in the clipboard does not override the one already existing. Try adding a few other links in different ways.
  4. 1546 Add the Media & Text block and test vertical alignment options.
  5. 1577 Selecting an image block should show a blue border and you should be able to press the image to see a full-screen preview.
  6. 1582 Add and remove empty blocks a few times in a row and try to crash the app.
  7. 10788 Edit an existing post on the web, wait for an autosave, and close the browser tab without saving—then open the post in the app and confirm the dates in the conflict resolution dialog are accurate according to your device timezone. Follow up at 10773 too.

You can find more details about all of the updates for this release in the related PRs targeting WordPress-Android 13.7 and gutenberg-mobile 1.17.

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.

Thanks for testing! ❤️

#13-7, #android, #call-for-testing, #mobile

Call for Testing: WordPress for Android 13.6

WordPress for Android version 13.6-rc-1 is available for testing on the Beta 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-13.6-rc-1-universal.apk from here.

Bugs & Feedback

If you find a bug or want to share a feature request after testing, you can comment on this post, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see “Where to Report” below.

What to Test

To prepare:

  • Go to My Site > Settings > Use Block 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. 10713 Check as many different screens as possible and look for the bottom navigation color to be white (limited to Android 8.1+).
  2. 10708 Verify that page ordering is now case insensitive.
  3. 1469 Try adding images using the “Choose from Free Photo Library” and “Choose from Giphy” option and make sure the images are added and appear as expected in previews and after publishing the post. Test adding an image in a post or page as well as as a featured image.
  4. 1460 Add several images in different ways to a post and pick different alignments. Check that image alignments made in the block editor on mobile are reflected on the web from a laptop and vice versa.

You can find more details about all of the updates for this release in the related PRs targeting WordPress-Android 13.6 and gutenberg-mobile 1.16.

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.

Thanks for testing! ❤️

#13-6, #android, #call-for-testing, #mobile

Call for Testing: WordPress for Android 13.5

WordPress for Android version 13.5-rc-1 is available for testing on the Beta 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-13.5-rc-1-universal.apk from here.

Bugs & Feedback

If you find a bug or want to share a feature request after testing, you can comment on this post, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see “Where to Report” below.

What to Test

To prepare:

  • Go to My Site > Settings > Use Block 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. 1331 Block editor: add multiple images or videos at once and check that all get added. Do any problems happen when you upload the post? How many did you add in one go?
  2. 1394 Block editor: add an image link that opens in a new tab.
  3. 1439 Block editor: try adding and removing the Media & Text block. Try to break it.

You can find more details about all of the updates for this release in the related PRs targeting WordPress-Android 13.5 and gutenberg-mobile 1.15.

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.

Thanks for testing! ❤️

#13-5, #android, #call-for-testing, #mobile

Call for Testing: WordPress for Android 13.4

WordPress for Android version 13.4-rc-1 is available for testing on the Beta 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-13.4-rc-1-universal.apk from here.

Bugs & Feedback

If you find a bug or want to share a feature request after testing, you can comment on this post, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see “Where to Report” below.

What to Test

To prepare:

  • Set up a Jetpack site for testing if you don’t already have one. You can use jurassic.ninja to quickly create a Jetpack testing site.
  • Go to My Site > Settings > Use Block Editor to enable the block editor for new posts.

To test:

  1. Block Editor: create and publish post several available blocks—get creative, think like a user, try to break the editor.
  2. 10536 Verify that changes to a draft or published post on self-hosted and Jetpack sites are labeled as “local changes” and are not auto-uploaded.
  3. 10536 Try previewing changes to pre-existing drafts or previously published posts on self-hosted sites and Jetpack. Previews are not supported on these types of sites so you should see a preview unavailable notice.
  4. Come up with an additional scenario to test an autosave, auto-upload, or remote preview. There have been several changes in this area.
  5. 10106 Post List: try previewing a trashed post. You should not see Edit or View buttons and you should not be able to preview before restoring the post. Note the type of site you tested.
  6. 10457 Post List: Create an unpublished revision in WP Admin, open the post in the app, select “More recent version/The version from another device”, go back without making changes, then open the post in the app again and verify the change made in WP Admin is showing in the app.
  7. 10402 Create a private draft while offline, go online, publish the post, verify the post is still private.
  8. 10536 Create a new draft then exit without saving and verify an autosave happens. Try with different site types (self-hosted, Jetpack, or WordPress.com). Note: new drafts should always be autosaved and auto-uploaded.
  9. 10557 Open an existing draft in the block editor, add an image, tap back before the upload finishes, open the post again and check the HTML and make sure you do not see a local path for the image.
  10. 10517 Create a draft on a self-hosted site, turn on airplane mode, add an image, tap Publish, turn off airplane mode, confirm the post and media are published with no errors.
  11. 14270 Block editor: select text, tap Link button, exit without adding a link, check that no link was added. Check that adding a link after that still works.

You can find more details about all of the updates for this release in the related PRs targeting WordPress-Android 13.4 and gutenberg-mobile 1.14.

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.

Thanks for testing! ❤️

#13-4, #android, #call-for-testing, #mobile

Call for Testing: WordPress for Android 13.3

WordPress for Android version 13.3-rc-1 is available for testing on the Beta 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-13.3-rc-1-universal.apk from here.

Bugs & Feedback

If you find a bug or want to share a feature request after testing, you can comment on this post, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see “Where to Report” below.

What to Test

To prepare:

  • Set up a Jetpack site for testing if you don’t already have one. You can use jurassic.ninja to quickly create a Jetpack testing site.
  • Go to My Site > Settings > Use Block Editor to enable the block editor for new posts.

To test:

  1. Block Editor: create and publish post using all of the available blocks (Paragraph, Heading, Image, Lists, Separator, Page Break, Quote, More) and check that each one works as expected.
  2. 10497 Change your username in the app.
  3. 10468 From a Jetpack site in the app, go to Settings > Performance and try updating the options and verifying they were saved by comparing the updated settings via the web. Try from accounts with different types of plans.
  4. 10476 Check that a site with <100 published pages are ordered topologically and a site with >=100 pages are ordered chronologically.
  5. 10434 Browse as many pages in stats as you can. Does the performance seem good? Is anything extremely slow loading?
  6. 10483 Open a draft, edit title and content, close and re-open the app, make sure the title and content edits were not lost.
  7. 1200 Open the block editor, tap on the empty editor area, verify that a new empty block is created.
  8. 975 Add a caption with rich text to a video block.
  9. 1254 Open a post that has a paragraph and a video block—tap between the caption and paragraph block and make sure the keyboard stays open.
  10. 1262 Select an empty paragraph block, tap + to add a new block, the empty paragraph block should be hidden and when a block is selected then it should get replaced by the new block that is added. See other test scenarios at 16931.

You can find more details about all of the updates for this release in the related PRs targeting WordPress-Android 13.3 and gutenberg-mobile 1.12.

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.

Thanks for testing! ❤️

#13-3, #android, #call-for-testing, #mobile

Call for Testing: WordPress for Android 13.2

WordPress for Android version 13.2-rc-1 is available for testing on the Beta 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-13.2-rc-1-universal.apk from here.

Bugs & Feedback

If you find a bug or want to share a feature request after testing, you can comment on this post, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see “Where to Report” below.

What to Test

To prepare:

  • Create test accounts at LinkedIn, Tumblr, and Twitter for testing Sharing connections.
  • Have an Author or Subscriber user role setup for at least one test site.
  • Add some files to a WordPress.com test site and click to download them while logged out to generate some stats for testing the new File Downloads section in Stats.
  • Set up a Jetpack site for testing if you don’t already have one. You can use jurassic.ninja to quickly create a Jetpack testing site.
  • Go to My Site > Settings > Use Block Editor to enable the block editor for new posts.

To test:

  1. 10362 Go to My Site and make sure the new quick action buttons work. Check that tapping on Site Name or URL opens site preview. Log in to a test site as an author or subscriber role and note that the Pages button is not there.
  2. 10378 Go to My Site > Sharing and connect a LinkedIn, Tumblr, and Twitter account then make sure sharing works as expected. If you already had any connected, disconnect and reconnect them.
  3. 10276 Go to My Site > Blog Posts, select Everyone in the author filter, check that both list view and cards view (icon at top right) show an author name. Select Me in the author filter and check that the author name is not shown.
  4. 10411 From a WordPress.com site, go to My Site > Stats > Days/Weeks/Months/Years and scroll until you see the File Downloads card. Does everything look good? Are the numbers correct? Repeat the test from a Jetpack site and check that the File Downloads card is not there.
  5. 10425 Go to Profile and check that the following notice appears, “Notification Settings can now be found in the Notifications tab.” Find the Notification Settings in the Notifications tab and make sure they work as expected.
  6. Block Editor: create and publish post using all of the available blocks (Paragraph, Heading, Image, Lists, Separator, Page Break, Quote, More) and check that each one works as expected.

You can find more details about all of the updates for this release in the related PRs targeting WordPress-Android 13.2 and gutenberg-mobile 1.11.

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.

Thanks for testing! ❤️

#13-2, #android, #call-for-testing, #mobile

Call for Testing: WordPress for Android 13.1

WordPress for Android version 13.1-rc-1 is available for testing on the Beta 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-13.1-rc-1-universal.apk from here.

Bugs & Feedback

If you find a bug or want to share a feature request after testing, you can comment on this post, ping one of us in the #mobile room on WordPress.org Slack, or head straight GitHub and open an issue—please see “Where to Report” below.

What to Test

To prepare:

  1. Have a publicly accessible Facebook page available, or create one, to use for testing.
  2. Go to My Site > Settings > Use Block Editor to enable the block editor for new posts.

To test:

  1. Go to View Site or My Site > Blog Posts > View to preview content and use the icon at bottom right to change to a desktop view and back again. (10326)
  2. Go to My Site > Sharing > Facebook > Connect and add a published Facebook page. (10376)
  3. Block Editor: create and publish post using all of the available blocks (Paragraph, Heading, Image, Video, Lists, Separator, Page Break, Quote, More) and check that each one works as expected.

You can more details about updates to version 13.1 in the related PRs targeting WordPress-Android 13.1 and gutenberg-mobile 1.10.

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.

Thanks for testing! ❤️

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