Search This Blog

Independent, Punk, Leeds Testing Atelier IV

On Tuesday 9th May 2017, we did it again, the fourth iteration of the Testing Atelier rocked the mighty city of Leeds.

We try to do things a little different.

Our venue Wharf Chambers is different, a community run venue rather than stuffy conference halls or meeting rooms. We wanted to present a different type of event too as many testing conferences are mainly testers talking about testing that testers do. We wanted to show testing as an activity though, something that all roles do in their own way and how those fit together. To this end, we sourced speakers, workshop facilitators and panelists from loads of roles, developers, ops, build engineers, product all contributed. In fact we had pretty much a 50/50 split between testers and other roles. Winning.

As well as having more from all those roles who have a stake in testing as an activity, we had:

More focus on understanding issues that are changing our testing lives, including DevOps and Continuous Delivery techniques, in order to realise that testing is often enriched by new patterns for software development.

More gender diversity than before, 40% of speakers, workshop facilitators and panelists identified as female, an improvement on 20% for Atelier III. More diversity, more viewpoints, more understanding, better relationships, better decisions and different thinking.

More sponsors enabling us to do more for our attendees, more media (thanks to Codera for helping us out) and more swag (again, thanks to Skelton Thatcher and Ministry of Testing). Infinity Works, Ten10 and Chris Chant kept the bar stocked and bellies full of pizza, a crucial part of the day.

Anyway, I think this tweet summed up my feelings for the day, quite nicely:

Post a Comment

Popular posts from this blog

One area that testers might be able to enhance their contributions to software development teams is how we perceive and contribute to unit testing. I believe testers busting their own illusions about this aspect of building something good would bring us much closer to developers, and help us realise what other layers of testing can cover most effectively.

Also, I want to do a talk about it, so I figured I would test the premise, see if potential audiences were into it. I put this on Twitter:Working on a talk about what testers might believe about unit #testing & how we interact with developers creating unit tests. Any challenges/additions for my list below? #development#agilepic.twitter.com/4oT5HE4qs3 — Ash Winter (@northern_tester) December 19, 201730 replies with ideas tends to indicate that people might be into it. The ListI thought, as my final blog of 2017, I would provide a super useful list of the myths and legends we as testers might believe about unit testing:That developer…

Thank you Reddit, while attempting to find pictures of the earths core, you surpass yourself.Turns out Steve Buscemi is the centre of the world.

Anyway. Lets start with something I hold to be true. My testing career is mine to shape, it has many influences but only one driver. No one will do it for me. Organisations that offer a career (or even a vocation) are offering something that is not theirs to give. Too much of their own needs get in the way, plus morphing into a badass question-asker, assumption-challenger, claim-demolisher and illusion-breaker is a bit terrifying for most organisations. Therefore, I hope the wheel is a tool for possibilities not definitive answers, otherwise it would just be another tool trying to provide a path which is yours to define.

In part one, I discussed why I had thought about the wheel of testing in terms of my own motivations for creating it, plus applying the reasoning of a career in testing to it. As in, coming up with a sensible reflection of real…

I've only had to quit two jobs to finally find the time to finish this blog series. Winning at life. If you need reminders (like I did) check out Part 1 and Part 2 before reading on...

After the first two blogs regarding the Wheel of Testing, I was delighted to receive a few requests for the wheel itself, which got me thinking about applications of it, beyond what its original intent was, which I've explored in detail in part 1 of this series of intermittent blogs. Most models need a little air time to show their value, in software development we crank out models all the time, but I'm not sure how many get used. I am inspired by models such as the "Heuristic Test Strategy Model" by James Marcus Bach, as I have used it and seen the benefits it has brought for my clients, particularly the ability to ask questions. So, I wanted to create a model which has a number of use cases, both real and imagined: