Reading:
What Do Software Testers Do?
Share:

What Do Software Testers Do?

We asked the testing community what was involved in their software testing roles and this is what they told us.

by Rosie Sherry

A while back we surveyed the community on the very important question of 'What Testers Do?'. Ā Not only did we feel that testers would benefit from understanding the things they could get involved with, we also felt it was important that people outside of testing understood what we do.

We surveyed the software testing people and came up with a list!

Ā 

What Do Software Testers Do? ā€” The List!

Explanations of what software testers do revolved around the concept of looking for answers.

This means testers:

  • investigate
  • seek and provide information
  • learn about risks
  • ask questions
  • clarify
  • find gaps
  • check expectations
  • document and communicate findings
  • find the truth
  • maintain a cynical view
  • look for better ways
  • ask more questions!

All of this is with a goal to help our stakeholders make good decisions.

I wish all testers did was provide scientific information, isolate & understand issues, and advocate for customers, developers & the business. We also speak unpopular truth to power & do the uncomfortable lawyer type work of proving or disproving that things work ā€œas intendedā€. ā€” Lanette Creamer

Ā 

Software testers gather...

Testers are knowledge seekers. We seek to understand to help the team make better decisions.

Gathering and providing information to others about the state of the software  Investigations, reporting, sharing, discussing, documenting, communicating, strategising, problem solving, diagramming, modelling, critical thinking, logical thinking, modelling the system, systems thinking, creating and performing experiments, truth seeking and the uncovering of lies. Investigating technology, asking more questions, gathering data, gathering metrics, gathering user data. Looking at production queries.  Business Processes. Reviewing requirements. Assessing risk. Analysing logs. Review product backlog. Understand clients objectives. Learning about the product. Learning about the company. Learning about the market. Metrics. Gap analysis. User stories. Being the connector between different business departments.

Ā 

Information gathering leads to things that look like testingā€¦

It's easy to dismiss all this gathering of things as a waste of time. Or to claim that it isn't testing.

Information gathering leads to things that look like testing!Generating test ideas. Writing tests. Maintaining tests. Documentation Automation scripts. Generating/using test data. Created performance simulations and communicate why I think people should care about the results. Writing a massively scalable dynamic data driven test harness with validations controlled by business rules. Multiple exploratory test sessions on multiple products. Traffic light quality reports of the system. Back end testing. Pair testing. Test environment setup and maintenance. Compatibility testing. User experience testing. Providing Test Data. Inventory unit tests with an eye on what to update, fix, discard. Helping clients test changes. Tools to look at errors. Back end testing. Reviewing bugs. Raising bugs!

Ā 

Things that look like testing leads to other tech related thingsā€¦

Can we accept that no job role exists in isolation and that we all may get involved in different day-to-day tasks?

Deploy code. Configuring tech for internal/customer use. Working with devs to solve problems. Organising releases. Reporting. Encouraging developers to provide fix details and retest guidance for bug fixes. Help prepare user guides. Documenting testing. Discussing feature design with UX designers and developers. Pair with developers. Working with project/program managers to find gaps in requirements/user stories/specifications/use cases. Suggest enhancements. Assisting with investigation of customer issues. Sales support assistance. Rapid product evaluation and recommendations on what risks we could assist with.

Ā 

When we test we need software testing toolsā€¦

Of course, tools, resources, process and templates can help us test better.

Creating, sourcing or managing all the tools... Software. Templates. Checklists. (GitHub) Repositories. Guides. Evaluating commercial, free and open source tools. Exploring and learning existing tools.  Different tools for different things... Automation. Data. Design. Planning. Accessibility. Load. Performance. Stability. Usability. Security. Analytics. Communicationā€¦ (Always be looking for tools to be doing a better and more efficient job!)

Ā 

Day to day communicationsā€¦

A big part of most tech jobs is good communication. We can't just be bug hunting all day long, there is much more to a testing role than that.

Stand-up meetings. Refinement meetings. Sprint review. Sprint retrospective. Release stuff. Attending all hands on meetings. Presenting to the team. Recommend changes/improvements. Bug triage. Reviewing Code. Increase communication across stakeholders. Acting as the "corporate memory" for past changes and problems. Talking to stakeholders, customers, engineers, management; anyone and everyone.

Ā 

When you test there will always be bugs to manageā€¦

Testers can find the bugs, but as testers we must strive to stop them as a team effort. Ā Bugs do not define testers.

Finding. Reopening. Fixing. Managing. Re-testing. Bug triage. Bug prioritisation. Testers can find them, but as testers we must strive to stop them.  Bugs do not define testers.

Ā 

Who will manage all the testing things?

Testing things need to be managed by testing people.

Test strategies, plans, tests. People. Processes. Stakeholders. Documentation. Resources. Resource planning & allocation. Peer reviews. Workflows. Review requirements. Test environments. Recruiting. Interviewing. Stakeholders. Clients. Customers. (An "all the things" meme image in the bottom left hand corner, just as a bit of fun).

Ā 

There are also so many angles we need to have perspective onā€¦

Sometimes we can be a generalist software tester, other times we may need to specialise.

Exploratory. Performance. Usability. Security. Load. ATDD. Monkey. Agile. Accessibility. UX. Design. API. Automation. Checking. Testing in Production. Continuous Testing. CI/CD. Mobile. Unit. Data. Database. Monitoring. Testability. Data protection. Spam. Business. AI. Ethics. Regulations. andā€¦ GDPR

Ā 

We quantify testing in tangibles by having names for thingsā€¦

When people think about testing, the immediate things they think about are things like what ā€˜approachā€™ you are taking, and what will be the out puts.

Do whatever works well for your team!
Ā 

 Waterfall. Agile. Wagile. Exploratoring. Mind maps. Checklists. Test cases. Test tools. Session Based Test Management. Note taking. Bugs. Pair Testing. Mob testing. Sprints. Specs. Documentation. Automation, automation, automation?  And trying to think what do management and stakeholders need.

Ā 

Software testers need to share and learn tooā€¦

To keep doing well at our craft we need to continually invest in our learning. This can be, but is not limited to, events, through work activities, self-directed efforts and our overall attitude to bettering ourselves for the benefit of us all.

Ā 

Events: Meetups, conferences, training courses, online things At or through work: mentoring, coaching (not just testers, but anyone - devs, designers, managers, etc!), teaching, use the training budgets, experience reports, contribute to company testing guild or community of practice, lean coffees. Self directed: blogs, books, podcasts, courses, videos, online courses, social media, community discussions. Your attitude: ask questions, always be learning (tools, software, industry, systems, design, being more technical, be more user focused, management, etc)

Ā 

Software testers do what?

Testers look for answers which leads to gathering lots of things which helps us do testing and other necessary practical day to day activities.

To do testing we need tools, communicate with lots of people and a way to manage all the things.

When we test there will always be bugs.

Testers need to think about testing from many different angles. And often we talk about it in relation to tangible things.

And of course, as a professional career, we must always seek to share and learn.

Rosie Sherry's profile
Rosie Sherry

Founder of Ministry of Testing



Ask Me Anything - Modern Testing
What Do Tests Look Like?
The Surprising Benefits of Exploring Other Disciplines and Industries - Conor Fitzgerald
With a combination of SAST, SCA, and QA, we help developers identify vulnerabilities in applications and remediate them rapidly. Get your free trial today!
Explore MoT
TestBash Brighton 2024
Thu, 12 Sep 2024, 9:00 AM
Weā€™re shaking things up and bringing TestBash back to Brighton on September 12th and 13th, 2024.
Essentials - Introduction to Software Development and Testing
Start your journey into software development and testing by learning what it's all about