I recently read a chapter on Explore/Exploit in Algorithms to Live By, and saw how much this concept can apply to software testing.
First, let’s define what we mean by “Explore” and “Exploit” in the context of software testing.
Explore: continue to explore the software under test and look into new areas of the SUT Continue reading “Explore/Exploit: An approach to software testing”
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) Continue reading “What I wish I knew when I started testing: Get involved with the testing community”
In this blog post, I will focus primarily on the struggles I’ve faced in managing and achieving my goals, as well as what I’ve learned from it.
Less is better
When it comes to managing and achieving goals, I’ve found that less is better. Continue reading “Bloggers Club: Managing and Achieving Goals”
Here’s a step by step guide on how to write a bug report /defect report.
First, we need to ask ourselves a few questions:
- Why are we writing a bug report?
- So there is a record of the behaviour
- So that the bug gets fixed – for the bug to get fixed we need to provide clear enough information so the developer can act upon it and the product owner/manager etc can decide how to prioritise this bug and if it should get fixed.
Continue reading “How to write a bug report /defect report”