Letter from the Editor – March 2019

Software development projects are multifaceted. There is staffing and budget work. There are communication and team dynamics. There are project and process issues from what the customer wants, when they want it, revenue projections, and production dates.

As part of my work in helping people deliver software, I get involved in all aspects mentioned above. But, in the end, it all comes down to one thing: testers have to do a great job testing! This is where strategy, tools, technology, methods, and skills come into play.

Every time we do a methods and skills issue, my desire is the same: get testers the skills they need in order to do the best testing job possible. It’s important that you learn all the basic methods, test methods, and leverage tools and technology where you can.

A tester’s job is to find bugs. We want to find the important technical bugs, and we always want to find them as early as possible because they will be much cheaper to fix; we want to find as many customer focused bugs as possible. 

With there being a focus on shift-left and as the technical skills of most test teams increase, leverage new tools as much as you can. It’s always a good idea to reevaluate your testing strategy instead of just “Doing what we always do.”

What I often find in my work is that most developers and many testers do not understand the basic practices of software testing. Whether you are testing at the API or UI level, you still need to know how to do equivalence class partitioning and boundary value analysis to get the most test coverage with the most efficient set of test cases. Additionally, you can help the developer write unit tests by optimizing with your knowledge of the best data for testing. 

I have noticed a bit of a revival of model-based-testing recently. This is good! Testing from models is not only a standard and basic testing practice, it’s a great complement to requirements-based-testing built on user stories. You can find better bugs earlier, but first you have to know how to make a model! A few years ago, Unified Modeling Language (UML) fell out of preference. And, along with it, people stopped learning modeling skills and diagramming (such as making object models, state-transition diagrams, or class diagrams). Most organizations today, if they model at all, will make a UI wireframe.

The amount of information test teams use from a wireframe is important, but it’s nowhere near the amount of information test teams could use from other technical diagrams. It is all too bad! I would change my testing strategy often based on what parameters are sent to various components.

Apply important test methods — perhaps, adding a new interface earlier to ensure that you do the best testing job possible. Knowing how to do concurrency and race condition testing is essential. Most people do that later in the development cycle when the product is fully built. Instead, maybe you can shift that earlier. Maybe you can shift-left and do your concurrency and race condition testing earlier at an API level if this applies to you or your product, based on you knowing the testing skills and methods used for this. The same idea goes for soak testing and other essential test methods. As long as you know how to do them, what they are, and when you do them in a process (based on your product and technology) you can really optimize your testing strategy.

Build your skills and share testing technology across the development team.

In this issue, we take an in-depth look at a wide variety of testing essentials and methods. Our own Hans Buwalda discusses using Action Based Testing in TestArchitect in our cover story. Fred Murphy, a LogiGear alum, discusses the process of testing smoke detectors, Eran Kinsbruner returns to discuss progressive web apps and its impact on cross-browser testing, and Sankha Jayasooriya discusses how to test a mission-critical system. Due to popular demand, we’ve created a fun word search for you. Rounding up this issue, we’ve also included a recommendation of books every software tester should read and explained TestArchitect’s awesome screenshot feature in TestArchitect Corner. Whether you’re new to the software testing industry or a veteran, this issue explores a variety of test methods and essentials you’ll need in your software testing journey!

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

In every year since 2011, we have devoted one edition of our magazine to the topic of mobile testing. In this year’s issue on mobile, we focus on testing from the point of view of the user experience. Most teams start with UI testing, and it may seem basic — until you look at the ...
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 ...
The Greek philosopher Heraclitus of Ephesus (c. 500 BCE) is credited with saying, “The only constant is change.”   This is a statement that, more than 2,000 years later, still holds true. Today, we are in a time of great change. Everything is in flux. The fact is, we are always in a state of change even if ...
This is our third issue concerning topics of Continuous Delivery (CD) and DevOps with the inclusion of Continuous Testing. DevOps has been around for a while and I hope the period of buzz is over and companies moving towards building a development pipeline have begun their process, including changing their test strategies.
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, ...
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 ...
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 ...
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 ...
For everyone still celebrating holidays: Happy Lunar New Year! At this time of the year many teams and companies are starting new projects, new initiatives, and hiring new staff. LogiGear Magazine will continue to be the resource for you for better testing with much less stress! We are excited about the focus of this month’s ...
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 ...
Integrated teams Something we’ve learned in the Covid-19 pandemic is that we have to work together-whatever together means. Very few teams stayed co-located; even teams in the same town worked at home. We’re all working remote. Hopefully all the thinking, tools, work and effort we put into having offshore teams work together benefited us here. ...
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 ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe