Letter From The Editor – December 2019

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 variety of people who work in quality every day, in all sorts of fields. Some of these fields include government, consumer products, security, insurance, education, banking and finance, and more. We also got answers from around the world!

Testing is a multifaceted practice and process-this is one of the things that attracted me to it. It can be complicated, we design and engineer tests, not to forget “the exciting world of” product development.

It’s also quite misunderstood. Some people underestimate the creativity involved in designing tests, designing data, and even sometimes designing an environment and condition to execute those tests and apply that data. Some people also underestimate how repetitive testing is. Run a test. Change one thing. Run another test. Change one thing. Run another test.

The people coming into the field are typically those who do not understand it. It is also mistaken by people who are scheduling it, waiting for it to be done, and the people who manage it. I hope this issue gets people wondering about testing as a career, as well as a glimpse into what testing work is about. We also want to provide people who work with test teams as opposed to in test teams a view into what test teams do, in addition to what they like and do not like about their work. We tried to get as many different situations of test work as possible. Testing is very different from company to company. What passes for normal workday and common practices in one company might never happen in another company whose practices and execution may be completely unique. There are few rules in testing. There are suggestions and some guidelines, but in the end, there are no standard practices–it’s always content-driven.

In my work, I also see how varied the quality world is, from testing being an afterthought that barely happens so the product can meet a schedule, to quality running the entire development and deployment schedule on safety-critical products, and everything in between. I thought it would be a benefit to test teams and the software development world to hear this from the people who work in the software development industry, rather than a simple survey, or just me relaying other people’s experience. So, we decided to have an issue only about testers telling their story, ranging from what they like, what they don’t like, what is frustrating, and simply just what testers actually do day-to-day. 

We hope you enjoy this issue. We had fun talking to so many people working in the field to develop this content. Also–it’s not over! You can join in by now going to our website and reading the other Tester Profiles submitted, as well as post your own!

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

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.
For everyone still celebrating holidays: Happy Lunar New Year! At this time of the year many teams and companies are starting new projects, new initiatives, and hiring new staff. LogiGear Magazine will continue to be the resource for you for better testing with much less stress! We are excited about the focus of this month’s ...
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.
Happy New Year from LogiGear to those of us who celebrated New Years on January 1! And for our lunar calendar followers, an almost Happy New Year come February 3rd. We look forward to an exciting and full 2011 as its predecessor was a tough year for many in the software business. At LogiGear Magazine, ...
Every year, LogiGear Magazine devotes one full issue to Test Automation. We could do more than one, and perhaps even that would not be enough. The problems around automation have become increasingly complex. And now, automation is much more integrated into the software development process. For over a decade teams have been faced with “do ...
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 ...
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 ...
Hi everyone and welcome to our fourth edition of LogiGear Magazine. This month we finish Michael Hackett’s piece on “Agile in Testing” with part five, Tools.
I remember the times when test teams sat in their own area and we were not allowed to “bother” developers.
“Why do we need to understand a bunch of test methods? I write test cases from user stories or requirements, automate what I can and execute the rest manually, and its fine.” If this is your situation: good for you. If you are time crunched, if your automated tests have lost relevance, are hard to ...
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 ...
Automation is a mantra in testing. Anyone associated with software development wants more test automation, but it’s often misunderstood. People who do test automation know how difficult it can be. But some people do not understand that automation is code, and that it needs to have architecture and design just like production code. They do ...

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