It’s important to have a good testing plan before releasing a new version of an app. The apps are currently released to beta testers for 2 weeks before being submitted to the respective app store.
Want to help by testing the apps? Here’s how to get the beta versions:
- Join the Android beta program with the “Become a tester” button. Let us know in the #mobile channel on WordPress Slack if the beta program is full.
- Sign up for the iOS TestFlight program (open the link on your iPhone or iPad).
Calls for Testing
Calls for testing each app release are posted on the Make WordPress Mobile blog. To join in testing, you can follow the instructions in the latest call for testing and report any issues you find.
Want to help post calls for testing? Let us know in Slack! Here’s what to include in a call for testing post:
- App version number
- Release date (deadline for testing feedback)
- How to join the beta
- Release notes (“What to Test”)
- Focus on new features or enhancements.
- Include bug fixes if they require specific testing (e.g. a risky fix with potential regressions not covered with automated tests).
- Include brief testing instructions that explain any required setup, where in the app to test (without using feature codenames), and what testing scenarios are relevant (device types, site types, user roles, or other testing considerations).
- Link to each feature/bug fix PR for additional context.
- Include a link to the release milestone for testers who want to see the full list of changes.
- Where to report bugs and feedback
After publishing a call for testing, be sure to monitor the comments for testing feedback. Make sure every comment receives a reply and appropriate action. You can move the feedback to a GitHub issue or ping someone in the #mobile channel in Slack to discuss it further.