You want to be sure that the quality of every release of your Mendix application is good. You’re considering the use of test automation, but you’re unsure if it fits in with Mendix projects. Read more to know why test automation with MTA does deliver the speed, simplicity and control you know from Mendix.
Frequent and fast delivery of applications is only possible if all steps in the chain are equally fast. Mendix speeds up your development process, but not testing. As a result, testing is increasingly becoming a bottleneck in the rapid delivery of new functionalities.
MTA ensures that the delivery of Mendix applications is no longer delayed. The set-up and maintenance of test scripts in MTA is so simple that developers can test software versions in between (shift left testing) without loss of time.
The direct execution of tests on the Mendix models ensures a lightning fast test execution. No screen or browser interaction is needed with MTA. Finally MTA integrates seamlessly with your CI/CD pipeline.
Request demo
Agile development makes regression testing necessary to ensure that the quality of an application is maintained. New versions of the Mendix platform also need to be tested again. You have to check with each release whether the existing test automation is still working properly. This takes a lot of time that you would rather spend on development of new functionality.
MTA automatically checks if the existing test automation still matches the application to be tested (consistency checking). Any problems are detected and shown so they can easily be adjusted. Also no scripts need to be made for new functionalities, because all building blocks from the adjusted Mendix model are immediately available for testing.
Read more about MTA features
Test automation requires additional knowledge of testing tools and scripting languages in your Mendix team.
MTA is a completely no-code test solution that requires no scripting language to be learned and which a Mendix developer can use to automate tests without having to learn about a new technology.
MTA is quick to learn for test automators and testers without Mendix experience. The knowledge level required is only Mendix rapid developer.
Experience the ease of use of MTA in a demo
Test tools that test via screens usually cannot automate microservices testing. This limits the coverage of tests that can be performed to the verification of a single application.
MTA supports the simultaneous test execution of multiple Mendix apps. Any configured app can be called from any test case. This makes it easy to test business processes across a landscape of Mendix microservices. External systems that are linked to your Mendix application can also be tested or set up in MTA as a stub.
Want to know more?
An automated test needs testdata to be executed. When Mendix models change, not only do the test cases change but the test data must change with them. This often takes a lot of effort.
MTA makes it possible to specify in a clear way which data will be varied. Each data element is automatically checked for the data type defined in the Mendix model, so wrong input is not possible. For each data variant the expected outcome can be specified (assert). The latter makes it very easy to test multiple test cases with exactly defined outcomes in one test run.
Visit our demo to see how testdata is maintained in MTA
A Mendix application needs different test automation tools for each level of test automation (unit, component, process). Because of this, in a Mendix project multiple test technologies have to be maintained both in terms of knowledge and infrastructure and test sets are distributed over multiple systems.
In MTA both unit, component and process tests can be configured. MTA thus limits the number of test tools needed and makes the management of test sets easier and cheaper.
More information about the test capabilities of MTA
Setting up test automation requires a large upfront investment and requires maintenance throughout the lifecycle of an application. Many Mendix projects start small and grow in size and complexity step by step. Because of the high upfront investment, test automation is often not, or too late, deployed for Mendix applications.
MTA asks for a low investment because of the pay-per-use model and lowers the maintenance costs because test automation can be maintained easily and quickly in the Mendix team without using extra knowledge for this.
MTA supports multiple test levels (unit, component, process) making test coverage high. This reduces the chance of costly errors in production software and fewer failures occur.
Please contact us to know how we can help you to save costs
In Mendix projects, screen testing techniques are used for regression testing. This is costly, maintenance and error prone.
With MTA, all test levels, from unit to process test are covered in a maintenance-friendly and fault-tolerant way.
If you use MTA in combination with screen testing you can minimize screen testing and use it only for testing screen flow, visibility of buttons and fields and correct selection of data in screens.
The coverage of your regression tests is high with MTA, without unnecessarily high maintenance costs of screen tests.
Learn more about MTA in our demo
With MTA it is possible to build tests from the smallest building blocks (units) to complete end-to-end process tests in a microservices landscape.
This is possible because in MTA you can connect unit tests together to form component tests and component tests together again to form process tests. The process tests of different applications can be linked into one integrated microservice test.
This way you can build your tests under architecture and maximize test reuse without sacrificing test coverage and your development budget.
Test capabilities
| info@menditect.com | |
| +3185 - 4010494 | |
| KvK: 82975795 | |
| Follow us on LinkedIn |
Enter your information and choose a day and time when you would like to receive the demo (1,5 hrs).