Who is this article for?

Enterprise or Decani administrators and users who want to know about mobile beta feature testing.

Active mobile application is required.

Beta testing allows you to validate mobile functionality before changes are released to production. Unlike desktop applications, which use a User Acceptance Testing (UAT) environment, mobile testing uses preproduction builds of the application.

This article helps you prepare for mobile updates.

Testing basics

The goal of beta testing is to identify issues before release to production and provide actionable feedback to development teams.

Beta testing validates:

• Mobile device management (MDM) tools
• Single-sign-on (SSO)
• Devices (models, generations, settings and OS versions)
• Custom application behaviors

Testing types

There are two main testing types:

• Structured - Follow predefined test scripts to validate specific functionality. These scripts may be created by Ideagen or by your organization.
• Unstructured - Perform typical day-to-day tasks to identify issues in real-world usage.

Testing scenarios

We recommend testing for unexpected behaviors. We're listing some examples to get you started.

Submit records with incomplete required fields

To test this scenario:

1. Partially complete a record. 
2. Switch to another application.
3. Return and complete the submission.

Test input limits and validation

To test this scenario:

• Upload excessively large or small images, or omit images entirely 
• Exceed character limits 
• Enter special characters

Taking part in testing

Any user can participate in beta testing. For additional information, see enabling beta features.

Mobile testing applications

iOS (Apple)

TestFlight is Apple’s beta testing platform for iOS devices.

Requesting access

Request support or contact your account manager. Include the tester’s Apple ID. An invitation email will be sent after approval (check spam folders if not received).

Installing TestFlight

To install TestFlight:

1. Open the invitation email on the test device.
2. Click View in TestFlight.
3. Open TestFlight.
4. Tap Redeem.
5. Enter the invitation Code.
6. Locate the application in the list.
7. Tap Install.

The testing application icon looks just like the mobile application

The TestFlight version of the mobile application looks nearly identical to production, with the exception of a small yellow indicator.

Verify by comparing the application version number with the version listed in the release notes documentation. See Enterprise and Decani mobile release notes.

For additional information visit Beta testing made simple with TestFlight.

Unenrolling

Uninstall the TestFlight application version and install the production version from the App Store.

Android

Android beta testing is managed through the Google Play Store.

Requesting access

Request support or contact your account manager. Include the testers Google Account username. An invitation email will be sent after approval (check spam folders if not received).

Installing the beta version

Once enrolled, install the application from the Google Play Store. The beta version will display a visible “Beta” indicator.    If the application is not visible:

• Force quit or stop the Google Play app

• Clear cache and application data for Google Play app

Unenrolling

Unenroll from the beta program by signing into the Google Play store with a different account. If a test Google account was used when enrolling in beta testing, then the tester simply needs to log into the Google Play store with their normal Google account.

Important

We highly recommend that Android beta testers create a new Google account specific for beta testing that is separate from any other Google accounts to simplify the process if the tester decides to no longer be a tester.

Windows

We periodically distribute beta test builds for manual installation via sideloading. These releases are made available to customers on a case-by-case basis.

Sending testing logs

When reporting issues, include logs from the mobile device. You can access these in debug mode.

To send us your testing logs:

1. Open the app.
2. Quickly tap the Ideagen logo seven times in one of the following locations:
   • first step of the welcome page
   • login page
   • left navigation sidebar
3. A confirmation message will appear if you enabled debug mode successfully.
4. Tap the Bug icon.
5. Tap Zip Logs or Open Log.
6. Save the log.
7. Attach the most recent log to the ticket.

To exit debug mode, tap the logo seven times again. 

Frequently asked questions

Who should be a beta tester?

Administrators or frequent mobile users are recommended.

Should IT be informed?

Yes. IT and security teams may need to adjust configurations to support testing.

How are new release versions announced?

Notifications are published via the Technical Blog. Ideagen recommends subscribing.

Will the testing application update automatically?

Automatic updates depend on device settings.

Where should testing occur?

Testing should be performed in UAT. Testing applications may connect to production environments. Connect with caution.

Can the testing application be used in production?

Yes, for standard daily tasks.

Can both beta and production versions be installed?

No.

How do I stop being a tester?

Follow the unenrollment steps for your platform.

How do I report issues?

Submit a ticket and include:

• Description of the issue
• Steps to reproduce
• Application version
• Device type and OS
• Logs