---
description: >-
  You should have successfully configured two Poll Processors and two Pollers -
  to enable polling data from your PDI & passing the relevant data between them
  and then passing it to Unifi.  Now to test.
---

# Testing

It may help to turn off the Parent Update Poller we created (set Active 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**.

![](https://796541950-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MRRCpoWKJnUmfL7aoVp%2F-MRRELZB8pxnwFSVs8YN%2FV2%20-%20Testing%201.png?alt=media\&token=b26b2d91-580c-4e13-80f9-b01cdfdba923)

Our Poll Processors have 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 Update type 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](testing/test-updateincidentinbound)
{% endcontent-ref %}

{% content-ref url="testing/test-resolveincidentinbound" %}
[test-resolveincidentinbound](testing/test-resolveincidentinbound)
{% endcontent-ref %}

