Why MTA?

Why is MTA different from other test automation tools and what problems does it solve

MTA’s unique capabilities

If you compare MTA to other test tools the main difference are that MTA:

  • executes tests directly based on the Mendix models, therefore it does not need API’s or screens
  • requires no test code in the Mendix apps
  • provides a test framework for process testing in combination with specific capabilities for unit testing
  • can assert any objects because Menditect has access to the Mendix memory and can retrieve all persisted and non persisted objects that need evaluation even if the objects are not shown in screens or available in API’s.


Integrates in your landscape

MTA is specifically made for testing Mendix, therefore it is not a generic testtool. MTA can be integrated with standard CiCd pipelines and testmanagement tools in order to function in a multi platform app environment


Compare MTA to other Mendix test tools
Multiple test levels in one tool

Do you recognize these problems?

Test automation is not always easy and might have its own particular problems. Do you recognize any of these?

  • A bottleneck in delivery of new functionality
  • More maintenance than expected
  • Difficult and requires specialists
  • Does not support end-to-end microservices testing well
  • Maintenance of test data is cumbersome
  • For each test level a separate tool
  • Too expensive
  • Screen based testing provides a too low coverage at too high costs
  • There is overlap in the test sets for the different tools that are used


Read how MTA helps you solve them
testautomation problem

Want to experience how MTA works?

Request a demo or contact us for an appointment with an expert.