Test automation brings a number of pitfalls that you should avoid. In this page we mention a few that should be avoided as much as possible
Test automation is a domain of its own. There are many different tools, all based on different technologies. There is a good reason for that. The ideal test tool does not exist. Second best is a test tool that your development team can maintain, therefore always look for test tooling that:
Processes are the easiest to understand from an end user perspective. However, process testing with high coverage is an impossible task if you look at the number of variations that can occur in a process. It is better to:
Although in Mendix is is relatively easy to build screens or API’s it is not a good idea to create screens and API’s just for test automation purposes because:
Mendix projects often start small. Because a Mendix team can create new functionality very fast it is possible to create so much functionality that a serious test debt is already present after a few months of development. Avoid this testdebt by:
Enter your information and choose a day and time when you would like to receive the demo (1,5 hrs).