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:
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
The test cases that need to be automated must be built with test steps that perform specific tasks (calling a microflow or CRUD) action. All microflows and enitities from the Mendix model are immediately available and can be selected. The output of a test step can be used as input for a test step in the same test case or in test cases in the same test suite. Automating the test cases does require some knowledge of the Mendix platform from a tester, but is very easy for a Mendix developer to do.
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
For each test case (and data variation), the expected result must be determined. For this purpose, checks (asserts) can be configured in MTA. These checks can be on the end result, but also on intermediate results so it’s easy to check where a possible error occurred in the test script. Implementing controls does not require knowledge of the Mendix platform, but it does require knowing what result the application should deliver, given a certain input. Setting up good test coverage is very important here.
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.
Based on the results of the test performed, either the test script must be modified, the data entered or the application being tested. When initially setting up the test case the emphasis will be on the first two things. Once a test case is working properly it will only go wrong if the software contains errors. Analysis of the test results is a joint effort between developers and testers.
Request demo and experience how MTA works
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.
| 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).