Most visual components can be defined by simple drag and drop operations. Reusing the defined objects is intuitive. For more complicated components, Identifying windows and window components is flexible and powerful. Complicated test steps can be defined and reused, particularly helpful for test setup. Adding functionality to visual object classes has helped us extend features of AscentialTest. The most valuable feature of AscentialTest for us is that it fully supports PowerBuilder Product support is amazing. AscentialTest is not an easy tool to master but the patient and helpful support provided what I needed to get everything done and continues to be an essential and reliable resource.

It’s the UA server engine which allows us to work on embedded IE and Desktop based applications simultaneously. As ours is a healthcare application identifying the smallest icon in the scanned image was of significance which was resolved using render image concept which was very easy to implement. We have been using AscentialTest from past 7 years and developed around 2k tests and each test takes around 8 minutes to execute. Host Target Model allowed us to run tests in parallel which made Smoke and Regression test smoother. Maintenance of these suites have been efficient with the snapshot technology resolving most of the object issues at ease. This has allowed us to finish the regression within the sprint everytime. The Customer support was at its best from both Matrysoft and Zeenyx.

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!