When I first started my career at Sandhata, I was introduced to middleware test automation using a tool called IBM RIT (Rational Integration Tester). As a newbie, without any experience even of manual testing, I had to try to make sense of this new, unfamiliar process. Soon, however, I became fascinated by this particular tool and started to discover the real power of automation.
We recently announced the arrival of our Live DevOps Innovation Platform built in-house here at Sandhata. I wanted to share some of the tools we have used for it so far, as well as my personal experiences on this platform, as it has been very interesting and a big learning experience for me.
In 2016 we started creating a live DevOps innovation platform internally in Sandhata. We have been working hard, with the goal of creating a platform which incorporates DevOps principles and practices across the whole delivery lifecycle. We want this platform to demonstrate various aspects of the delivery lifecycle, and expose the inner workings – so that the platform can be used to help others get a headstart on their continuous delivery journey and also plan their DevOps strategy based on our working example.
Service virtualization is becoming a must-have technology enablement in the IT transformation programmes of many enterprises. However, service virtualization alone will not yield the desired ROI or measurable benefits unless the investment is extended to support the right level of testing and, especially, test automation.
DevOps: Let the team use virtual services instead of production services, and test the application right away. I am sure you might have heard this “virtual service” term in recent times if you are keeping up with the latest trends in the market. Now what is this virtual service and how is it that important for DevOps?
Being in software testing for many years now, I feel that one thing that has never changed is IT managers always being in a position to justify the investment of test automation or any technical enablers to improve the testing function within their organisation. I think this is mainly due to difficulty in proving the ROI for testing.