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.
Over the last few weeks, we have been publishing a few articles about the Live DevOps Innovation Platform, and how we built it. But I’d like to take the opportunity to share some of the benefits that we, as Sandhata consultants, have seen – so far – as a result of building this new DevOps platform and the application Sandhata Bank.
The importance of security in software development is already widely understood and security testing is generally well embraced in the software delivery process. But when organisations enter the world of Continuous Delivery and Continuous Deployment, it becomes even more important to be able to test and enforce continuous security the same way – not only quarterly or monthly.
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.
Choices shape and define us. Past choices mould us into who we are today and the ones we make today shape who we become tomorrow. In this blog post, I will share a brief story of how my career choices have helped shape me into who I am today. After all, aren’t we are all ultimately responsible for our own actions?
Having worked in the development side of projects for so long, donning a tester’s hat for some projects at my current workplace was a new experience, nevertheless a useful one. It was almost like starting from scratch. I always had this idea that testing was largely a manual process. Yes, I knew there was automation testing and I was aware of tools such as HPQC, QTP and so on. But, having never used them before, I was not sure how they were leveraged to test the multitude of requirements. So, here go a few of my observations when performing a tester role.
Results reporting is one of the key stages in the testing phase where the interested project participants or the stakeholders are presented with information on the test progress. Although many of the test automation tools have inbuilt reporting capability, the information may either be too low-level or technical, or it may not be fully relevant for management. As part of test process improvement, I’m working on a requirement to present the test results in an efficient way, so the management can visualise the current status of testing or the overall status for a test cycle, and make decisions accordingly.