The Agile software development approach has replaced the traditional testing strategy based on product risk analysis with the delivery of test effort based on sprint impact. As a result, (automated) tests are often focused on a small piece of functionality with the smallest result being the unit test. However, these tests can hardly ever be used as building blocks for functional tests.
With MTA’s test capabilities we break this impasse, because the principle behind MTA is based on a building block approach. Unit tests form the basis for component tests which in turn are aggregated into process tests. Because you can configure multiple applications simultaneously in an MTA test configuration, you can define process tests even across multiple microservices (applications).
Request a demo to see how MTA supports these test levels
Shift left testing shifts testing activities to the beginning of the development process. This provides great effectiveness and cost savings because errors are discovered early. MTA focuses on the discovery of functional and integration errors. MTA supports shift left test capabilities by:
Testing techniques focus on identifying and capturing test conditions, test cases, and test data. MTA supports a number of standard testing techniques:
Enter your information and choose a day and time when you would like to receive the demo (1,5 hrs).