Test Multiple Users on an Experience
When creating experiences, testing using multiple environments is essential. Due to the nature of load-balancing environments across CloudShare infrastructure, testing with many participants is good practice, as this will ensure that participant and customer environments perform as expected in live situations.
Create Separate Email Aliases for Each Role Type Being Tested
For example, when testing how things might look to a participant, log in to CloudShare using an email alias associated only with that participant. Refrain from using a project member's email addresses (which can lead to double logins and inconsistent results). Note that many email systems and services (such as Gmail and Microsoft 365) support the concept of sub-addressing.
Many email systems and services (such as Gmail and Microsoft 365) support sub-addressing (RFC 5233), where random text is added after the user part of an email address to provide multiple email aliases that are all delivered to a single primary inbox. Filters or rules can then be applied based on those addresses. For example:
- user+randomtext1@example.com
- user+randomtext2@example.com
Utilize Multiple Browser Sessions When Logging Into CloudShare Using Multiple Aliases
Using multiple browser sessions is recommended when testing various roles with multiple aliases. This approach enables login to CloudShare with several accounts simultaneously, so that changes can be made as a project member while viewing the results as a participant. This can be achieved either by using an incognito window or by working with separate browsers (for example, Edge, Chrome, or Firefox). Note that Firefox does not support RDP Booster and some session managers.
Test All Regions Where Snapshots Will Be Deployed
Snapshot copying between regions (Miami, Amsterdam, and Singapore) can take time, potentially several hours. Allow enough time for the snapshot process to complete, then test those regions. When using the multi-region feature in Accelerate, it is often preferable to use a VPN with egress to the nearby CloudShare data center.
Ensure Participants Run Connectivity Checks to the Region(s) to which They Will Connect
Be aware that the internet may not always be 100% stable. The CloudShare technical Support team (support@cloudshare.com) can assist in testing the internet route to CloudShare remote access proxies and gateways and beyond. Corporate firewalls and proxies can also cause issues for users connecting to their CloudShare environments.
When Configuring Virtual Machines for Public Access, Ensure Awareness of Our Open Port Ranges and Test All External Connections
Specific ports can be whitelisted for a vNIC interface that is configured to use a public address.
Use a “Pre-Flight/Familiarization” Experience
This experience could benefit from a reduced blueprint and a limited policy to help familiarize participants/prospects with CloudShare environments. It will help ensure that they receive the correct instructions and can access the environments, as well as meet our minimum requirements.