How to start your career in software testing

So, you want to become a software tester but you are not currently working in the IT industry? There are a few things you can do to get your foot in the door, but it can take a bit of time to actually land your first role as a tester. There are a few options regarding the very first step you can take. 1. Join a company that has testers by using the skills you currently/already have I’ve met a few people who became testers using this approach. continue reading

Are we talking about the same thing?

I’ve always found it fascinating how people can use the same words but be referring to something entirely different. There seems to be a tendency for people to attach different meanings to concepts, words and ideas based on their previous experience to these things. On a personal level, before our daughter came along “a s*** sleep” used to refer to 5-6 hours of sleep. Nowadays 5-6 hours of sleep sounds amazing and “a s*** sleep” refers to 3-4 hours (or less! continue reading

Coming up with a device testing strategy

On my current project I’m in charge of both manual testing the app on iOS and Android as well as maintaining two separate automation suites for iOS and Android (when I joined the team I had to overhaul each suite as the app was rebuilt). In this blog post, I will share my device testing strategy for testing new features (manual testing) and what guides it: What must be supported? Our client has communicated with us their expectation around what OS versions and devices must be supported. continue reading

Why diversity matters (to me)

I had an interesting conversation with our Managing Director of the European Studios at a recent get together where our Malmö team got to meet our leadership team in real life, after a long time of only seeing people’s headers and shoulders (#notsponsored). Our fairly brief conversation covered a range of topics but one thing I distinctly remember her mentioning was how important diversity is to her. This got me thinking. continue reading

Choosing what not to write automated tests for

While it’s important to make sure your test automation has good coverage, I think it’s also important to know under which circumstances you should not write automated tests. In my opinion, when it comes to test automation, more isn’t necessarily better. More tests don’t necessarily result in better coverage. More tests don’t necessarily increase your chance of finding regression bugs. More tests is just that. More tests. When deciding what not to write automated tests for, I think it’s important to ask yourself a few things. continue reading

Getting started on a testing project (revisited)

A few years ago I wrote a post on getting started on a testing project. I’ve learned a few things since then and wanted to share an updated 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 continue reading

Step by step guide to becoming a technical tester

It seems to me that there’s an increasing demand to hire people who can write test automation, or at least are “technical testers”. For more on what this term means, check out this article on the Ministry of Testing. For the purposes of this blog post, I’m going to say that “technical testing” means someone who can go and test beyond the UI (User Interface). This means they can probably do the following: continue reading

Interview with Marie Drake

Marie Drake is a Quality Engineering Manager at Zoopla. Previously, she was a Principal Test Automation Engineer at News UK within the Product Platforms team where she was responsible for setting up the overall QA strategy and ensuring that they deliver a high quality product to end users. Part of her role is to also educate everyone about Software Testing and Test Automation so the responsibility of testing is shared across the team. continue reading

Interview with Emma Bostian

Emma Bostian is an American Software Engineer working at Spotify in Stockholm, Sweden. She is a co-host of the Ladybug Podcast and teaches web development with LinkedIn Learning and Frontend Masters. Emma is also the author of De-Coding The Technical Interview Process. What’s been your biggest learning from your side projects that you have been able to apply to your day to day? My biggest learning from my side projects that I’ve applied to my daily routine is to commit to something (be that a meeting or a deliverable) and to deliver on that. continue reading

The Economics of Software Testing: The Sunk Cost Fallacy

What is a sunk cost? A cost that already has occurred and cannot be uncovered. (Source: https://en.wikipedia.org/wiki/Sunk_cost) What is the sunk cost fallacy? Individuals commit the sunk cost fallacy when they continue a behaviour or endeavour as a result of previously invested resources (time, money or effort) (Source: https://www.behavioraleconomics.com/resources/mini-encyclopedia-of-be/sunk-cost-fallacy/) Put simply, if you are continuing to do something because of the resources you have ALREADY committed to it, then you have fallen for the sunk cost fallacy. continue reading

All posts or browse all categories