Array
(
)

Step-by-step plan for using MTA

MTA supports the collaboration between testers and developers in the testing process, because they need each other. We do this optimally if you adhere to the following step-by-step plan:

Step 1: Define tests

In MTA, you can define the tests you want to run without automating them immediately. This allows testers and other users to define what needs to be tested without having technical knowledge. These test cases can be used as input for automation in MTA.

See how this works? Request a demo
Test-design-with-manual-test-case

Step 3: Determine test data variation

Once the process to be tested is working properly, the input data can be varied. In MTA you can very easily determine which data should be varied. All variations are in a clear table, so you always have an overview of the input data for the different test cases. For the input of the test data variation no knowledge of the Mendix platform is required, but knowledge of the necessary data variation for a good test coverage is required.

Want to know more about data variation? Request demo
Support-data-driven-testing

Step 5: Execute tests

MTA runs the automated tests at the touch of a button or through a fully automated process on a CI/CD street. Once the tests are completed, the results are available in MTA.

Testresults-of-the-test-configuration

Step 7: Integrate MTA into your CI/CD pipeline

In MTA you can define what has to be tested via the CI/CD pipeline. You can then specify via your CI/CD pipeline when that should happen and what the consequence of errors found should be.

computerscreen men working

Discover the benefits of Menditect Test Automation for your Mendix application

Software menditect interface

Want to try MTA for yourself? You can!

Contact us for a demo. Also for Mendix partners.

Menu