Letter From The Editor – September 2020

There is a growing software development dynamic of teams without Testers.

When I first went into Software Quality, I learned one thing right away: My role was user advocate. My main job was to find bugs. This is the Lean principle called Amplified Learning. We learn about behavior by testing. Even then, validation was not the main job. We validate by finding bugs. There is a current movement happening in software development towards having Developers validating software without Testers or Test Teams.

Now, in this new paradigm without Testers—who is doing that?

The current movement toward Developers validating software without Testers or Test Team to test is risky—for a lot of reasons. First, let’s look at the role of a Tester:

What is a Tester’s job, or at least—what are some expectations of Testers?

  • Think like a user.
  • Act like a user.
  • Find bugs to cut user support calls.

Let’s look again at the Venn Diagram describing the main skills I look for on a Test Team (Figure 1).

Let’s say Developers take over all technical testing—both white-box and gray-box tests. That is a big ask, and the subject of its own discussion. Will a Developer really set blocks of time aside—or will they do “happy path” acceptance criteria validation and call it done?

The gap between Dev Mindset and Testing Mindset has narrowed significantly.

Developers work toward building and validating. Testers design tests thinking about externals: Inputs, platforms, alternative paths, boundary cases, and corner cases. Testers even think about the ever-elusive user expectations.

Subject Matter Testing – BAs and/or POs

In a perfect world, if you want to reduce Test Engineers, you have business analysts (BAs) or Product Owners (POs) and User Experience teams (UX) who will provide extensive, complete, well-thought-out user stories or requirements with lots of acceptance criteria. These people are Subject Matter Experts (SMEs) or Domain Experts, having Domain Knowledge. These folks will be very involved at the beginning of the project assisting with TDD (test-driven development) analysis of what to test. They will also run and execute System Tests (fully integrated end-to-end transaction/workflow testing on an environment very similar to production.) These folks will also run a User Acceptance Test, a pre-release test phase executed by Users. 

Testing Skill – and There are Testers Being Testers

There are tests designed and Tester skills independent to Domain/Subject Matter Expertise.

Exploratory Testing—the Lean principle of “Just in Time” (JIT Test Design)—tests the system the way it was actually built—not what a design doc or release plan test skill. New tests are designed as tests are executed based on observations, clues, and behaviors.

Good Testers can test any system. Testing is definitely not solely reliant on Subject Matter Knowledge. And actually, the more and better BAs, POs, UX teams, the less of that style testing you want.

Testing focuses on: boundaries, under stress, error cases, complex cases, boundary data, wrong data, less common platforms, problematic devices or browsers, different character sets and date/address/phone formats… the lists and tasks go on. This is where Test Teams thrive and Developers run out of steam and time to test. This is not the forte of BAs or POs—this is Test Engineer 101! This mindset, skill set, and sets of tasks cannot get lost and usually cannot be effectively distributed among other staff. It isn’t their focus.

We mainly use Exploratory Testing as a tool to learn—how does the function or system behave when I try this data, that platform, when I repeat the task but do it under a different memory condition or, even If I do it concurrently with another task? This is the basis of testing. It’s fundamental to software development. It’s a mindset. When this mindset is minimized or removed from a software development team you need, at least, 3 things:

  1. Very understanding users who are fine with having bugs/unexpected behavior, as long as they get value fast and get fast roll-backs and fixes.
  2. A substantial support system that can scale with more customer calls, customer cases, immediate feedback, and hand-holding to fix customer found issues.
  3. Not to be worried about competitors, reviews, or lost customers.

Summary

Test Teams still have a place in Modern SDLCs. Test Teams give a unique and important perspective, judgment, and feedback. It is this kind of thinking that is still needed. More specifically, the Tester’s thinking is still needed. Especially when it comes to meeting customer expectations. Even if speedy development is hoping for immediate feedback; initiatives like Continuous Testing can help to meet this need for immediate feedback in systems like DevOps.

“In this Issue” of LogiGear Magazine, we hope to inspire you to Modernize your SDLC. Our Cover Story is a special 2-part article which covers Developer testing. Our VP of Business Solutions, Clay Simmons discusses using Agile Testing Quadrants to solve Automation headaches. We have a delightful infographic on where QA Fits in Agile, and our Blogger of the Month feature is from Manish John as he dispenses lessons learned in 5 years as a Software Engineer. We’re also debuting a new survey series to capture what your work life has been like during this pandemic. I encourage you to take it and share it with your teammates, we will be releasing results in the upcoming December issue!

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

Every organization goes through times when the internal, or home team, cannot execute the testing project easily or quickly enough. The reasons are many, from the lack of an effective test strategy to low automation engineering skill, to staff positions going unfilled due to a great job market. With everyone working and very few people ...
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. ...
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 ...
Big and complex testing. What do these terms conjure up in your mind? When we added this topic to the editorial calendar, I had the notion that we might illustrate some large or complex systems and explore some of the test and quality challenges they present. We might have an article on: building and testing ...
As part of my work, I spend a lot of time at client’s sites and talk to various software development organizations. I am beginning to see a problem arise regarding Test Automation. There is too much automation! Surprised? While there are still many teams struggling to make progress with Test Automation, many teams have been doing ...
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, ...
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 ...
This is a very special issue of LogiGear Magazine. When we were putting together the Editorial Calendar for this year, we decided that instead of a technology issue, we would focus on the human side of quality and test engineering. We want to focus on individual Test Engineers and their jobs. We talked to a ...
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 was just recently at a company that had a beautiful test architecture, framework, and Cucumber with tons of well-automated tests. But there was no good test management on top of the Cucumber tests, and they did not do a good job tagging the tests. Although almost everybody on the team could write and maintain ...
Test automation is a big topic. There are so many different areas to talk about: tool choice, jumpstart, cross platform, services, cloud… Each of these areas have changed so much in the recent past that they could each be worth their own magazine issue.
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 ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe