I love New Year's Day! There's something exciting about getting a fresh start and imagining all that can be accomplished in the coming year. The new year is an opportunity to think about how we can be better testers, how we can share our knowledge with others, and how we can continue to improve the public perception of the craft of software testing.
Here are some suggestions for resolutions you could make to improve your testing and the testing skills of those around you:
Because testers are sometimes made to feel like second-class citizens compared to software developers, they might feel timid about voicing their opinions. But testers often know more about the product they test than the developers, who are usually working in one small area of the application. This year, resolve to speak up if you see an issue with the product that you think would negatively impact the end user, even if it isn't a "bug". Similarly, speak up if you find a bug that the team has dismissed as unimportant, and state why you think it should be fixed. Advocate for your user! Make sure that the product your customers are getting makes sense and is easy to use.
Pay Attention in Product Meetings
I'm sure my Product Owner would be sad to read this (sorry, Brian!) but I find product meetings boring. I know that the small details of the user's experience are important, and I'm so glad that there are people who care about where a notification badge is displayed. But listening to the discussion where that decision is being made is not very exciting to me. However, I am so glad that I am included in these meetings, and every year I resolve to pay more attention to product decision-making than I did the year before, and to contribute when I have information that I think will be helpful. Attending product meetings allows me to hear why certain choices are made, and also helps me think about what I need to test when a new feature comes available.
Do Some Exploratory Testing
I suspect that most of us have some area of the application we test where we have a sneaking suspicion that things aren't working quite right. Or there's a really old area of the application that no one knows how to use, because the people who initially built and tested it have since left the company. But we are often too busy testing new features and writing test automation to take the time to really get to know the old and confusing areas of an application. This year, resolve to set aside a few hours to do exploratory testing in those areas and share your findings with the team. You may find some long-buried bugs or features that no one knows about!
Streamline Your Operation
Are there things your team does that could be done more efficiently? Perhaps you have test automation that uses three different standards to name variables, making the variable names difficult to remember. Perhaps your methods of processing work items isn't clear, so some team members are assigning testing tickets while others are leaving them for testers to pick up. Even if it seems like a small problem, these types of inefficiencies can keep a team from moving as quickly as it could. Resolve to notice these issues and make suggestions for how they can be improved.
Learn Something New
This year, learn a new tool or a new language. You don't have to become a master user; just learn enough to be able to say why you are using your current language or tool over the new one you've learned. Or you could discover that the new language or tool suits your needs better, in which case you can improve your test automation. Either way, learning something new makes you more employable the next time you are looking for a new position.
Share Your Knowledge With Your Team
Don't be a knowledge hoarder! Your company and your software will be better when you share your knowledge about the product you are testing and the tools you are using to test it. Sometimes misguided people hold on to knowledge thinking it will make them indispensable. This will not serve to keep you employed. In today's world, sharing information so that the whole team can be successful is the best way to be noticed and appreciated. Resolve to hold a workshop for the other testers on your team about the test automation you are writing, or create documentation that shows everyone how to set up a tricky test configuration. Your teammates will thank you!
Share Your Knowledge With the Wider World
If I had one wish for software testers for the year 2020, it would be that we would be seen by the wider tech community as the valuable craftspeople we are. If you are an awesome software tester- and I'm guessing you are because you are taking the time to read a blog about testing- share your skills with the world! Write a blog post, help someone on Stack Overflow, or present at a local testing meetup. You don't have to be the World's Most Authoritative Expert on whatever it is you are talking about, nor do you have to be the Best Speaker in the World. Just share the information you have freely! We will all benefit from your experience.
What New Year's resolutions do you have for your software testing? Please share in the comments below!
"Perfect Software and Other Illusions About Testing", by Gerald Weinberg, is the best book on testing I have ever read. It is a m...
This week, we'll be talking about adding assertions to our Postman requests. In last week's post , we discussed what various API re...
As software becomes increasingly complex, more and more companies are turning to APIs as a way to organize and manage their application'...
The concept of measuring quality can be a hot-button topic for many software testers. This is because metrics can be used poorly; we've...