Letter from the Editor – December 2020

Digital Transformation and IT Modernization projects have shifted into high gear during the COVID-19 pandemic. Tough on some teams is having to do more with less and speed up projects on reduced budgets due to the resulting COVID-19 business climate. On the other hand, other companies are adding funding and pressing the schedule under the idea to “innovate or die.” No one questions the immediate need for this work, but one thing is for sure: Test Teams need to be at the center of these projects.

“Digital Transformation” and “IT Modernization” are broad terms for big projects. A Digital Transformation (DT or DX) is the adoption of digital technology to transform services or businesses, through replacing non-digital or manual processes with digital processes, or replacing older digital technology with newer digital technology. Digital solutions may enable—in addition to efficiency via Automation—new types of innovation and creativity, rather than simply enhancing and supporting outdated ways of doing things. IT Modernization aims to bring legacy IT infrastructure up-to-date and focuses on addressing operational challenges, including efficiency, access, security, and agility.

There are many reasons why these projects or paradigm shifts can overwhelm a company, including:

  1. Software Development practices have changed significantly.
  2. Toolchains have grown rapidly thanks to DevOps’ influence on quality, automated delivery and deployment, and speed.
  3. Staffing models and changes.
  4. Adoption/modernization of new technologies, hardware, and devices.
  5. Legacy systems.

Why specifically are these projects happening now? Multiple reasons: Business models and processes have changed, demand for full mobility, users’ demand has taken control, taking advantage of new technology, etc. How can Test Teams help here? No matter the exact cause, the situation at hand is a rapidly changing need, not well understood, and evolving use cases, new technologies, and speed. This is a typical strong suit of Test Teams––if it isn’t, then you may not be using your Test Team correctly.

In my experience with new products, workflows, or transformations like these, the Product Owners (POs) may not understand the customers or have a great projection of how their users will actually use the product. The Team may also get incomplete user stories without a lot of understanding of how a new feature is expected to be used.

What is often lacking here is alternative uses and alternative workflows––specifically, workflows from various personas who have different needs and goals. At the speed that most development teams work today, these are often not defined. An example of this is not thinking through error conditions, where the user needs more help or may become more frustrated as error conditions push the system into more unstable states.
It’s understandable that these issues happen––particularly with new technologies, new business models, and demanding customers. But, this situation is a strong suit for Test Engineers. A Test Team’s core skills are the magic intersection of knowledge of the user, knowledge of the technology, and knowledge of quality and testing practices. It’s the knowledge of how to test that is particularly useful here.

A three-way Venn Diagram, depicting the intersection of "Knowledge of the User," "Knowledge of the Platform/Technology," and "Knowledge of Testing & Quality Practices"––the magic intersection of a Tester's core skills.

Figure 1 – Skills Testers need.

If you are using your Test Team merely for acceptance criteria validation and UI Automation, you are under-using them, tasking them wrongly, or not aware of what great benefit Tester exploration and spending time in a new system can be. Key skills for testing that any trained and skilled Tester must possess is the ability to explore alternative paths, discover other workflows by spending time in the system, and doing “the Tester Thing.”

Put to the right task, Test Teams are a valuable asset on transformation and modernization projects with developing and evolving use cases and user stories. Core testing skills are designed just for these situations. Good Test Teams bridge the technical system to deliver a product with customer value.

This issue brings together an array of content to help you succeed in a Digital Transformation initiative. Our cover story is part 2 of my series Developer Testing? What is QA and Testing’s Place? and strategizes how managers can succeed in Developer Testing initiatives. Another part 2 piece, Using Agile Testing Quadrants to Solve Quality Assurance Headaches, was written by our SVP of Sales Clayton Simmons and explores the need for Automation in Agile, as well as how to use the quadrants to your success. This issue’s Blogger of the Month, 6 Things to Consider When Choosing an RPA Vendor, provides guidance for organizations looking to implement RPA––a foreseen key-enabler of Digital Transformations in the near future. Our infographic, LogiGear’s Winter 2020 Reading Guide, aims to help you solve common testing problems by recommending related eBooks. We’ve also collected the Best of LogiGear Magazine 2020, where you can learn some testing tips and tricks from our best-performing magazine articles of the year. Finally, we also wanted to share the latest and greatest features of TestArchitect Gondola in TestArchitect Corner: Greetings from Gondola!

