Skip to main content

What is a good Agile Tester ?

Its a good question!

Over the last couple of weeks I have read various articles highlighting what a good Agile tester is… all very good, but all very different!

"Testers are responsible for quality" No, no, no...

So the question is, what do YOU think a good Agile Tester looks like?

Here are my thoughts:

I strongly believe that a good Agile Tester is whatever it needs to be for a given project. Everybody within an Agile team has the same goal and requires continuous collaboration to succeed.

At the start of a sprint, an outsider looking in, should they be able to pick out who is the Developer, BA or Tester? I don’t think so. Everybody needs to be involved in defining things such as processes, user stories and acceptance criteria etc.

We all need to deliver value, we all need to continually look for improvements and we all need the ability to respond to change.

It’s only at this point that I see people doing specifics to their specific role, and for testers believe our main purpose would be:

·       Provide continuous feedback
·       To be creative
·       Think about the end user
·       Validate that all acceptance criteria has been met
·       Ensure that no testing has been overlooked
·       Continuous learning (Keep up to date with new tools & approaches)
·       Provide the business with confidence in the feature under test

Having the right tester mind set and an easy to work with personality is always a winner for me J

This is just a few thoughts, Hope it helps.


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 …