# Activity Testing

## ✅‍ Activity Testing 

To strengthen our QA process, we have the possibility to test the Actions, Action Groups or Translations inside an Activity. This allows us to conduct a final check before sending to players. 

This is the process of sending Actions, Action Groups or Translations from an Activity or Lifecycle to a test user to simulate the player experience.  

### Why Test

We strongly advise to **Quality Assure** Activities and Lifecycles before enabling them. This gives your team the chance to **catch any errors in the set-up or execution before it's too late**. 

Activity Testing is another step in the QA process to be able to check how the player communication content display and translations will appear before it is sent. **Use this to spot any mistakes, styling errors, or translation issues that could have a negative effect on player experience or even incur avoidable business costs**. 

### When to Test

Test Actions, Action Groups, or Translations from inside an Activity or a Lifecycle Activity. This can be done from  any status but we recommend that you use this feature in two main ways:

* **Before QA** - The person setting up the Activity or Lifecycle can test the Actions to be confident they are displaying as intended
* **QA** - The person quality assuring the Activity or Lifecycle can test the Actions to simulate the player experience and double-check the settings before approving

## 👱 Test Users

To test the Actions from within Activities and Lifecycles, we first need to set-up **Test Users**.

You can **create Test Users by using players from within your database.** You can tag these players to be able to use them as testers. 

The **Test Users** need to be created manually and are not related to the FT CRM user already set up your back office. 

{% hint style="info" %}
**Tip**: You need to have the relevant Testing permissions to be able to create Test Users. Access this from **Settings → Users & Permissions.** 
{% endhint %}

Follow the step-by-step tutorial to setting up new **Test Users** [here](https://www.fasttrack-solutions.com/en/resources/knowledge-base/ft-crm/quality-assurance/setting-up-a-test-user).

## 🧪 Testing Activities 

Once you have a **Test User** set-up, you can go ahead and test the Actions of a desired Activity or Lifecycle.  

Start by selecting the **Activity Testing icon** from either the **Action Group**, above a specific **Action**, or from next to an individual **translation**. 

![Activity Test Icon](https://3654650655-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGrxN2ttYCb8JwJc2TS%2F-MShNTezBHj_Ec8nahRY%2F-MShNmTXozOxV4QRF6Un%2FActivity%20Test%20Icon.png?alt=media\&token=29cda798-8e43-4c75-b172-b6cba5c07845)

![Activity Testing](https://3654650655-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGrxN2ttYCb8JwJc2TS%2F-MShNTezBHj_Ec8nahRY%2F-MShNwwMv7vzKsEbtbRU%2FActivity%20Testing%20Image%201.png?alt=media\&token=99b04a73-0301-49e0-a1e5-665f60816a9a)

Once you've selected the **Test User(s)** who should receive the communication, follow the prompts to select the communication profiles that should be sent, if necessary.  

Finally, review the actions that will be fired and **execute the test**. Now, your test user(s) should receive all the selected Actions and Communication Profiles to be able to do a final check before signing-off your work. 

{% hint style="info" %}
**Note**: Your Test User(s) will receive all selected test Actions regardless of the opt-in status, blocks and consents.

Any test Actions will not appear on the Player Timeline.
{% endhint %}

For a more comprehensive tutorial for testing an Activity, [check this out](https://www.fasttrack-solutions.com/en/resources/knowledge-base/ft-crm/quality-assurance/testing-an-activity).