The testing system is integrated into the resultant WorkflowFirst application, after it is published. However it's not available in every application – only applications that have a Server Type of “Testing (Enhanced)”. This means the system is enhanced to provide testing capability. 

To enable this, go to your Application record in WorkflowFirst. Then go to the Servers drilldown. Create a new Server entry for your testing system. You can also copy and paste your existing Server entry, but make sure: 

1. You give the server entry a suitable name, which should include 'Testing' in the title. 

2. You select 'Testing (Enhanced)' in the Type dropdown. 

3. You change the name of the database. Change the 'Prefix Database Tables' to 'No' and enter a new name into 'Database Name', which should generally include the term 'Testing' for differentiation. 

4. Update the 'URL of App' to have a new port number. The existing port number comes after the host, so whereas it may say http://localhost:8030 you may want to change that to be http://localhost:8031 so that it doesn't interfere with the existing web server instance. 

5. Update the 'Path of App Files' to point to a new folder, but still under the WorkflowFirst's application folder, in the Apps subfolder. The name of the folder should generally match the name of the application, with the addition of 'Testing' for differentiation. 

6. Drill down to 'Advanced' and set the 'Override Title' and 'Override Description' to include the term 'Testing', again for differentiation.'  

Also, remember to include any 'Feature Modules' you have selected in your regular server target, to ensure the same functionality is enabled in both systems.

Once your server is setup, you'll be ready to publish.

To do this, click Publish and select the name of your new server entry from the 'Target' dropdown list:

This will create the application files and start up the web server pointing to your new application.

Initially the application's data will be empty . If it is NOT empty then something is wrong and you must be pointing at an existing database! If so, go back to the bit about editing the server entry and make sure you've set up the database correctly. 

Note : Make especially sure you don't run the “ TEST – Clear Database ” action unless you're absolutely sure you're using the test application's database!