Letter from the Editor – July 2011

How do you test software? How do you validate it? How do you find bugs? These are all good questions anyone on your project team or anyone responsible for customers may ask you. Can you articulate your test strategy─not your test process, but explain your approach to testing? I find that this can be a great challenge for test teams.

This month’s theme naturally follows the Test Process Improvement Issue as it is common to identify a gap in testing skills, test methods or strategies during process improvement. This issue provides you a refreshing look at various traditional test methods.

Many test teams test out of old habits. However, today’s fast-moving and high-stakes software development world demands teams do more with less, reduce risks and be more agile─and do all this faster! These pressures require the ability to effectively communicate your strategy and risks.

This month’s issue addresses something helpful to me: I can fall into a rut and need to re-examine how I test. I’d like to find out how other people are practicing. Hearing how others handle testing challenges improves my own testing. Executing the same tactics will not address new issues─I need new ideas!

Our issue provides interesting vantage points and new concepts with progressive authors discussing current topics. Lindiwe Vinson reports on Organic Inc’s strategy in mobile testing, an area of tremendous growth in development and testing today. Nadine Shaeffer evaluates the basics of writing good user scenarios and distinguishing between user story, user scenario, and use case. Janet Gregory, co-author of Testing in Agile answers test practitioners’ questions on test methods and strategy for Spotlight Interview; and Blogger of the Month features Jason Barile pointing out key features in a test plan. Also included in this issue is also the latest installment of the 2010 Global Test Survey, presenting results in the areas of test methods, tools and metrics.

With a mixture of both new and traditional testing tactics, we’ve selected a line-up of articles that will address testing methods and strategies of today.

Our next issue will focus on outsourced and/or offshored testing projects. Stay tuned!

Michael Hackett

Senior Vice President

Editor in Chief

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

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.
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 ...
In the November 2011 issue: Mobile Application Testing, I began my column with the statement, “Everything is mobile.” One year later the statement is even more true. More devices, more platforms, more diversity, more apps. It boggles the mind how fast the landscape changes. Blackberry has been kicked to the curb by cooler and slicker ...
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 ...
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.
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 ...
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.
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 ...
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 ...
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 ...
API testing– an old school technology gets way cool again. APIs and testing them is nothing new; the technology has been around for decades. The most basic definition of an API is an exposed function— a producer (person or company) writes a function and exposes it so that others, consumers, can use it. We copy ...
“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 ...

One thought on “Letter from the Editor – July 2011

  1. Good questions and an imnpotart topic, Raj!My two cents:- Good agile managers are experienced in using agile methods, passionate about it, and yet realistic enough to realise that the people are the most imnpotart factor for successful new product development.- When talking about what a person is most proud of having accomplished previously in their careers, I expect to hear a good agile manager talking substantially about others not just themselves. They would ideally be proud of their ability to teach and lead via example, to coach, rather than to direct.- I think we agree and at least I have found that good agile managers disturb the status quo, look for how to improve continuously, are full of energy, have some humility about what they don’t know, love communication and technology, and are proud of team success.- I’ve seen different hiring styles in the several agile companies I have worked in, but all require a substantial investment in time by other experienced agilists, including ideally managers and non-managers the line between the two in the agile world is much less distinct and the opinion of those to be managed counts more than ever.Thanks for this blog posting!

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news