If your organisation is embarking on a Digital Transformation project, then you’ll need to consider the prospect of working with suppliers to help ease the journey. Digital Transformation is the integration of digital technology into every areas of a business, significantly changing how your company operates and delivers value to customers.
OK, so I’ve decided to write something about regression testing, what it is, what it does, why and how do we do it. So as the song goes, “Let’s start at the very beginning”.
Building a high performing team is never an easy undertaking. Building the test team for a Digital Transformation project is no different.
You’re probably familiar, to one extent or another, with the Software Development Life Cycle (SDLC). At least, you are if you’re bothering to read this blog.
Unless you’ve been hibernating for the past couple of years then you’ll be fully aware that Digital Transformation is at the top of every IT Directors list of things to do. Companies today are facing a couple of big challenges, staying ahead and on top of new technologies and at the same time providing outstanding customer experience. To be clear, Digital Transformation is the process of using new or modified business processes and customer experiences to meet changing business and market requirements by use of new and advanced technology.
The purpose of a defect triage meeting is to review and prioritise open defects and provide stakeholders with the opportunity to track progress, review and take action based on the information available.
IT teams and testers have been challenged by automated testing for decades now. It seems to me that many organisations haven’t really cracked the nut yet with regards to functional automation and many (too many) automated testing efforts fail to meet their objectives, budget and stakeholders’ expectations. Expectations seem to be lower for load and performance testing. I’m not sure if this is because it’s perceived to be more difficult or the risk is perceived to be lower or both. Either way I don’t think that’s true, but that’s for another post. There isn’t much conversation happening yet about automated security testing - yet. I find this strange considering 47% of companies surveyed for this year’s World Quality Report said that enhancing security is part of their IT Strategy. The number of security breaches is increasing – the 2018 Cyber Security Breaches Survey shows 43% of businesses in the UK experienced a security breach in the past year.
We’ve all seen sci-fi movies where robots take over the world, that is until Will Smith (or similar) steps in at the eleventh hour and saves the day. But like a lot of movies made, they do have a good knack of portraying what the future might hold, whether that’ll be a home robot for doing the daily chores to an all singing all dancing fully autonomous home.
Even today, in the modern world of DevOps, I see this all too often in automated test code for regression tests:
Test planning, it’s that task testers are often asked to perform at short notice and frequently without enough information. It’s something that sounds like it should be easy, but all too often turns into something more challenging. As testers, we also find that we sometimes become accountable based on a test plan that was formed in a hurry without enough information to begin with. Is there anything we can do to avoid this?