Letter from the Editor


clockThis is our first Trends issue in our 10- year history. Trends are important to help foresee what is on the horizon and coming next.

For as long as I have been in software testing, there has been a constant demand to grow technology, grow skills, automate more, and do it all faster (that is a given). What has been so remarkable recently is the rate at which these demands shift gears and move in different directions, new products, and evolving technologies.

It’s the new normal. The explosion of every aspect of technology– from development methods to tools to products– is more diverse and more cross platform than ever: shift left, Lower level API and service testing, data in the cloud, multi-tool test automation suites – and always faster.

For example, mobile evolved into SMAC with huge demands for new skills, working faster, more cross environment tools. There have been embedded systems since hardware was first made. There has been data and databases since flat files. Now, embedded systems on IoT devices can stream massive amounts of data to giant data clusters in the cloud to be mined, then have analytic results sent back to the team.

The new systems being developed with a focus on mobility and smart devices on diverse platforms all need completely different test technologies and strategies all along the way.

There are so many aspects of software and hardware products we could use as examples in this rapid change- testing with often problematic local servers has evolved to testing on perfect, easy-to-build environments using containers in the cloud.

The question then becomes for any career in software testing: how do you respond to these rapid changes?

Before we get too deep in this conversation, an old school rule of thumb is that programmers need to be specialists, and testers need to be generalists. However, I am not suggesting that everybody has to learn to be effective in every aspect of product development, technology, tool, and test technique.

To some degree I still think that true testers can have a gentle knowledge of any certain area and do an effective testing job. The Agile principle of cross functional teams supports this idea of being a generalist in many fields.

One response could be to diversify and learn high level skills in diverse areas. Another response could be to specialize in one area to develop expert skills. Example areas include subject matter expertise, testing skills and technology.

It seems like a no-brainer to focus on technology, but before you make that decision, reflect.

I am asked quite often in my work about testing and subject matter expertise. Many software development engineers continue to struggle with understanding their users, understanding the market and understanding the domain where their product will live. If I’m working on a stock brokerage application, how much do I know about what the users do? For as long as software has been made, testers have been expected to specially understand users. The feedback about the subject matter of your product and your users will always be a benefit to the team, and the analytics world, which is growing so much right now, is trying to tackle this very problem of feedback to the Dev and Test.

Technology would include, for example, learning how to test microservices, how microservices work in containers, and what interfaces to apply testing when using containers as a platform.

You could learn a variety of tools and they could become an area of expertise. This would be especially useful in the DevOps world with so many tools changing the Dev process. The questions are: How and where do you include performance testing with new performance testing tools? What security testing tools would be useful for a functional software test engineer to use rather than a security testing expert? What tools can you use to test microservices that are different than testing web services or ideas that are the same?

You could focus on testing technology with the shifts from continuous testing to continuous delivery. However, what are the insertion points for software test teams? What are the responsibilities of the software test team in continuous delivery? What testing belongs to other teams like developers or Ops/IT? What testing belongs to performance engineers and security experts? What types of automated tests can I run in production that will be useful for immediate feedback and continuous monitoring but not be intrusive to the running system?

This is why we are looking ahead in a trends issue. What are the areas in software testing undergoing explosive growth and increased use to which any responsible software tester must be knowledgeable? As we often talk in this magazine, lifelong learning is a goal for any knowledge worker. It is an essential part of your job and job satisfaction! Whether you choose to do lifelong learning for yourself, or your company provides that for you, is situational to you. But you need to grow and change in your skills.

In this special issue our CEO, Hung, will be giving us perception of what he thinks are the new movements for 2017. Also, our contributor James Sivak, will be giving us his professional insight into security testing. We have plenty noteworthy articles in store for you including an exciting interview with Hans Buwalda, a newly launched video series, and our popular regular entries Leader’s Pulse, and TA Corner. You can also find out how you can contribute to the next LogiGear Magazine Issue, and take part in our Survey!

What’s more is, we are announcing the 2017 editorial calendar for LogiGear Magazine. If you want to submit an article, we are happy to consider it.

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.

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

Testing Embedded systems and testing the Internet of Things could each have their own issue of LogiGear magazine. But these days they are referred to presupposing knowledge of the other, so we thought it would be a good idea to tackle the two together in this issue to give a broad understanding of the landscape ...
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 ...
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, ...
Change is constant. What’s different today is the rate of change. Moore’s law resulted from the observation that that the rate of change in computing power is exponential. The products, services and software landscape appears just as dynamic. At the same time, we pretty much take for granted the ubiquitous presence of software running our ...
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 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.
Everything is mobile. What else can we say? Everything. If your product or service is currently not, it will be very soon. As Apple says: “There’s an app for that.” There is an app for everything. The race for mobile apps has consumed the software development world. I did a few projects at Palm Computing in the ...
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 ...
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?
“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 ...
If you are reading this issue, you are probably aware of the impact on the business world of cloud computing. Most people do not have a good grasp on what the cloud is or how people and products can use it. BTW, you are already a cloud user. If your email is stored somewhere “on ...
I led the Editor’s Note in our very first mobile issue with “Everything is mobile”, but it is now way beyond what we thought. Mobile has come to mean only the smart phone, mobility is the word that describes everything a smart phone enables you to do. Mobility is more than a device! Mobility is ...

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