# Testing

If active, 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 it off, in **Unifi Integration Designer**, click the **'Pollers' icon**, locate the Parent Update Poller & set **Active** to **false**.

![](/files/-MgusglxkilfepIi4JwI)

If you have edited the Connection, Poll Processors & Outbound Message Paths and because 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, it will be necessary to test, utilising all the previously configured Messages, along with the new one. The Message Scenarios we shall be testing are:

* CreateIncident
* UpdateIncident
* ResolveIncident
* CreateIncidentInbound
* UpdateIncidentInbound
* ResolveIncidentInbound
* AddAttachmentInbound

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

{% hint style="info" %}
If you have not editied the Connection, Poll Processors & Outbound Message Paths (because they were already configured with the `/table/incident` element in the Poll Processors & Outbound Message Paths), then you may not need to test the Outbound Scenarios.  This is because they would have already been tested as configured when following the Outbound Incident Guide.

However, because the codebase hase been edited in the Response Script of the 'Unifi - SN REST Poller Single Incident with Attachments' Poll Processor, all the Inbound Messages should be tested.

*(You will need to create some bonded tickets in the remote system - whether created outbound or inbound - in order to facilitate testing the Inbound Messages.)*
{% endhint %}

First, we shall **test** the **Outbound Scenarios**.

{% content-ref url="/pages/-MRVw3ryB\_B5K8IGHxfK" %}
[Test Outbound Scenarios](/unifi/3.1/integration-guides/incident-attachment-poller-guide/testing/test-outbound-scenarios.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MRWWdWd-2IEL7kNmWPX" %}
[Test CreateIncidentInbound](/unifi/3.1/integration-guides/incident-attachment-poller-guide/testing/test-createincidentinbound.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MRW\_dQMH66zLcXSedDk" %}
[Test UpdateIncidentInbound](/unifi/3.1/integration-guides/incident-attachment-poller-guide/testing/test-updateincidentinbound.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MRWdyTLpfln5mnKqBsU" %}
[Test ResolveIncidentInbound](/unifi/3.1/integration-guides/incident-attachment-poller-guide/testing/test-resolveincidentinbound.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MRWh2Lw04SJKX42T9uU" %}
[Test AddAttachmentInbound](/unifi/3.1/integration-guides/incident-attachment-poller-guide/testing/test-addattachmentinbound.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sharelogic.com/unifi/3.1/integration-guides/incident-attachment-poller-guide/testing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.