> For the complete documentation index, see [llms.txt](https://docs.keyfax.biz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keyfax.biz/product-suite/admin/script-editing/testing-your-changes.md).

# Testing your changes

{% embed url="<https://youtu.be/3guDrG-Q2Dg>" %}

The Test Container page can be launched from the main menu:

<figure><img src="/files/QdRhQa1RzhaEF8tdhNe1" alt=""><figcaption></figcaption></figure>

The Test Container page provides access to a screen for launching Scripts and testing their operation prior to release to Operators. Some Scripts will have been set up to operate only as ‘test’ Scripts and are only accessed via this facility.

The Test page has some different features depending on whether it is run from Diagnostic Scripts or Enquiry Scripts.

The Script Test page goes some way to emulate data that echoes what is passed to Keyfax from a host system in the Startup (XML) data file. This may vary between installations/configuration but for Repairs this comprises:

* **Restart Script** - option to restart the test container at any point, negating the need to close and re-launch the test container
* **Clear Cache** - option to clear cached memory at any point, allowing users to see script changes without having to close and reopen the test container
* **User** – logon username
* **TenantText** - the Tenant name and address
* **Property or Tenant ID** – reference held in host system
* **Asset ID** – reference held in host system, not always provided and may be same as property /tenant ID
* **Tenancy Type** – code denoting service or client group and links to Script Set code
* **Repairs No** - the Script Test allows for a Repairs Number to be passed
* **Return to address** - a pre-configured URL to return the user to specific pages upon completion or cancellation of a script&#x20;
* **Test Changes** – if checked, the Script set being run will include any Scripts set as ‘Test’ mode. See screen shot below

The Test page for Enquiries includes two additional fields as below:

* **LAID** - the Local Authority ID held in the host system
* **Scheme** - Reference held in the host system

The Script Test allows these elements to be changed to test the effect of such changes as well as, most importantly, to allow testing of Script's functionality.

To launch the Scripts, select the appropriate settings and click on Submit. Scripts will then appear and can be run to replicate the Operators actions.

<figure><img src="/files/uQC0EZmAUM36j4CGTiBt" alt=""><figcaption><p>Test Container for Repairs Diagnostics including Scripts in Test mode</p></figcaption></figure>

On completion of a Script, after the final Submit, the Scripts will generate an export data document (XML, although JSON can also be returned). The details of this file are displayed back in the Script Test tab.

<figure><img src="/files/dSApY2qOwm0yeGy6Pf2I" alt=""><figcaption><p>Test page export XML for Repairs Diagnostics</p></figcaption></figure>

### Flagging up Test Topics

When a Topic is set to Test mode, e.g.&#x20;

<div align="center"><figure><img src="/files/UPqpQh9ZZwOdOFHpsUOY" alt=""><figcaption><p>The Test mode</p></figcaption></figure></div>

you will see the warning icon against the script in Admin Tool's Navigation pane:

<div align="center"><figure><img src="/files/PLFfPrwbfwMFKTmUGEAA" alt=""><figcaption><p>Spot the Test script!</p></figcaption></figure></div>