In this blog we provide more insight in how the “shift left testing approach” can help you keep up high quality in combination with high delivery speed.
Below there are two definitions of shift left testing that are similar, but also emphasize different aspects of shift left testing,
Shift left testing:
Shift left testing Mendix is about changing your Mendix development process; moving test activities “to the left”. It is also about collaboration between testers and developers.
At its core “shift left testing” is, just like agile development and DevOps, about behavioral change. Changing the behavior of people is not easy. However, if the change process is supported by the right tools it can support this change process and make it easier.
Mendix provides the tools for a faster development process by bringing design and coding together. Menditect adds test automation to the Mendix platform and enables testers and developers to collaborate in one tool.
Shift left testing:
Shift left testing stimulates developers and testers to interact frequently and early in the development process. How could this work in a Mendix team? Below we describe three types of testing activities where developers and testers can work together during the development process.
Testing of single microflows (units):
Test Data generation & maintenance:
As described above, shift left testing is a joint effort between testers and developers and should be supported by test tool(s) that allow you to:
With the upcoming release of MTA 2.0 in january, Menditect will make another step in supporting shift left testing of Mendix apps. It will provide the ability to test locally and on virtual machines and makes it easier for testers and developers to collaborate. Please follow our announcements on our website and LinkedIn for the latest information.
Enter your information and choose a day and time when you would like to receive the demo (1,5 hrs).