Skip to main content

Why Exploratory Testing Should Be Part Of Your Process!

Essentially testing is an exploratory task...
Exploratory testing is a structured process of investigating an application by learning and understanding its use, features, and operation in a series of logically constructed but ad hoc tests.  By itself, exploratory testing can be useful, but when combined with other testing practices, it can be a powerful way to better understand the application, build more and better functional tests, and ultimately increase product quality.
Exploratory testing can take many forms.  A tester might methodically execute a series of transactions as a user might do, recording the results and looking for discrepancies or inconsistencies.  Or the tester might perform a series of actions that a real user would never do, such as press the return key multiple times or type nonsensical data into a field.
The goals of exploratory testing also vary.  In some cases, it serves as a final reality check on the quality of the software before determining whether or not it is ready for release.  In others, it serves as a beginning point, an analysis of application strengths and potential weaknesses before beginning formal testing.  Ideally, it should be used throughout the testing process, alternative with other forms of testing to provide a high level of different types of interactions with the application.
The tester starts exploratory testing with one or more of these goals in mind.  Exploratory testing is typically a relatively quick process, usually taking a few hours to a couple of days, so that a tester can quickly find useful information for a decision on further testing or release strategy.
Depending on the goals of specific testing processes, exploratory testing can initially provide testers with domain and operational knowledge of the application, along with determining areas that might require additional functional tests.  If you can automatically record explorations, they can also be easily turned into functional test scripts, which support the traditional testing process.  Eventually, exploratory tests can even be automated.  
I will talk more about exploratory testing in future posts as I am keen on defining this for myself.

Comments

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 …