Skip to main content

Exploratory Testing Poster Attempt!!!

Over the last couple of months I have had a number of team session relating to Exploratory Testing.

We wanted to create a poster that contained information about the following:
  • Session based
  • Key elements
  • Structure to exploring software
  • Where does exploratory fit
  • What to think about when exploring software
  • Small section on the benefits of paired testing
  • Tools to assist exploratory testing sessions
  • Bug clustering
  • Reporting/Auditing

So, I have done just that!

The main aims of this poster is to spark conversation within project teams about how/what you do when exploratory testing, it’s high-level ideas! There is no reason why you cannot create your own. I am NOT saying this is how you will do exploratory testing its more of an ideas framework equipped with some context for the wider stakeholders…

Here is my first attempt:

Exploratory Testing Framework Information

Our Principle: Exploratory testing is an approach to software testing that is concisely described as simultaneous learning, Test design and test execution. We learn continuously, we design better tests from our continuous learning and we learn from the results and use them to make better tests.
We pick a test type, technique, method & level given the project context and information objective
The context of your exploratory testing will change depending on the risk, issues, and assumptions and the product under test

Session Based Testing: Session-Based Testing is a method used for measuring and managing exploratory testing. Sessions range from 15 minutes to 1 hour and will be focused around a ‘Charter’ which outlines the main purpose for testing. 

During a session, the tester will use a ‘Session Sheet’ to detail things such as the charter, test notes, issues and bugs (amongst other things). This session sheet will then be stored for future use as testing evidence as well as a point of reference should similar charters be tested (e.g. different charters under the same user story).

Rapid Reporter is a tool used to generate the template for a session sheet.

Paired Testing:  A software development technique in which two team members work together at one screen to test the software application.
Pairing can be between a tester and any other member of the team e.g. Product owner, developer, business analyst.
The benefits include mutual learning, ability to get a quick review of bugs/features, mentor new testers/team members, able to get a different point of view on the product, increased coordination. FUN FUN FUN.

Key Elements: We can all agree that freedom is a good thing. For example; painting your face and shouting “freedom!” can feel really good.
With greater freedom comes greater responsibility. When you are given the freedom 
To do things your own way it is up to you to spend that time wisely. 

Exploratory Testing Structure: Exploratory testing is an approach to software testing that is concisely described as simultaneous learning, test design and test execution, we learn continuously, we design better tests from our continuous learning, we learn from the results and use them to make better tests.

Where does Exploratory Testing Fit:

What should we be thinking about: Oracles: are a heuristic principle or mechanism by which you recognise a potential problem

Heuristics: is a fallible idea or method that may help you simplify and solve a problem

Mnemonics: Are a mind memory and/or learning aid. Mnemonics rely on associations between easy-to-remember constructs which can be related back to the data that is to be remembered.

Bug Clusters: Many testers have observed that defects tend to cluster. This can happen because an area of the code is complex and tricky.
Testers will often use this information when making their risk assessment for planning the tests, and will focus on a known area called a 'Hot spot'.
Tester can focus on the same area in order to find a larger number of defects. It will reduce the time & cost of finding defects as by focusing on certain areas more bugs can be found in order to improve quality of the software.

Tools to help: We have listed a good number of tools, these will aid in some way your exploratory testing. Take a look at them and make your own decision on the uses for them.


Popular posts from this blog

My Testbash Brighton 2017 Notes

This was my second Testbash... if you ever get the chance in the future these conferences are a must!
I took copious amounts of notes from the 9 talks and tried to highlight my key takeaways here... hope they make sense but please comment if you have any questions :-)
Amy Phillips - Continuous Delivery
A survival guide to joining a fast paced environment/project…
Where does testing fit within Continuous delivery:

As highlighted, basically from start to finish…
There are lots of things we can do when joining a project that is using Continuous Delivery but one of the main points from this talk was to do your research! There should be an element of "Continuous" in every aspect of the project.
·Learning the ling, what's the difference Continuous Delivery, Continuous Deployment, Continuous Integration, Continuous design, Continuous Improvements etc.? ·Understand what your role in the project is going to be ·Understand the teams values, What's going well and maybe what the team p…

Is TestBash an Invaluable experience?

Over the last few years, I’ve attended four single track conferences at TestBash Brighton and Manchester. Most recently, September 2018 and April 2019.

One of the most common questions I get after the conference is, Was it worth it? Especially now given, I’m a contractor, and I attend at my own expense.

In short, Yes It’s definitely worth the trip!

That leads me into my question; does a single-track conference work for me, or could I get more out of TestBash?

Of course, there are pros and cons, some talks may not be as engaging, but this is no disrespect to the speakers, for me, it’s because I probably favour certain subjects and I’m pretty sure others will think the same.

Do I make the most of what’s on offer at TestBash? It pains me to say, No! I don’t make the most of the events leading up to and post the single-track conference so I could get more from the week.

TestBash offers master classes on automation. A full day of workshops. Test.bash() with talks on automation and technica…

The way we work shouldn’t be ‘Alien’ anymore, Should it!?!?

It’s been a good while since I have written anything (Mainly because I’m not that good a writer) but given my 16 months in the public sector I thought it was time… 
For a good number of years now the DevOps trend has given rise of buzzwords and methods aiming to speed delivery and it’s now an assumption of mine that most organisations are au fait with the term ‘Continuous Delivery’.
I was wrong…
Within the organisation that I am currently placed I believe I have a high-functioning collaborative team who work flexibly and in continuous cycle. We also involve the users which is a huge benefit to the development teams, but that’s not saying we get everything right 100% of the time! Teams must continue to learn and evolve to remain productive.
Our team work in one of several delivery groups and with this comes multiple challenges; Silos No single environment strategy lack of communicationsVaried ways of working.  And thats just to name a few, which is interesting when all delivery groups …