# Testing

It may help to esure the Poller we created is turned off (Active set to 'false') whilst conducting these tests and to manually execute it as required (this can still be done even if the Poller is inactive). This is so that we don't have to wait for the Poller to run, but rather manually activate it when needed by clicking 'Execute Now'.

To turn off the Poller, in the **Unifi Integration Designer** window, navigate to the **'Pollers' icon** & set **Active** to **false**. *(If you've created this Multiple Message Poller by editing the previously configured Update Poller, it may already be inactive.)*

![](https://605238050-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MfhoOiA7Ao1-luN_BsP%2F-MfhrmIu51Fh5vrhWLo4%2FIMMPG%20-%20Testing%201.png?alt=media\&token=858fc2dc-3734-4e88-b97a-b3acc9d02c45)

Our Poll Processor has been configured to poll for updates from our PDI and make a decision, telling Unifi which Message to use to process that data. We will therefore test our poller by means of testing both of the inbound Messages on our Integration:

* UpdateIncidentInbound
* ResolveIncidentInbound

We will look in more detail at the steps for each over the next couple of pages.

First, we shall test the **UpdateIncidentInbound** Message.

{% content-ref url="testing/test-updateincidentinbound" %}
[test-updateincidentinbound](https://docs.sharelogic.com/unifi/3.1/integration-guides/incident-multiple-message-poller-guide/testing/test-updateincidentinbound)
{% endcontent-ref %}

{% content-ref url="testing/test-resolveincidentinbound" %}
[test-resolveincidentinbound](https://docs.sharelogic.com/unifi/3.1/integration-guides/incident-multiple-message-poller-guide/testing/test-resolveincidentinbound)
{% endcontent-ref %}