community 
We got several questions about the custom error tool and how to properly use it.
To clarify the usage, we created a short tutorial and a test case:
Extract both tests to Tests folder and open Test 64.
The tests were generated on 5.1 patch 4 - available in the download center.
In this test, you enter a folder name to {folder} variable, and an error will occur if a file called "tal.example.zip" is missing from that folder.
If the error will generate, the Error Handler function will be launched and throw a message with the folder name.
Few things to note:
The error step - I used here a custom name error (I didn't select a preset error from the list - I simply typed "Missing File" in the error name.
I also included a description and a parameter.
I will be able to access those after the error occur, when I use lastError.Name, lastError.Description orlastError.Parameters.
Error Handling page in Test 64 -
I created a custom handler that will trigger if the error is "Missing File"
The action will be to launch a EH test.
The EH test expects an IN parameter. I populate it with the error parameter I created.
lastError.Parameters is a 2 columns matrix of the parameters I defined in the Error step.
So I will use as input: {lastError.Parameters('FolderName',1)}
Contributors
