Letter from the Editor – March 2018

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.

I often run into people who ask me about best practices and my response is always that I am ‘not a best practices guy’. I don’t believe in that phrase.Those that inquire about the best practices will encounter infuriating results. The question comes from a place that assumes testing is mechanical, which would send the tester into a monotonous loop of repeated results. It’s not. If it is mechanized, it’s repetitive, boring, requires no creativity or intuition, and follows the exact same suite every
time.

Testing is complicated. It’s full of “what ifs”: what if you’re logged in, what if you’re not logged in, what if it’s the first time and you have no cookies, what about the same workflow after cookies are set, what if you switch mobile devices after you started some work or transaction—the “what ifs” are plentiful. Testing is creative and complicated. Different situations require alternate approaches. There is not a single best practice.

In a world where everyone is expected to do more with less time and resources, the idea of getting full, complete, well-conceived requirements through beautiful user stories at the beginning of a project is a pipe dream. By its very nature, Scrum is iterative and user stories evolve. So test teams must be fluid, dynamic, smart, aware, and empowered. Test plans evolve and are always in a state of change from various aspects.

Testing is not a canned activity that you can pop off the shelf, point at some system, and expect to get every facet of quality information that you need: bugs, coverage, risks, validation, or otherwise.

I’ve heard too many stories about teams that had their test cases prepared; they knew what needed to be automated and they had a scope for exploratory testing. But once the teams had begun on their chosen path, the product or development teams added and altered their user stories, thus undoing their previous intentions. In a similar scenario, there may not be a plan since the user stories were incompletely drafted, and they were poorly written or late. Testing requires a daily plan of attack—not a best practice.

To reiterate my point about the best practices approach, please bear in mind that not every project is the same. Some projects demand more responsiveness testing, others require accessibility testing, some need the API level or firmware level, and others that need an entirely different approach or a unique combination of all that. There are traditional projects on a desktop, browser, and mobile UI with a backend and a database—while many projects have none of that. Some projects have an abundance of new functionality whilst others are uniquely bug fixes and cleaning up existing functionality. In further consideration, we need to draw attention to projects that entail exploratory testing, which is a characteristic of many Agile projects.

Projects that oblige more confidence from you are those that are more geared towards regression testing. For all other projects, workflows and user scenarios are the best strategies.

Source: WordStream

We aren’t directing you towards a ‘best practice’, rather we are exploring alternative methods and strategies to fulfill your testing needs. Through LogiGear’s senior testers, Minh Ngo and Thong Nguyen, we guide you through the integration of CI/CD in API testing.

This month’s issue also includes two featured writers: Dustin Rodgers and Johann Hoberg. Dustin discusses a framework that aims to reduce duplicate bug reporting by a landslide. Through Johann’s article, we are provided with a fresh outlook on the world of games testing and characteristics that equate to being a good games tester. If you are in search of management methods for different generations, Leader’s Pulse is your one-stop shop. LogiGear’s VP, Michael Hackett, analyzes various management styles through personal experience and Peter Drucker’s principles. If you’ve been puzzled or found yourself interested in the aforementioned topics, peruse this issue.

Every development project is different. Testers need a variety of skills, methods, test, and data design techniques to handle each situation as each situation is unique.

As a result, you need smart, sophisticated, intelligent, and knowledgeable test teams who are also cognizant and dynamic. They must understand the nature of being iterative and emerging development rather than nailed-down, fully defined functionality. They must be able to think quickly on their feet, change their minds, and shift the strategy accordingly.

So for this best practice idea, my preference is to say there are better practices and some are better than others. Testing has never been a one size fits all. You need smart testers who can use their brains and think—testing is a challenge!

LogiGear Magazine is constantly aiming to keep you up-to-date, refresh long-standing methods, and introduce new methods to load your arsenal. In this issue, LogiGear explores various testing methods and strategies to derive the most from your testing experience and experiments.

 

 

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

If you are reading this issue, you are probably aware of the impact on the business world of cloud computing. Most people do not have a good grasp on what the cloud is or how people and products can use it. BTW, you are already a cloud user. If your email is stored somewhere “on ...
I remember the times when test teams sat in their own area and we were not allowed to “bother” developers.
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 ...
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 ...
Digital Transformation and IT Modernization projects have shifted into high gear during the COVID-19 pandemic. Tough on some teams is having to do more with less and speed up projects on reduced budgets due to the resulting COVID-19 business climate. On the other hand, other companies are adding funding and pressing the schedule under the ...
Hello everyone – I’m hoping each one of us is having a great October. This time of the year is always my favorite, with the changing of the seasons, Fall was always my favorite time of year; it signified change and renewal – but I don’t want to digress to much from what’s going on ...
In our continuing effort to be the best source of information for keeping testers and test teams current, we have another issue to explore testing in Agile development. As Agile evolves, systemic problems arise and common rough situations become apparent. We want to provide solutions. For anyone who has worked on Agile projects, especially if ...
Everything is mobile. What else can we say? Everything. If your product or service is currently not, it will be very soon. As Apple says: “There’s an app for that.” There is an app for everything. The race for mobile apps has consumed the software development world. I did a few projects at Palm Computing in the ...
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 ...
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 ...
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 ...
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 ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe