Letter from the Editor – June 2021

Because of the type of work I do (consulting projects at different companies), I’ve been lucky in my Software Development career to have worked on a bunch of software projects specific to hardware devices or integrating new hardware into software systems. Starting with the Palm Pilot, I worked on some operating systems (OS) projects, firmware, drivers, and the like. Some of the skills I developed I never used again… but, many skills opened up doors to other jobs and my knowledge in testing hardware integration, particularly automating testing of wifi-enabled smart devices (IoT) and voice systems. 

Had I stayed in the area of my first few jobs where I was building some subject matter expertise, my domain knowledge would have increased, but the technical knowledge gained proved more beneficial. Working on a variety of projects for various companies forced me to learn a variety of technical skills I would not have learned had I stayed at one company. Building a wider variety of skills is important to anyone’s career, or whether you will become a “Full-Stack” Tester or not. But in these days of Digital Modernization or Full-Stack Product Teams, floating between testing tasks from database to browser to mobile to back end is the new norm.  

The same situation happened when I jumped to a data and database project at a different company. This was a completely different product development and testing situation. Over time, I gained a pretty wide variety of tools for my toolbelt: Device and OS, driver, firmware, and hardware integration testing skills; web and server testing skills, followed by database skills; jobs that were only API testing; jobs that were IoT, wifi-connected devices; jobs that were testing cloud systems… I could go on.

Now we are in a world of Digital Modernization. The big benefit here is that with Digital Modernization, the whole idea is modernizing with new technologies, cutting-edge technologies, and data––lots of data. But, we can’t forget modernizations like automating processes, adding connected devices, or moving to the cloud; these are all typical for Digital Modernization.

For many teams, the issue with Digital Modernizations is having the skills to build and test new and complex systems. Lately, what is becoming more common in product development vernacular and where the conversation turns to is the phrase “Full-Stack Development.” The full-stack tech worker is the jack of all trades. “Full-stack” is most commonly referred to as “Full-Stack Developer” but also as “Full-Stack Tester.” The point here is that they’re a multi-skilled team member who can go from front end to back end with added skills in the newest technologies. This is a tall order for any team, but in Digital Modernization, we’re now not only testing web systems, but also devices to data, to servers, and to the cloud. And, of course, the testing should be automated.

There’s a lot of discussion today around this idea of both Full-Stack Development and Testing. Adding to your technology skills regardless of what you do is essential, but there are really 3 options here:

  1. You can try to learn as many skills as you can. Be careful about only scratching the surface or only having high-level knowledge. You do not want to be a jack of all trades, but master of none.
  2. You can have a complete skill set across the team. Have multiple people on the team be sufficiently skilled in general but also have a new area of expertise. This way the entire team when looked at holistically is full-stack.
  3. Outsource to fill out the skill set. Then, you’ll have the freedom to build more skill overtime or have individual experts and the team before stack. Outsourcing can give you the flexibility to hire for specific technology gaps on a team. You can also outsource all the tech need and keep internal teams focused on domain/subject matter testing. This is particularly helpful with new technologies added into your modernization projects.

Building skills and growing in technical skill, testing skill, as well as domain knowledge is a tall order. But, it is the nature of our job! And, the goal behind LogiGear Magazine has always been to help you in this effort.

As you begin or continue your Digital Transformation journey, we want you to know that LogiGear is here to help you at every step of the way, and that’s precisely why we’ve dedicated this issue to DXs. Our cover story breaks down the 4 key components of a DX, as well as the 7 pillars of an effective DX strategy. When it comes to a DX, you hear many reasons as to why you should embark on a DX journey, but sometimes the benefits aren’t always clear; in our article 4 Business Benefits of Digital Transformation, we outline 4 overarching benefits that you can expect to reap after a successful DX implementation. While this piece focuses more so on the overall business and organizational benefits, we also created Digital Transformations Effect on QA to give a voice to and hear the opinions of the people putting in the work to actually push the DX forward. Our infographic, What’s Driving Digital Transformations, takes a step back to look at the external forces of the global business market that are driving these mass digital strategy adoptions, as well as commonly cited roadblocks to a DX implementation. Finally, in this issue’s Blogger of the Month, Jabil delves into a survey they ran that asked tech leaders what the biggest challenges to DX was, as well as recommendations on how to overcome them.

We hope you enjoy our June 2021 Magazine––Happy Digitizing!

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

Integrated teams Something we’ve learned in the Covid-19 pandemic is that we have to work together-whatever together means. Very few teams stayed co-located; even teams in the same town worked at home. We’re all working remote. Hopefully all the thinking, tools, work and effort we put into having offshore teams work together benefited us here. ...
This is our first Trends issue in our 10- year history. Trends are important to help foresee what is on the horizon and coming next.
I remember the times when test teams sat in their own area and we were not allowed to “bother” developers.
This is our third issue concerning topics of Continuous Delivery (CD) and DevOps with the inclusion of Continuous Testing. DevOps has been around for a while and I hope the period of buzz is over and companies moving towards building a development pipeline have begun their process, including changing their test strategies.
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 ...
In every year since 2011, we have devoted one edition of our magazine to the topic of mobile testing. In this year’s issue on mobile, we focus on testing from the point of view of the user experience. Most teams start with UI testing, and it may seem basic — until you look at the ...
As we settle into autumn, we’re taking the time to start some new traditions. This is LogiGear magazine’s first issue on SMAC. SMAC—social, mobile, analytics and cloud. We will be doing more issues in the next few years on these topics since so much of the product world is moving to this development stack.
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.
API testing– an old school technology gets way cool again. APIs and testing them is nothing new; the technology has been around for decades. The most basic definition of an API is an exposed function— a producer (person or company) writes a function and exposes it so that others, consumers, can use it. We copy ...
We launched the first ever software testing conference in Vietnam, VISTACON. It was a resounding success, with well over 200 participants and 20+ speakers from around the globe; each speaking on a wide range of cutting-edge testing topics. In this month’s magazine, we have uploaded several video recordings of event presentations – giving our readers ...
As fast as Mobile is growing, the platform is still immature and is evolving at a very rapid pace. While there are whole countries that have migrated large government services to mobile, countries ranging from Estonia to Turkey to Kenya have many longtime mobile users have yet to use mPay or other mobile payment systems. ...
Software development projects are multifaceted. There is staffing and budget work. There are communication and team dynamics. There are project and process issues from what the customer wants, when they want it, revenue projections, and production dates. As part of my work in helping people deliver software, I get involved in all aspects mentioned above. ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe