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 have been training testers for about 15 years in universities, corporations, online, and individually – in both a training, managing and coaching capacity. So far, I have executed these various training efforts in 16 countries, under good and rough conditions – from simultaneous translation, to video broadcast to multiple sites, to group games with ...
“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 ...
DevOps can be a big scary thing. Culture change, constant collaboration— whatever that means— a big new set of tools… it’s a lot. What most teams want is to have a smooth running software development pipeline. I have stopped using the phrase “DevOps,” and now I say “Continuous Delivery.” There are many reasons for this.
I remember the times when test teams sat in their own area and we were not allowed to “bother” developers.
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, ...
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.
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 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.
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.
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 ...
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 ...
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 ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe