Testing Team

What is a Test Team and why is it ideal to use?

A Test Team is designed to support the software development life cycle by emulating a Project Team to test a Solution version before deployment. It allows users to streamline the user acceptance testing (UAT) process as relevant users can be assigned as members to test the Solution. The Solution Widgets, Dashboard and Scheduled Tasks are also transferred over to display data and trigger actions respectively. Automated emails and e-signatures can also be tested via the Test Team.

Ideally, users will first test a Solution version via a Test Team before publishing and/or deploying to a Project Team. Users can assign relevant members to both Test Teams and Project Teams. However, typically Test Teams will only include a small portion of users as testers to receive feedback before publishing and deploying to a Project Team assigned with all relevant users.

 

What are the differences between Test Teams and Project Teams?

Features	Test Teams	Project Teams
Solution Widgets/Dashboards/Scheduled Tasks	Yes	Yes
Custom Widgets/Dashboards/Scheduled Tasks	No	Yes
Team Members	Yes	Yes
App-level Permissions	Yes	Yes
Watermark	Yes ("[TESTING TEAM]" label in red is displayed on all pages including the Preview mode in App Studio)	No
Access Control (Permissions)	Must be either a Solution Owner or Solution Author to access the Test Team. Having the "Manage All Project Teams" account-level permission does not grant access to Test Teams.	User must be the Team Owner or Member of the Project Team or have the "Manage All Project Teams" account-level permission to access a Project Team.

 

How to test a Solution version in a Test Team

Test Teams are not associated with Project Teams and must be created from the Solution. Follow the instructions below:

1. Navigate to the Solution you wish to test
   
   
2. On the left panel, go to the "Versions & Publishing" tab
   
   
3. In the "Actions" column of the table, click onto the 3 dotted icon for the Solution version you want to test
   
   
4. Click on the "Test this version" option
   
   
5. Confirm you are looking to test the correct version
   
   Note: Test Teams will inherit the Solution name with an added "(Testing)" label. Test Teams can be found via the Project Teams listing page in the "Test Teams" tab or in the suggested options when hovering over "PROJECT TEAMS" in the navigation bar if it is a recently accessed Test Team
   
   Alternatively:

1. Navigate to the Solution you wish to test
   
   
2. On the top left of the left panel of the Solution, using the "Currently viewing" dropdown, select the version you wish to test
   
   
3. Click onto the "Test this Version" tab
   
   
4. Confirm you are looking to test the correct version

If a Test Team has already been created via the above steps, users can also click onto the newly appeared "TEST NOW" button in the Versions & Publishing tab of the Solution to test the current testing version.

 

How to add testers to a Test Team

Similar to a Project Team, you will add members to your Test Team. However, it is recommended that only a small portion of users are added as members to your Test Team in the form of testers. Follow the instructions below:

1. Navigate to the Test Team you wish to add users to
   
   
2. On the left panel, go to the "Team Members" tab
   
   
3. Click on the "+ ADD MEMBERS" button
   
   
4. Select the users you wish to add as testers in your Test Team
   
   
5. Configure the role of the testers in your Test Team

It is also recommended to set up the role and member specific permissions at an App level just as you would set this up in a Project Team when the Solution is published and/or deployed. Follow the next set of steps to do this.

 

How to set permissions for users on an App level

Permissions can be applied to members of a Test Team at an App level in the same way as Project Teams. Permissions can either be role-based or user-specific.

1. Navigate to the Test Team you wish to set permissions for your users at an App level
   
   
2. Click onto the App you wish to set user permissions on
   
   
3. Click onto the "Permissions" tab
   
   Role Based Permissions:
4. In the first table of the page, change the default role-based permissions via the 3 dotted icon under the "Actions" column for the "Members" row.
   
   Note: The role-based permissions configured will be applied to all users with that role.
   
   Member-Specific Permissions:
5. In the second table of the page, click onto "+ ADD" to add existing Members of the Project Team who you want to create a custom permission configuration for
   
   
6. Change the member-specific permissions via the 3 dotted icon under the "Actions" column for the specific member's row.
   
   Note: The member-specific permissions configured will only be applied to the particular user.