99 Things You Can Do To Become A Better Software Tester


(Rosie) #1

‘Back in the day’…in our old forum we ran a forum discussion asking the software testing community for 99 ideas of what software testers could do to become a better tester.

We collated the list of answers and produced an ebook 99ThingsEbook.pdf (3.2 MB).

We’d like to do it all again! Whilst some answers are still relevant, others are not so much. Can we do better? Have we become smarter and wiser as a testing community?

Add your response to this forum post and we’ll collate them once we have a long enough list.


(Matt) #2

Attend security conferences (eg. BSides, Defcon, AtlSecCon). There are great opportunities for us to learn from them, and vice versa.


(Alex Langshall) #3

Stop treating developers as the enemy. I still see this mentality, and it’s unproductive, causes unnecessary conflict, and just outright needs to stop. We all work together on modern teams to make the product shine.


(Claire) #4
  • Understand the architecture of the application, what it’s made of, how it’s put together. It can help you to identify risks and test more deeply.

  • Empathise - with your customers, and your colleagues.


(Kate) #5
  • Read the Club
  • Read the blog feeds on Ministry of Testing
  • Read/Watch everything you can on the Dojo

(Butch Mayhew) #6
  • Seek to understand your customers and how they use the system. This should help you identify ‘critical areas’ that should never fail
  • Build good relationships with your developers. Ask them what they would test if they were in testing the system.
  • Question everything

(Joe) #7
  • Learn to write Gherkin
  • Learn to read code
  • Advocate for testability
  • Provide valid and valuable feedback promptly

(Rick) #8

Try to fix a bug yourself, even if it’s been around for years. You gain a new understanding of not only the process to code something, you also get to experience exit and entrance amigos from a new perspective and you get to learn how to write tests as a developer would, allowing an in to see what tests are covered. Also it allows you to get in the code review process, something that would be awesome if all testers could be involved with.


(Peet) #9

Never stop learning. At the end of every day I ask myself the question: “what have I learned today?”
No matter how small, every day there is something you’ve come across that you didn’t know the day before. All these little (and big things for that matter) “learnings” will make you a better tester.


(Will) #10

Read Git commits. As someone who comes from the ‘manual’ side of the coin there is importance in knowing what goes into the code when a produt is tested. Git commits are snippets demonstrating how the code is changed for the purpose of bugfixing, new features or refactoring, all of which are useful as a tester to figure out where the risks might be.

They also tell you more how a developer works and where they might be focused. This is especially useful if your teams work with code reviews and so you might catch on to possible mistakes or how other developer’s insight might catch bugs before you even have a line of code to test.

Finally they tell you how to prepare for the tests you will be running in your evaluation as a tester of their code. Sometimes there might be something else that wasn’t on the Jira ticket that might allude to either a potential bug or feature…


(Karthik) #11

When a feature is given to the team for development, testing and deployment, as a tester, analyze - Why do we have to do this feature in the first place? What are we trying to solve by doing this? What is the big picture of doing this small feature - how can we connect the existing dots (features) with this feature we are developing to make things better? Can you get first hand information from your managers or anyone else to get an answer to these questions?

By doing this we as testers will not just look at a web page as a set of web elements, a feature as a testable work product, but we’ll also look at it as a problem solver - a solution that someone is trying to figure out.


(Mike) #12

Learn the Command Line - it will aid you greatly in your testing

Push yourself out of your comfort zone every now and then - it’s the only way you’ll truly grow

Remember that security is your responsibility, it’s everyones responsiblity

Be kind to yourself, you have this job because you can do this job. You got this.


(Mike) #13

Advocate Usability - this software is (usually) going to be used by a fellow human being so chances are that the text being in two different fonts is going to annoy them just as much as it’s annoying you right now.


(Ken) #14

Be willing to learn.
Adapt.
Listen.


(Faith) #15

Build strong relationships with the programming team. It can be hard on the developer when you keep sending their ticket back and telling them that it still isn’t good enough, but if you have a good working relationship, you are less likely to create any tensions. Also, they can be really useful when you are trying to understand error messages and you can learn from each other. They will only help you if you are on good terms to begin with.


(Faith) #16

This! I can’t believe how hostile the testing and programming teams can be and it is really sad. At the end of the day, they both want the same outcome - a good, working system. It isn’t hard to be kind.


(Aya) #17
  • Don’t let go of your Exploratory Testing Skills.
  • Go and talk to your developers and discuss about bugs and how the things are developed.
  • Always dig deeper and find the root cause.
  • Share your knowledge with the community.
  • Try different tools (not just testing related), it will give you ideas to explore more and differently.
  • Brainstorm your ideas (Mindmaps are awesome)

These all I can think of now but will add more :wink:


(João Farias) #18

Increase information transparency => Look for ways to make people know more about all aspects of the project without having to wait for date/milestones, big delivers, or having to ask people directly. Thus, you will enable others to detect risks and problems earlier and more often.
(Sounds almost like a manager job, but I think a tester should pay as much attention as a manager in the team’s dynamics)


(Florian) #19

Apply testing to itself to become a better tester:

Test your testing methods. Test your tools, your team, yourself (but never other people - they notice). Test your test code and your automation (if any). Test your bug reporting and your other communication.

Test everything.


(Janet) #20

Learn and practice your craft: read books, blogs, magazines; attend trainings, courses, conferences; talk with colleagues, join tester’s networks and so on.

Share your knowledge.

Reflect your activities, your results, your role, your skills, your behavior.

Be aware of your responsibilities, your order and your limits.

Train your communication skills: train to listen, to ask constructive questions, train to discuss and argue in a positive manner.

Be friendly, be positive, be supportive - be the person you want to have in your team.

Be open minded, be curious.

Be patient with yourself and with your colleagues.

Have fun! :grinning: