Letter from the Editor – February 2014

“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 maintain or regularly miss bugs, if you do not have useful and meaningful ways to confidently measure and report coverage and risk, if you are doing what you have always done, if you document too much, or document too little, if testing is “a mess”, if the dev teams do not trust your testing, if you wish there was a better way……then arming yourself with new test methods or examining the methods you currently use will, without a doubt, be beneficial!

In our continuing effort to be the best source of information for keeping testers and test teams current, we have dedicated this issue to exploring test methods. Learning test methods is core to a test engineer. These are the skills and methods we use in the daily execution of our work. Without having enough tools in our arsenal, our job is compromised. Worse, it can be inefficient, insufficient, misleading and worst- miss bugs!

From useful and complex Linear Code Sequence and Jump (LCSAJ), to old faithful, Model-based testing, there are a very large number of important test methods. Lately I have seen a renewed use and importance of Scenario-based testing using personae for higher customer satisfaction, Real-world testing and user story validation.

Why does learning more test methods help? Test methods provide a structure for thinking. They give a framework for well understood measures of coverage and risk. For example, Model-based testing can give easy measurements of path coverage, Requirements-based testing is a common method when requirements coverage is measured or there is a need for regulatory compliance.

Different methods and techniques have different uses and goals. Different goals might be, for example, finding bugs, customer satisfaction, regulatory compliance, getting the product out as fast as you can, having confidence in the already functioning parts of the product with new added functions- all need different methods to provide the greatest confidence for these different goals.

Using particular test methods in your test strategy takes away the seemingly random nature of some test teams. I know a few teams who “hope” they find the worst bugs. Remember, hope is not a strategy! Test methods help create your strategy!

The objective of this edition is to present some new views on test methods. The goal is to give you as many tools as possible to attack your test effort and do the most effective, efficient job and communicate it effectively to the team so you can make the best most informed decisions on bug fixing, risk and release!

In this issue Brian Heys warns that without exploratory tests, the number of defects will always be higher; I’ll explain how Action-Basted Testing is a much saner way to evolve a testing project; Salesforce’s Keith Stobie reviews, “The Domain Testing Workbook” by Cem Kaner, Sowmya Padmanabhan and Douglass Hoffman; Robin Roy writes that boundary guidelines can provide a higher rate of error detection and LogiGear CTO, Hans Buwalda explains that a good test design can improve quality and the efficiency of the tests.

And, at this time of year, for those of you who celebrate Lunar New Year- Happy Year of the Horse! For those of you who do not celebrate Lunar New Year- give it a try! Its as good a reason as any to have a fun celebration.

Michael Hackett

Senior Vice President, LogiGear Corporation

Editor in Chief

 

 

LogiGear Corporation

LogiGear Corporation provides global solutions for software testing, and offers public and corporate software-testing training programs worldwide through LogiGear University. LogiGear is a leader in the integration of test automation, offshore resources and US project management for fast and cost-effective results. Since 1994, LogiGear has worked with hundreds of companies from the Fortune 500 to early-stage startups, creating unique solutions to exactly meet their needs. With facilities in the US and Vietnam, LogiGear helps companies double their test coverage and improve software quality while reducing testing time and cutting costs.

For more information, contact Joe Hughes + 01 650.572.1400

LogiGear Corporation
LogiGear Corporation provides global solutions for software testing, and offers public and corporate software testing training programs worldwide through LogiGear University. LogiGear is a leader in the integration of test automation, offshore resources and US project management for fast, cost-effective results. Since 1994, LogiGear has worked with Fortune 500 companies to early-stage start-ups in, creating unique solutions to meet their clients’ needs. With facilities in the US and Viet Nam, LogiGear helps companies double their test coverage and improve software quality while reducing testing time and cutting costs.

The Related Post

Testing tools – very important, very often overlooked, and very often where mistakes are made. First, the most common mistake people make about tools is thinking tools are only about test automation! False. Automation tools are merely one type testing tool. We will try to balance this issue between test automation tools and other test ...
Our plan for the December LogiGear Magazine was to have a forward-looking Trends and Challenges issue. However, whilst assembling our September issue on SMAC, we realized the momentum SMAC was gaining in the industry. We had a large amount of content on our hands from a range of excellent contributors. Thus, we decided to split ...
Hi everyone and welcome to our fourth edition of LogiGear Magazine. This month we finish Michael Hackett’s piece on “Agile in Testing” with part five, Tools.
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.
A while ago, I helped start a Software Quality Certificate Program as a part of the Software Engineering Program at the University of California, Santa Cruz Extension in Silicon Valley. I was on the Board of Advisors. While putting the curriculum together, a few people suggested a Measurement and Metrics course. Since I was teaching ...
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 ...
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 ...
Every year, LogiGear Magazine devotes one full issue to Test Automation. We could do more than one, and perhaps even that would not be enough. The problems around automation have become increasingly complex. And now, automation is much more integrated into the software development process. For over a decade teams have been faced with “do ...
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 ...
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, ...
I once consulted for a company to give a week-long course on testing and QA. It was a survey course covering a wide range of topics. I was setting up and chatting with students in the room. One man came over to me and said: “I have been testing for 6 months and I am completely ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe