Skip to main content

What I wish I knew when I started testing: Get involved with the testing community

 In November 2018, I gave a talk at Belgrade Test Conference on 'What I wish I knew in my first year of testing'.

Here's the second post on the series with some key areas from that talk. (Here's the link to the first post on Expectations vs Reality)

This post will focus on more "accessible" ways of being involved in the testing community (i.e. not speaking at conferences or starting testing meetups/events)


How I discovered the testing community

At my first company, I worked with a few people who were involved with the testing community - it is through them I discovered it existed. There were also a few people at the company who organised a testing meetup in Wellington, New Zealand. Later my former mentor and two other women started a testing meetup in Auckland, based off the model that was done in Wellington.

Note: The meet-ups would have a 20 minute experience report (where someone shares their experience on something) and then this is followed by a facilitated discussion where everyone can share ideas with each other (not just direct questions towards the speaker).


How I have benefitted from attending meetups (and seen others benefit)

Discovery of new testing tools and how they are being used

By attending meetups, I was able to listen to others share their experiences on what testing tools they  used and why. They would also often share why they chose the tool and any struggles they had.


Expand understanding of how testing is/can be done

If you only work at one company for a long time, then your understanding of how testing can be done is probably fairly limited. From what I have seen, testers who don't try to see what's out there and expand their understanding on testing, might not even realise that their understanding is limited.

By attending meet-ups you'll get to see what other testers are doing and how they are solving problems etc. 

Networking

You get to meet new people. I also know a few people who got jobs based off people they met from attending meetups.


Online forums 

I wrote a few posts in the Software Testing Club back in the day and enjoyed reading others' experiences on there. Nowadays, I am somewhat active on the Ministry of Testing Discussion forum. In online forums you can ask questions and get a wide variety of perspectives on that question. 


Next steps: How YOU can get involved with the testing community









Comments

  1. I've learnt more about testing in the past four years (when I joined a company where a colleague was heavily involved with the testing community) than I did in the preceding twenty!

    ReplyDelete
  2. Nice post! I found it very useful, as I'm starting my career in testing. :)

    ReplyDelete

Post a Comment

Popular posts from this blog

Getting started on a testing project

I started on a new project a few weeks ago and thought it would be a good idea to share a checklist for what new testers on a project need and some good starting questions when you, as a tester, are new on a project Checklist for what new testers on a project need (Note, your project may not include all of the below) Note to check if user credentials are needed for any of the below

My Most Used Test Heuristics (with examples)

First, what is a heuristic? A heuristic is a guideline ,  it is fallible.  Therefore, it will give you a good idea of what behaviour you should see BUT it isn't definitely what should happen - it's up to you to confirm that the behaviour you are seeing is correct.  In a previous blog post I shared a step by step guide on  how to test without requirements/little requirements.    But I figured it's good to share my most used test heuristics that I use for testing without requirements. They are: Consistency with History Consistency with User Expectations Consistency within Product Let's take a look at each of them along with some examples to illustrate the concept. 1. Consistency with History  The feature's or function's current behaviour should be consistent with its past behaviour, assuming there is no good reason for it to change. This heuristic is especially useful when testing a new version of an existing program. (Source: developsense) Example: Whitcoulls, a

Bloggers Club: The Importance of Exploratory Testing

 Before we dive into the importance of Exploratory Testing, I would like to clear three things up. Firstly, I align with this definition of Exploratory Testing, by Cem Kamer, it is an approach to software testing that consists of simultaneous learning, test design and test execution. Secondly, I don't think Exploratory Testing has to be a substitute for test cases, it can complement test cases. (It's up to you, how or if you choose to combine both Exploratory Testing and Test cases when you test a feature) Lastly, exploratory testing is not adhoc testing - adhoc testing is random, unstructured testing, exploratory testing forced you to think critically about the application under test. (For more about the difference go here .) Job Interview Analogy To illustrate the importance of Exploratory Testing, I'd like to first use the analogy of a job interview. (I wrote about this in a previous blog post but will expand on this further) The Test Cases in this analogy In a job inte