To begin recording a test, you should first clear out the database so that it is empty and then add in the records that you need to run that test. Because of space limitations (the database is stored in the test itself), please limit the number of records you create for the test.

To clear out the database click on the “ TEST – Clear Database ” action. You will have to accept a couple of warnings so you don't click this type of thing accidentally. 

Once the database is cleared out you can begin adding your records. You do this BEFORE recording. When you hit the action to start recording WorkflowFirst will take a snapshot of all of the records in the database that you added. 

Before you start recording, first plan what it is you want to test.

 • Consider what data you will need for your test, and think about the values you will use.

 • Consider any operation that raises events or has calculated fields that will need testing.

 • Think of reports that you can run, and what kind of data you will expect to see in the report.

 • Also consider cases of deleting records and re-running reports to see how things change.

 • If possible don't perform any actions that require email interaction, such as approval workflow or document review. If human interaction is required the test won't be able to be run automatically.

 • It shouldn't matter if notification emails are sent, however. Make sure people are aware that the notification is just a test (you can usually do this by changing the system's application title (in the target server entry's advanced / override title option), as this is incorporated into the email from line).

Planning these things ahead of time makes the testing easier to perform.

When you are ready, click 'TEST – Start Recording'. You don't have to enter a name at this point. 

Note : It doesn't matter how long you take to run the test, when the test runs it executes everything as fast as it can, regardless of how long it originally took to be entered. 

You'll then see an indication that your actions are being recorded through a caption at the top of the screen: 

• | Recording : You are currently recording a test case. Click Stop Recording to stop and save the current test case. 

 This indicator will remain on the screen for as long as the recording is active. When you finish recording it will hide.

At this point you're free to do whatever you please in the application. You can insert records, change records, delete records. Also don't forget to perform actins that you know will fail as this is part of the test: If it doesn't display an error when the test is re-run then the test will fail.

Note, though, that only database changes will be recorded. Other operations, like viewing lists or running searches, won't be recorded or verified in the test case.

When you're done recording, click “TEST – Stop Recording”.

This is where you enter the title of your test. For example if you were testing the totaling of invoices, then enter 'Invoice Totaling Test' in the title. You can also create test groups in a hierarchy, using the 'Test' tab, and select the group in which the test will reside in the 'Group to Store' dropdown. 

Once you submit that, the red indication at the top of the screen will disappear and you will be able to continue using the application without any further recording. The test will now be available to run.