Letter from the Editor

I remember the times when test teams sat in their own area and we were not allowed to “bother” developers.

We sat there idly waiting for code hand-off. We only tested through the GUI. We worked all week and had meetings half of each Friday, to review status reports, metrics and bug reports. One day a week was “build day” and everyone ran around getting all kinds of various tasks done: qualifying the build, smoke test, verifying bug fixes, and combing the build notes for feature changes. To some people— this may seem strange. Times have changed. A lot! It was actually not too long ago this was common and, most importantly, there are still organizations like this.

Testing— as has all development— been revolutionized. Even calling people “Testers” has changed. The team name QA/Quality Assurance is practically non-existent any more. The whole team has responsibility for quality, not one group. And that group certainly does not promise or guarantee anything! They run tests, they don’t promise quality.

The idea of testers being not part of development is outdated as well. People who test are in the middle of software development— not on the outside. An often cited example, now 12 years old, is when Microsoft stopped having Test Engineers and had a new role of Software Development Engineer in Test (SDET). For more information on that transition, find the details at MSDN blogs. What is important to me here for this issue, is the declaration that people who run tests help design the software product. It’s not only POs, Bas, Programmers, or Marketing.

Testers contribute to product design and help specify how a feature will work and what will be blocked or throw error messages. In many teams today, test teams are the ones most responsible for adding acceptance criteria to user stories so they are essentially ironing out the deep details of how a feature will work.

Now, instead of waiting for handoff, we are in the middle of designing and testing it.

No longer outcasts, and now, right at the center. This is a great modernization.

With so much changed today, and working together on smaller teams with more collaboration, there is more distributed ownership of testing. Many teams stopped writing test plans. Most teams stopped writing test plans— so they stopped planning testing projects. Bugs were missed and technical debt builds up.

In my consulting practice, I go to many companies each year and evaluate, recommend practices, implement, and coach. We get a bit biased in Silicon Valley that everyone develops “like us.” Also, in research and writing about software development today, we rarely hear from teams anywhere but at the cutting edge.

Regardless of where you are on the spectrum of your software test practice, there are some basic skills and practices in testing that use to get more attention in those old days. Some teams today either don’t know how to perform or even get help with basic practices. We are here to help.

This issue of LogiGear Magazine is focused on the essentials of a testing practice. Whether the testing is done by developers, traditional testers, customers, or product owners, these are the basics of communication in testing that everyone needs to know. But as with everything in development today, these things are done differently than they were just 10 years ago.

In this issue, we will cover everything from writing modern test plans, and writing great bug reports. Blogger of the Month, Thanh Huynh discusses 3 simple reasons why your bug reports suck, and how to fix them. Zephyr’s Sanjay Zaldivia discusses distinguishing the differences between smoke and sanity testing in this exclusive article. Leader’s Pulse is Part 2 of Managing the Knowledge Worker, and this issue of TestArchitect Corner shows how you can use TestArchitect for API testing for SOAP and REST Web Services— without a single line of code. Catch Minh Ngo and Thong Nguyen discuss the latest release of Selenium in “Selenium 3.0”. We also have two cool infographics exploring the evolution of software testing, and we review ten things QA teams should know about testing.

Thanks for reading. Good luck! Learn and share skills across your team!

 

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.

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 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 ...
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 ...
“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 ...
I have been excited about this issue since I included it in the 2011 editorial calendar. This issue of LogiGear Magazine dives into an exploration of agile automation—from the most efficient methods for test automation, to skill sets and better preparation for test teams, and even to understanding the variety of tools in question. We ...
I led the Editor’s Note in our very first mobile issue with “Everything is mobile”, but it is now way beyond what we thought. Mobile has come to mean only the smart phone, mobility is the word that describes everything a smart phone enables you to do. Mobility is more than a device! Mobility is ...
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 ...
Testing the Software Car. As usual with the LogiGear Magazine, we are tackling a big subject. With our goal of having single-topic issues, we have the ability to grab and disseminate as much information as we can related to a current topic that is interesting and also on the frontier of Software Testing.   Some ...
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. ...
I spend about half my work time in the role of a consultant assessing, auditing and examining software development team practices and processes for the purpose of process improvement. I am regularly surprised to find teams that lack basic skills, management support, tools, information, access to users, Product Owners and to developers. And yet they’re ...
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, ...
Methods and strategy have been my favorite topics since I started working in testing. It’s essentially engineering problem-solving. It’s both looking for efficiency and attempting to measure effectiveness. So, how do we develop a set of practices to solve our Software Testing engineering problems?
This is our first Trends issue in our 10- year history. Trends are important to help foresee what is on the horizon and coming next.

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe