TestBash Brighton and the Evolution of Testing

TestBash Brighton 2017 (testing conference) logo

TestBash Brighton 2017 logoIn March 2017 I attended TestBash Brighton. Despite being a long-time fan of the Ministry of Testing (as well as their busy Testers’ Slack), I’d never been to any of their events before. I expected an enjoyable and engaging day, and I was not disappointed! Both speakers and attendees were friendly and approachable, and each talk was directly relevant to my role at Inviqa. Above all, attending TestBash feels like joining a ready-made community for a day. From the pub drinks the night before, to the board games at the end, it felt like I’d known my fellow attendees for years.

A key thing that struck me was that there seemed to be a unifying theme to all of the talks. This theme wasn’t explicit or predetermined, but revealed itself as the day unfolded.

Continuous Delivery and the evolution of QA

If you follow me on Twitter, you might have noticed that I’ve already blogged about this conference on the Inviqa blog. In that post, I reflected on Amy Phillips‘ Continuous Delivery talk and how CD was changing the way that Inviqa’s QA team operates, both as individuals and in partnership with colleagues in other roles. Here’s a little snippet of that post:

QA has always been a bottleneck – most teams have more developers than testers / QAs – but on CD projects that bottleneck has the potential to become even more pronounced.

One solution to this problem is to add more QAs to the project, but another option is to get other team members involved in your testing. Testing is a job role, but it’s also a skill that can be taught to others fairly quickly.

On my projects at Inviqa, I’ve had success with asking developers and PMs to help me set up environments ready for testing, explore specific edge cases, and document the implementation details of a feature that’s ready for UAT.

This is especially helpful when deadlines are tight or the tickets are piling up in the QA column, and it fits well with the collaborative nature of continuous delivery projects. More importantly, by teaching our colleagues about testing we can help to spread quality throughout our teams and the organisation as a whole. This fits in well with the ‘shift left’ theory of QA, where quality is a key component of each stage of the process.

Check out the full post for my thoughts on the changing role of Testing/QA in a Continuous Delivery context. Some of this post was left out for length reasons, so I’ve put it here instead.

Pick-your-own testing career

Del Dewar gave a talk titled ‘Step Back to Move Forwards: A Software Testing Career Introspective’. He shared his reflections on his own career and how the world of testing has changed during this time. Many experienced testers will have treaded the path of Tester > Lead Tester > Test Manager during their careers. Over time these role distinctions have become less relevant and many more niche roles have sprung up in between.

In organisations with agile, self-organising teams, traditional role expectations may become outdated. A tester’s day-to-day responsibilities may also bear little relation to their job description. The key message I took from this talk is that testing has become such a broad church that we, as testers, must forge a career path to suit our own skills and the needs of the organisations we work in. Sticking to the old role archetypes and expectations of what a tester does/doesn’t do simply won’t cut it anymore!

Reimagining test strategy

Another of my favourite talks, ‘Rediscovering Test Strategy’, was given by the aptly-named Mike Talks. Like Del, he reflected on how testing has drastically changed during the course of his career. In the past 20 years, systems under test have evolved from standalone programs that ran on a single platform (i.e. Windows) to complex, connected and multi-component software. Modern software runs on a seemingly infinite combination of operating systems, hardware form factors, browsers, screen sizes etc. This increase in complexity has also largely resulted in a shift from explicit, repeatable test cases to exploratory and constantly evolving testing approaches. However, the move towards exploratory testing doesn’t remove the need for effective test planning. Mike shared his tips for developing test strategies, including looking at the bigger picture, capturing lots of ideas and identifying weak points to focus on.

AI and Testing: prostheses for human behaviour?

My final highlight among so many excellent talks was Professor Harry Collins, Professor of Sociology at Cardiff University and author of – among many other publications – Gravity’s Kiss, the story of the discovery of gravitational waves. He gave a riveting lecture on the commonalities between software testing and artificial intelligence. He also shared his thoughts on the importance of testers in shaping the future of AI.

Professor Collins pointed out that all software is a prosthesis (or model) of human behaviour. In the same way that a prosthetic leg can never work exactly like an ‘organic’ leg, a computer program can never be a perfect reproduction of the same function performed manually by humans. However, this isn’t necessarily a bad thing; if designed well, computer programs can perform specific tasks many times more efficiently than a human can. This frees us up to focus our attention on other things that cannot (yet) be automated.

Collins’ talk also helped me to think about the way I design my own testing. If we consider a test (manual or automated) as an imperfect model of human behaviour, we can use this knowledge to identify weak points and areas for improvements in our testing. This insight could lead us to change our testing approach in order to better match user behaviour.

But wait – there’s more!

The above highlights represent less than half of that day’s brilliant speakers – there were also talks on ethics and testing, API testing, tool-driven testing and running a startup. David Christiansen, a tester-turned-developer-turned-CEO, gave an insightful talk that helped us to consider how testers can be more mindful of the strengths and weaknesses of the developer mindset. As I alluded to in the introduction of this post, all the talks seemed to converge on a single theme – the evolving role of testers in the fast-paced world of software development.

One thing I love about conferences is the buzzy feeling that you get when it’s all over. You might be bursting to try out the new technologies or approaches that you’ve just learned about. Or perhaps a talk has helped you to think differently about a challenging situation you’ve encountered at work? It’s rarely possible to remember everything you learned or to try out every new tool you’ve discovered. Nonetheless, the right mix of talks and fellow travellers can help you to synthesise your own work with the wider community.

Shameless plugs

If you’ve never been to a TestBash before, then hopefully this post gives you an idea of what it’s like. I really enjoyed my time in Brighton, and it inspired me to apply to speak at future TestBashes. I was therefore thrilled to be invited to give my Accessibility Testing Crash Course talk at TestBash Manchester in October! Please do take a look at the event if you’re interested, browse their full event calendar, or even apply to be a speaker. If any of those talk summaries tickled your fancy, you can also find videos for all of TestBash Brighton’s talks at The Dojo.