MRA has traditionally done a lot of manual testing to deliver code changes in their existing on-premise solution. The time spend for testing was in many situations under-estimated and consequently ended up being rushed to meet deadlines. This resulted in code being released into production to early, which has caused some serious issues in the daily operation of MRA. The main problem was that code fixes introduced new issues and kept being repeated like a vicious circle that was difficult to break.
MRA recognized this problem and decided to setup a Continues Delivery capability with an important focus on test automation to ensure that APIs are regression tested after each code fix with the aim to reduce the ...
