Letter from the Editor – February 2013

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 lives and the conveniences and ease it brings.

The landscape of product development is constantly shifting— mobility is everything and everything thinks. From medical devices to toasters, from radio becoming Pandora, from cash, checks and credit cards becoming online bill pay becoming mPay— everything is run by software, and more software with logic capability is being deployed. The technologies landscape too is shifting— the Cloud, SaaS, virtualization, cross-platform/non-platform specific mobile apps to HTML5.

Many commentators on technology today state the PC is dead. How will this impact software development and how can test teams be best prepared for this new landscape? For starters, testing cannot remain the same. Software development today is more agile, less documented, faster and even more distributed—but that is last decade’s news. Testing has lagged software development but the future demands the lag must be reduced exponentially. This doesn’t mean that as testers we are behind the curve, there are teams already running tens of thousands of automated tests on hundreds of virtual environments against daily builds for global financial security systems. There are many very sophisticated test teams. Yet, even their landscape is changing as products and services change.

This issue of LogiGear Magazine examines the seismic shifts changing how we do product development and specifically how we test software. The landscape has changed. What we test has changed—how do we keep up? As much as we are looking at global trends, some people are already there.

This specific issue also reminds me of the mission of LogiGear Magazine. We want to provide a forum for learning new ideas, methods, practices, state-of-the-practice in software testing and a view into the broader landscape of software testing. I tend to focus on the project ahead of me and sometimes lose sight of the broader horizon. In this issue, Mandira Srivastava tells us why 2013 is the year of the cloud; I will discuss the changing software testing landscape; Pete Schmitt shows us how to leverage the cloud across your organization; Michael Vizard discusses how to get around issues of scale using virtualization; and Adrian Woodhead reviews the book, How Google Tests Software.

Since we moved in to a WordPress platform last year, we have built an archive of our past issues and also cross referenced all our content to be searchable on keywords for research on specific topics.

Also, Happy New Year. Happy 2013 and Year of the Snake in the lunar calendar. The Snake is intuitive, introspective, and refined. He can appear cunning and reticent and works very modestly in the business environment. The Snake will plot and scheme to make certain things turn out exactly as they want them to. Hmm. Sounds like many testers I know! Happy New Year.

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

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 ...
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.
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, ...
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 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 ...
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?
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 ...
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.
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, ...
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. ...
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 ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news