We use the tool for several complex Powerbuilder applications. You can set up the Ascential Test test suite entirely in your own way. In the editor you can perform simple test steps on objects that you can simply indicate in a screenshot. On the other hand, you can also automate complete processes and call them in a test with parameters, or for example generate current test data with your own scripts. It is also very useful to save used test data and read it from externally stored .ini files. If you have a little programming knowledge, you can create a script for all kinds of common actions to simplify the construction of a test. For example, writing and reading test data to an .ini file. Or opening or closing a screen, clicking on certain buttons on the screen, etc. Interaction with an external database is also possible to prepare test data, for example.

There are various reporting options, but we prefer to log everything that is important ourselves in the output of the test, again using small scripts. So yes, you can make it as simple or as complicated as you want. Fortunately, there is an extensive help file available.

The Ascential Test interface is very extensive so it is handy to have an extra large screen. And not to forget, the support from Zeenyx is excellent! Review collected by and hosted on G2.com.

It is a bit inconvenient that you cannot debug a test step by step. You will have to comment out test instructions to reach a certain phase in the test. But this is apparently being worked on at Zeenyx. Also managing the screen captures is sometimes a bit difficult if there are many screen captures and you prefer to have as small a collection as possible with all used objects. However, technically it does not matter how many screen captures you have. Also finding specific objects in a screen capture is not always easy, but it does not get in the way of working with the tool.

It is good to know that once the tool is running, the computer can no longer be used for other work, because Ascential Test simulates mouse movements and key strokes. Also, running in the background in a virtual environment does not work well (as far as we have determined) when the hosting workstation is used. It is best to use a dedicated workstation and run the test there. Review collected by and hosted on G2.com.