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?
Mainframe agility is paramount for any mainframe-centric enterprise in order to achieve true business agility and to get to the market faster. But how can it be done? Let’s take a look at some of the key DevOps mainframe tooling elements.
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.
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.
This blog follows on from last week’s Seven Steps to Start Your DevOps Initiative – part 1. The paper “Seven Steps to Start Your DevOps Initiative” by Ronni Colville (2014) lists 7 key recommendations for successfully implementing DevOps. Below I continue my discussion and share my insights for steps 5 – 7.