From all of us at LogiGear, Happy Holidays and Happy Testing!

Michael Hackett
Michael is a co-founder of LogiGear Corporation, and has over two decades of experience in software engineering in banking, securities, healthcare and consumer electronics. Michael is a Certified Scrum Master and has co-authored two books on software testing. Testing Applications on the Web: Test Planning for Mobile and Internet-Based Systems (Wiley, 2nd ed. 2003), and Global Software Test Automation (Happy About Publishing, 2006). He is a founding member of the Board of Advisors at the University of California Berkeley Extension and has taught for the Certificate in Software Quality Engineering and Management at the University of California Santa Cruz Extension. As a member of IEEE, his training courses have brought Silicon Valley testing expertise to over 16 countries. Michael holds a Bachelor of Science in Engineering from Carnegie Mellon University.

The Related Post

In our continuing effort to be the best source of information for keeping testers and test teams current, we have another issue to explore testing in Agile development. As Agile evolves, systemic problems arise and common rough situations become apparent. We want to provide solutions. For anyone who has worked on Agile projects, especially if ...
I have been excited about this issue since I included it in the 2011 editorial calendar. This issue of LogiGear Magazine dives into an exploration of agile automation—from the most efficient methods for test automation, to skill sets and better preparation for test teams, and even to understanding the variety of tools in question. We ...
A lot has changed since I began staffing test projects. From hiring college students and interns for summer testing programs, to building networks of offshore teams around the world, and from having 24-hour work schedules to having instant crowdsourced public beta or bug bounty testing—things have changed.
I once consulted for a company to give a week-long course on testing and QA. It was a survey course covering a wide range of topics. I was setting up and chatting with students in the room. One man came over to me and said: “I have been testing for 6 months and I am completely ...
Continuous Testing… what is it? When we first decided to do a magazine issue dedicated to the DevOps practice of Continuous Testing, I joked with someone: “It’s about testing continuously.” And their reply was: “Yeah. What else would it be?” I was joking, but clearly the joke didn’t land. Continuous Testing is about testing continuously, ...
Methods and strategy have been my favorite topics since I started working in testing. It’s essentially engineering problem-solving. It’s both looking for efficiency and attempting to measure effectiveness. So, how do we develop a set of practices to solve our Software Testing engineering problems?
This is LogiGear magazine’s first issue on the big world of DevOps. DevOps is a very large topic. Just when you thought you were safe from more process improvement for a while—not so fast. There’s DevOps, Continuous Testing, Continuous Delivery and Continuous Deployment. In this issue, we are focusing on Continuous Testing, the part most ...
On the whole, everyone wants to do a great job, have a better work environment, happy clients and customers, and to be employed by a company earning lots of money. All great goals! But this is not always the case. When it is not, you can suggest process improvements, better tool use, different estimating techniques, ...
Testing tools – very important, very often overlooked, and very often where mistakes are made. First, the most common mistake people make about tools is thinking tools are only about test automation! False. Automation tools are merely one type testing tool. We will try to balance this issue between test automation tools and other test ...
There has been a tectonic shift in software development tools in just the past few years. Agile practices and increasingly distributed teams have been significant factors but, in my opinion, the main reason is a new and more intense focus on tools for testing driven by more complex software and shorter development cycles. There have ...
Testers need to learn their craft and hone in on their skill set. That means building skills, sharpening their tools, and becoming creative detectives. There is no cookie-cutter tester and no best practice. The best circumstance is a fully-skilled, aggressive tester mixed with curiosity, nimbleness, and agility.
I spend about half my work time in the role of a consultant assessing, auditing and examining software development team practices and processes for the purpose of process improvement. I am regularly surprised to find teams that lack basic skills, management support, tools, information, access to users, Product Owners and to developers. And yet they’re ...

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe