Testing your changes
How to test changes before releasing them into production
Last updated
Was this helpful?
How to test changes before releasing them into production
Last updated
Was this helpful?
The Test page can be launched from the main menu:
The Test 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 Script Test 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:
User – logon username
Tenant name/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
Test Changes – if checked, the Script set being run will include any Scripts set as ‘Test’
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.
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.
When a Topic is set to Test mode, e.g.
you will see the warning icon against the script in Admin Tool's Navigation pane:
