Array
(
)
Request demo

Why MTA?

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

Test different with “Direct model testing”

Menditects “Direct Model Testing”  differs from other testtools because it uses the backend elements (object actions and microflows) from a Mendix app to  define your tests. This approach allows you to

  • test on multiple levels in one tool
  • integrate test automation with Mendix development
  • create tests withouth test code in your Mendix app

 

“Menditect is the only testtool in the market that can execute Mendix microflows directly without having to mainain test code in your app!”

 

Request a demo to see “Direct Model Testing” in action
Direct model testing with MTA

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

Why should I convert to MTA?

You should convert your existing test automation to MTA if you want to:

  • Embrace collaboration between testers and developers to increase the quality of your Mendix apps
  • Save money and time and rely less on (external and scarce) test automation specialists.
  • Setup and maintain both unit, component and process testing in one tool. This saves time and keeps the test automation knowledge in your Mendix team
  • No need to adapt your testscripts for new versions of Mendix (which is needed for screen testing).
  • Benefit from continuous innovation and support all versions of Mendix.
Convert to MTA

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
Markus Travaille

Want to experience how MTA works?

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

Footer contact ENG

  • This field is for validation purposes and should be left unchanged.
  • Menditect
  • Databankweg 12G
  • 3821 AL Amersfoort
    The Netherlands
info@menditect.com
+3185 - 4010494
  KvK: 82975795
   
Volg ons op LinkedIn
Privacy statement End user licence agreement Service Level Agreement
Design & development: TeamCreative

Menu

Request a free demo directly

Enter your information and choose a day and time when you would like to receive the demo (1,5 hrs).