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!
Senior Vice President
Editor in Chief