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

Because of the type of work I do (consulting projects at different companies), I’ve been lucky in my Software Development career to have worked on a bunch of software projects specific to hardware devices or integrating new hardware into software systems. Starting with the Palm Pilot, I worked on some operating systems (OS) projects, firmware, ...
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 ...
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.
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 ...
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, ...
As fast as Mobile is growing, the platform is still immature and is evolving at a very rapid pace. While there are whole countries that have migrated large government services to mobile, countries ranging from Estonia to Turkey to Kenya have many longtime mobile users have yet to use mPay or other mobile payment systems. ...
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.
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 ...
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 ...
We launched the first ever software testing conference in Vietnam, VISTACON. It was a resounding success, with well over 200 participants and 20+ speakers from around the globe; each speaking on a wide range of cutting-edge testing topics. In this month’s magazine, we have uploaded several video recordings of event presentations – giving our readers ...
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 ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe