Skip to main content


Showing posts from 2015

Exploratory Testing Overview

So, lately I've been thinking a lot about how to carry out Exploratory Testing and some learning have sparked previous posts regarding why we should approach software in this way.

I mentioned in my last post I was attending a course in the busy city of London. So here goes, my attempt at simplifying my learning's

Exploratory Testing is an approach to testing. It is concisely described as a simultaneous learning, test design and test execution, let's not mix this up with a test type or technique:

There are a number of myths that surround Exploratory testing:
Same as ad-hoc testingCan't be measuredEndlessCan't reproduce defectsOnly for Agile teamsNot DocumentedWe need test-cases As I said, these are just myths and make no sense at all!
Creating a test charter is a great way to document what it is you are testing, who is doing the testing, defining your tasks for your session, keeping test notes, recording bugs and logging issues. There are plenty of examples online s…

What Are My Main Aims to Exploratory Testing?

The key questions that come up are: what is exploratory testing and how should we do it?

Exploratory testing helps test analysts and others involved in the testing field ensure systems and applications work for their users. Exploratory testing is often misunderstood as an approach but there a number of pointers you can follow to ensure you’re on the right track.

Here are my top 10:

1) Focus on goals

Why would we not have them?

Exploratory testing helps you exercise a system like a user while actively looking to identify bugs. having set goals will maximise the value of your testing and complement other testing methods.

2) Plan ahead

Following a script is not exploring the software. Exploratory testing stills needs an element of control so plan out what you want to achieve.

3) Don't over do it

Its not about coverage stats! it’s to find the defects and issues in a system that you won’t find through other forms of testing.

4) Is exploratory a skilled activity?


Exploratory testing ne…

Why Early Performance Testing?

I am currently working on one of the highest profile projects in the company at the moment and I am really trying my best to nail early performance testing!
So I’m not from a performance testing background. Historically I have passed this phase of testing on to the official performance tester(s). By doing this I have removed all responsibility! Or have I?
What I have actually done here is miss out on an excellent learning opportunity and completely missed the importance of gathering performance stats early on in the project.
Over the last couple of weeks I have done some work to understand our projects “Performance Route to Live” along with some support from our performance consultants for guidance.
“Do you understand the performance requirements?”
Here is a draft of what I have come up with so far:

In my opinion it is important to gain an understanding of how individual services perform early on to give us an indication and enable us to plan for later stages. This can be done as ear…

Telling Stories Is Hard. Telling User Stories Is Terrible, OR IS IT?

I'm sharing this article as I feel this is one area of the lifecycle my project team don't nail 100% of the time. I'm not saying we don't deliver quality I'm just stating that we could do better... Couldn't we all?
I disagree with one statement in this article though "Only developers are never to be in charge of user story creation". I don't feel there is any reason why anyone on a project team can't manage a story providing it's not done in isolation, you need collaboration to succeed.
It is quite easy to operate with a good user story both in development as well as software testing and quality assurance processes. Though mostly used in Agile environments user stories may be of great value to many software projects. I feel there is no need of defining true value of user stories so I will simply skip that part. Straight to the story creation we go.
Where do I begin? Oh, right, with users. A good user story does what? It is describing possible…

Why Software Testers Are Awesome!

I was searching the web to understand what people think of testers and what testers think of themselves! I think this sums it up quite well from a testers view... Basically we are AWESOME!

A team of testers had decided to make a list of the reasons why they are making people happy with the fact that they are software testers. So, here we go with our little marathon of test-awesomeness! So tell me, why do you love to be a software tester?

I’m happy that I’m a software tester as I’m the first one who gets to play with the newest and the coolest software! That is one of the best reasons in the world why one may ever dream of becoming a tester (especially a video-game tester), sadly I don't get t test video games but we can't have everything!I am always up-to-date. Software is constantly evolving, getting more advanced and complex, etc. So does testing. And so do testers as there are new challenges emerging every day. New platforms, products, OS’s. It’s like everything in testing w…