Skip to main content


Showing posts from 2020

Step by step guide: Testing without requirements/ little requirements

 If you haven't already, you may one day find yourself in a project where there are no (explicit) requirements or very little requirements to go off.  Software can be created from conversations and assumptions. People may also assume that the little requirements they do write is enough to easily code against or test off, but then you later realise that the few lines that have been written actually pose more questions than provide answers. You first time testing on a project without requirements can be a bit scary but I'm hoping this step by step guide will help you. 1. Understand the difference between implicit requirements and explicit requirements There are ALWAYS implicit requirements. But there aren't always explicit requirements. An implicit requirement is a requirement on the SUT (Software Under Test) that is not explicitly stated somewhere (e.g. in documentation) An explicit requirement is a requirement on the SUT that is explicitly stated. Some potential examples: I

3 Things I've learned: Adjusting to my changed identity as a (paid) working mother

As I write this my daughter is having a nap, and I'm trying to enjoy my first day of vacation. Keeping a baby/toddler entertained without just turning on the TV is a struggle (we've made an exception for cutting her nails, she can watch a cartoon then). I'll openly say that before we had our daughter I never realised how much of a struggle it is to achieve a balance that feels like a balance. And now I understand what the parents were going on about when they said they went to work to rest. I'm also rather grateful that my husband is now on paternity leave, we're walking a mile in each other's shoes. I can see how difficult it can be to focus on work sometimes with a baby/toddler in the background and he can see how difficult it is to entertain a baby/toddler all day every day. I never realised how much less free-time I would have, and that's just with one child! We don't have any family support; no parents to take our daughter for a few hours. It's

Bloggers Club: What's the best career advice you've had?

When I was in university, I signed up to a mentoring program. Back then, I actually had no interest in pursuing a career in IT, I was actually a lot more interested in a career in management consulting - so this piece of advice can apply to all disciplines, in my opinion. I spoke to the careers advisor at my university   about what I was thinking of doing in the future and she suggested a guy called Dan to be my mentor. There's one piece of advice that he gave me, that still sticks with me. What makes you so f***en special? Now, as someone who lives in Sweden - this seems to be in direct contrast to the first rule of Jantelagen (Law of Jante) , "You're not to think you are anything special" so let me try to explain how I have interpreted this piece of advice. It's more a matter of forcing some self-reflection and realising what you have to offer , than it is about being special. When I was starting out my career, I was well-aware of the fact that it can be very ha

Bloggers Club: I wish I knew more about...

I wish I knew more about... Git and Source Control. While I've used Git in the past and been able to do what I need to do - I've never felt particularly comfortable in this area. I've read up a bit on what exactly source control is, and why we have it - so I feel that I understand the concepts at least. BUT when it comes to actually using Git - I tend to feel that I'm only keeping my head above water; technically staying afloat. I find that I have a fairly good idea of what to do, and what my options are if I need to park some changes I've made in my local etc. but when I read more up on it online, then I realise there's actually so much more to learn - and that I've barely touched the tip of the iceberg. My first step to tackling this is to take Simon Berner 's course on Git Source Control. I recently discovered the Bloggers Club on the Ministry of Testing Club. For more posts on this month's theme, check this out. 

4 Books Which I've Found Useful for my Testing

 1. Thinking Fast and Slow by Daniel Kahneman I heard from quite a few people how beneficial this book was for them. About six or seven years ago, I tried to read it, but couldn't get into it - then I tried again about two years ago and really enjoyed it. It's an intense read and focuses a lot on cognitive biases - a lot of which I come across in day-to-day testing.  2. Lessons Learned in Software Testing: A Context Driven Approach by Cem Kaner, James Michael Bach and Bret Petticord While this book was written almost 20 years ago, a lot of the lessons still apply today. There's A LOT of useful advice you can apply.  Strongly suggest you get a copy and then use it as a reference when the need arises.  The great thing about this book is that it's split into almost 300 lessons - so you can fairly easily pick it up and put it down. My highlights include: Lesson 9: You will not find all the bugs Lesson 25: All testing is based on models Lesson 57: Make your bug report an e

My learning journey while on maternity leave

Almost nine months ago, I gave birth to our daughter. A few weeks before then, I had started my maternity leave and since then has been the longest time (since I've started working) that I've been away from the testing world. I made a conscious choice to step back from testing while on maternity leave and not try to up-skill in that area during what little free-time I did have. Babies like to be constantly entertained it seems; or at least - mine does. However, I really enjoy learning - learning languages, new skills, about people and broadening my horizon. Therefore, I decided to still have a learning journey on maternity leave, but with some adaptions. Reading It's a great way to wind down in the evenings. Here is my Goodreads profile . Some of my favourite books that I've read since I've started maternity leave include: Don't Make Me Think: A Common Sense Approach to Web Usability by Steve Krug  The Power of Moments: Why Certain Experiences Have