Device and testing best practices

Review these best practices before running tests to keep devices available, protect sensitive data, and avoid common issues. To learn more about hybrid clouds, see Hybrid clouds | Configure and connect devices.

Training and resources

• Perfecto Getting started documentation

• Network-related guidance:

  • Best network practices (generic)

  • Hybrid clouds | Best network practices

• Perfecto Education (self‑paced courses)

• Perfecto Customer Handbook

Device credentials

Perfecto requires known passcodes and consistent device credentials to maintain device availability.

• Use only the standard passcodes provided for your cloud, typically one of the following:

  • 123456

  • 111111

  • 000000

• Do not set custom passcodes. Changing a device passcode makes the device inaccessible to Perfecto and removes it from the cloud until corrected.

• If a passcode is unknown, review the device’s most recent test report to identify the last successful user and request the passcode. If it cannot be recovered, contact Perfecto Support.

• Only Perfecto administrators should add or modify iCloud, Google, or Samsung accounts. Personal accounts must not be used.

• If you do not know the device passcode, contact Perfecto Support before taking any further action. A factory reset may be possible when credentials are not configured. If manufacturer credentials exist but are unknown, the device cannot be recovered and may require replacement.

Avoid device bricks

A device becomes permanently unusable (“bricked”) when:

• A non‑standard passcode is set and cannot be recovered

• Manufacturer account credentials are present but unknown

To avoid this:

• Use only the standard passcodes for your cloud

• Do not sign in with personal Apple ID, Google, or Samsung accounts

• Ensure only designated administrators manage cloud‑wide credentials

• Contact Perfecto Support before attempting corrective actions

Protect sensitive information

Use Secure Text when entering passwords or other sensitive values during testing.

• Activate the Secure widget before entering credentials.

• Text entered through Secure Text is masked in test reports.

• Text entered without Secure Text is visible to all users with access to reports.

Efficiency practices

Improve test efficiency and reduce device handling time by:

• Using toolbar shortcuts to launch and close applications

• Using copy and paste for credentials and URLs

• Refreshing the device browser if loading exceeds ~15 seconds

• Uploading APK/IPA files to the repository instead of installing from a local machine

• Selecting Resign when installing iOS apps to ensure certificates are trusted

• If resigning is not supported, provide a version signed with a pre‑trusted certificate

• Ensuring devices are placed in the appropriate groups for password auto‑logout behavior

Manual testing conventions

Use consistent reporting conventions to improve analysis and debugging.

• Name tests descriptively. Avoid generic names such as “Interactive Session.”

• Insert checkpoints after significant actions (for example, BrowserOpened, ItemsAddedToCart).

• Create custom views in the Report Library to quickly locate your own tests.

  • Apply filters for date range and owner.

  • Save the view for reuse.

Support case severity

When opening a support case, choose a severity that reflects the business or testing impact. Severity definitions and expected response times are defined in the official Perfecto Support Terms.