TestBash Manchester 2017

Testbash manchester adverts differently 2017 dojo events %281%29

TestBash Manchester 2017 - our annual our software testing conference t'up north was hosted at The Lowry on 27th October 2017.

All TestBash events aim to inspire and educate but in equal measure provide lots of opportunities for testers to meet, make friends and continue to build the amazing testing community that we have.

We hosted 250 software testers from across the globe, had 10 great talks, lots of awesome 99 second talks and plenty of socials!

We record all our TestBash talks and make them available on The Dojo. Some are free to watch and others require Pro Membership... get stuck in!

Join the discussion about TestBash Manchester over at The Club.

We would like to thank our TestBash Manchester 2017 event sponsors, CDL, Equal Experts, LateRooms, RentalCars and TestArmy for supporting this software testing conference and the software testing community.

If you would like to attend TestBash or any of our events then please check our latest schedule in our events section.

Watch all the talks from the event:
Event Sponsors:

Rapid Software Testing – Course Outline

  • Are you finding it difficult to assess how much time and effort you’re going to need to test effectively?
  • Are you overwhelmed by or uncertain about approaches to test planning, design and execution?
  • Are you working in an environment where some people aren’t following “the rules”?
  • Are you having trouble finding the right balance between planning, documentation, and testing?
  • Are you interested in learning skills and techniques that will help you to become a better tester?
  • Are you finding that “industry best practices” are infeasible and a poor fit for your organization?
  • Would you like to connect—or reconnect—with your passion for learning and discovering problems in order to defend the value of your organization’s products and services?
  • Do you want to get very good at software testing?

Developed by James Bach and Michael Bolton and taught by Michael Bolton, this 3-day, hands-on class introduces you to rapid software testing, a complete testing methodology designed for a world of barely sufficient resources, information, and time. Based on the principles in the book Lessons Learned in Software Testing: a Context-Driven Approach, this class presents an approach to testing that begins with personal skill development and extends to the ultimate mission of software testing: lighting the way of the project by evaluating the product.

The philosophy of rapid testing presented in this class is not like traditional approaches to testing, which ignore the thinking part of testing and instead advocate neverending paperwork. Products have become too complex for that, and testers are too expensive. Rapid testing uses a cyclic approach and heuristic methods to constantly re-optimize testing to fit the needs of your clients. Rapid testing isn’t just testing with a sense of urgency, it’s mission-focused testing that eliminates unnecessary work, assures that everything necessary gets done, and constantly asks what testing can do to speed the project as a whole.

One important tool of rapid testing we will cover is the discipline of exploratory testing– essentially a testing martial art. Exploratory testing combines test design and test execution into one process that finds a lot of problems quickly. If you are an experienced tester, you’ll find out how to articulate those intellectual processes of testing that you already practice intuitively. If you’re a new tester, hands-on testing exercises help you gain critical experience.

If you outsource development or testing…

We have taught this class at outsource firms in India on behalf of their clients so that they can do a better job of testing without needing detailed test procedures. But more importantly, the rapid testing methodology is about getting a lot of value for the testing dollar (value that simply can’t be reproduced by throwing untrained bodies at the problem) so that your top management won’t see testing as a commodity activity that any stranger will do as well as you. Even if you outsource, you may want to have a core team of testers back at headquarters who can rapidly test products to check the “testing” done by outsource firms.

If you are burdened with clerical requirements…

We have taught this class in organizations pursuing the CMM and organizations subject to FDA and other regulatory requirements. Rapid testing is about thinking. As long as they want you to think well and find important problems quickly, this is a class that applies to you. However, we do advocate a lean form of test documentation, to the extent you can possibly lean it. We also teach session-based test management, which allows you to measure and document exploratory testing in a manner compatible with more “formal” process cultures.

Want more detailed course outline?

Michael Bolton has a detailed course outline on his website.

Course Requirements

Please bring a laptop with you. Each computer must have an accessible USB port. Course content and software for the purpose of exercises will be installed on each system. The participants must have sufficient administrative rights to afford complete control over the entire system, including the capacity to install software.

Please direct questions and enquiries to hello@ministryoftesting.com

Michael Bolton

Michael Bolton is a consulting software tester and testing teacher who helps people to solve testing problems that they didn't realize they could solve. He is the co-author (with senior author James Bach) of Rapid Software Testing, a methodology and mindset for testing software expertly and credibly in uncertain conditions and under extreme time pressure. Michael has 25 years of experience testing, developing, managing, and writing about software. For the last 18 years, he has led DevelopSense, a Toronto-based testing and development consultancy. Prior to that, he was with Quarterdeck Corporation for eight years, during which he managed the company’s flagship products and directed project and testing teams both in-house and around the world.

Do you find yourself frustrated by the lack of challenge in your testing role, managing mountains of test cases, or increasingly aware of the bugs that slip through your net? Adopting Exploratory testing can help relieve these frustrations, but how do you go about performing ET in a way that is effective for both you and your team?

Join Dan and Mark for an interactive one day introduction to Exploratory testing where you will engage in discussions and exercises to learn about:

  • What Exploratory testing is
  • How to identify and organise your Exploratory testing activities
  • Techniques to help you generate test ideas during Exploratory testing activities
  • Test notes and reporting techniques

By the end of the day you will be able to conduct exploratory testing in a way that is:

  • Structured and well reported to support your team and stakeholders
  • Challenging and engaging for you whilst enabling you to test effectively and with speed

Attendees will also have the benefit of mentors. There will be a mentor per table of 5 students, really improving the support on offer. Add Dan and Mark back into the equation and you've got a great opportunity to learn about Exploratory Testing.

Dan Ashby
Danashby Dan is a SW Tester and he likes Porridge! (and whisky!)
Mark Winteringham

I am a tester, coach, mentor, teacher and international speaker, presenting workshops and talks on technical testing techniques. I’ve worked on award winning projects across a wide variety of technology sectors ranging from broadcast, digital, financial and public sector working with various Web, mobile and desktop technologies.

I’m an expert in technical testing and test automation and a passionate advocate of risk-based automation and automation in testing practices which I regularly blog about at mwtestconsultancy.co.uk and the co-founder of the Software Testing Clinic. in London, a regular workshop for new and junior testers to receive free mentoring and lessons in software testing. I also have a keen interest in various technologies, developing new apps and Internet of thing devices regularly. You can get in touch with me on twitter: @2bittester

Morning Sessions

We know that application security is important. We have to protect our customers' data and our employers' data while keeping our systems up and running. But do we have the skills and knowledge to meet that challenge?

During this workshop, we will begin to explore some of the concepts, skills, and techniques of security testing by working with a vulnerable web application. Through practical activities and hands-on learning, we will discover the key security issues that affect web applications today.

Testers will learn skills to identify software vulnerabilities and understand common threats and risks that occur in web-applications. We will also examine some of the tools and utilities that can enhance and extend security testing efforts. Let's look at the essential steps to build and execute your own security testing strategies. Let's examine how learning and mentoring can aid in the development of strategies. You can and should build up your own skills with integrated security testing. This will ensure ongoing relevance of your role in a security context, and the success of your organisations.

Building upon personal experience of integrating security testing into an existing organisation, incorporating DevOps, continuous delivery and integration, this workshop will highlight and discuss the reflections of learning from hackers, recent breaches and the socio-economic, political and technical impact upon software development organisations.

Attendees will take away a set of advice and techniques to incorporate and enable security testing into their day to day work, answering some of the questions that may arise around scope, skills, tools, models and learning.

Technical requirements:

This is a practical workshop, so all attendees will require a laptop, and the ability to install and run the application under test, as well as some open source tools that will be useful during the session. Installation instructions and a tool list will be sent before the workshop, and pre-installation is highly recommended for a smooth workshop experience.

Prior experience in security testing web applications is not necessary; however, attendees will need to be comfortable testing web applications and using modern web-browsers (i.e. Firefox, Chrome, Safari).

  • Understanding of key security risks, threats and vulnerabilities
  • Learn and practice security testing skills in a safe space
  • Development of the security mindset
Dan Billing
Unnamed %281%29

Dan Billing has been a tester for 17 years, working within a diverse range of development organisations, mostly in the south-west of England. He is now running his own consultancy, The Test Doctor, based near Brighton in Sussex. His passions in testing include mentoring, supporting and training members of the team to develop their security skills also.

Dan’s love of testing drives me to become an active member of the testing community, helping to organise local testing events and learning. He is also a co-host of the podcast Screen Testing, alongside Neil Studd.

Learn how to hire testers successfully and what to look out for through the interview process.

In this workshop we will look at the whole hiring process, from identification of a need to on boarding new people. Through inclusive and immersive exercises we will practice the key skills required in order to make hiring new people a success.

  • Identification of a need - do you need a new tester? Have you identified exactly what you require?
  • Individual and team context - are you hiring for a separate test team? A cross functional team? What’s the product or project?
  • Permanent vs contract recruitment and when it’s right to use either.
  • Selling yourself - How to make a job description that makes the candidate want to join you.
  • Ensuring that you take diversity into account when hiring, from job descriptions and adverts, all the way to on-boarding.
  • Where to advertise and how.
  • Getting the team involved and empowered.
  • Establishing recruitment pipelines before you need them.
  • What makes a good CV?
  • Telephone interview techniques.
  • Face to face interviews - traditional vs alternatives.
  • What to do once you’ve made the offer. How to get make sure the candidate you want actually starts, and stays.
Stephen Janaway

I’m Stephen Janaway.

I help people deliver software more effectively. Over the last 15 years I’ve worked in coaching, training and leadership positions in companies such as Nokia. Ericsson, Motorola and the YOOX NET-A-PORTER GROUP, as well as advising a number of mobile and e-commerce companies on development, testing and delivery strategies.

I have written and presented many times about software development, testing and delivery, frequently with a focus on mobile devices and mobile applications. I am co-curator of the Testing In The Pub podcast and organiser of West London Lean Coffee.

To test is to learn about a product, and to provide a story about what we've learned. Whether it's spoken or written, the testing story refers to the product and to the bugs in it and risks around it. A good testing story is far more than that, though. The product story is supported by a testing story—how you configured, operated, observed, and evaluated the product; what you've tested and what you haven't tested yet. The testing story is supported by a quality-of-testing story—why your testing is just what the project needs; or, if not, an account of problems that make testing harder or slower, and how such problems might be fixed.

In this class, we'll learn about composing, editing, narrating, and justifying your testing story. We'll discuss ways of collecting information and taking notes. We'll practice developing individual bug reports, session reports, and test reports. While we're doing that, we'll develop models and checklists for evaluating and debugging your testing story, and relating it to your clients.

Michael Bolton

Michael Bolton is a consulting software tester and testing teacher who helps people to solve testing problems that they didn't realize they could solve. He is the co-author (with senior author James Bach) of Rapid Software Testing, a methodology and mindset for testing software expertly and credibly in uncertain conditions and under extreme time pressure. Michael has 25 years of experience testing, developing, managing, and writing about software. For the last 18 years, he has led DevelopSense, a Toronto-based testing and development consultancy. Prior to that, he was with Quarterdeck Corporation for eight years, during which he managed the company’s flagship products and directed project and testing teams both in-house and around the world.

Afternoon Sessions

“Build Quality In” and “Quality is a team responsibility” are something you hear a lot when working with agile teams, particularly those moving to a continuous delivery model. But if we don’t know what quality is, how can build it in? How can everyone be responsible for it? How can we test for threats to quality?

How does your organisation understand what quality is , what it looks like and importantly what it looks like to your stakeholders? How do you turn something as subjective and philosophical as Quality into something tangible that people can act upon?

I was faced with this exact problem at one of my clients. I devised a workshop to help them work through what Quality meant for them.

Running a Quality Workshop requires some simple tools and a process. You can read that here. What this workshop does is workshop take you through the nuances of running such a workshop, and allows you to explore how to run the workshop in detail giving you the confidence to run a Quality Workshop at your work.

We will also look at how we can make the workshop actionable and reviewable throughout software delivery.

Join me for a fun and lively workshop on how to workshop quality!


  • Definitions of Quality and why they are important
  • Logistics of running a Quality Workshop
  • Skill to run the workshop at your workplace
  • Solve challenges specific to your workplace

Anne-Marie Charrett

Anne-Marie Charrett is a software tester, trainer and coach with a reputation of excellence and passion for Quality and the craft of software testing.

An electronic engineer by trade, software testing chose her when she started testing protocols against European standards.

Anne-Marie advocates a whole team approach to Quality. She sees software testing as a skilled activity that many might perform. She trains & coaches teams to help embrace this approach to quality with a contextual mindset.

In the past, Anne-Marie has developed software testing courses and lectured at the University of Technology, Sydney, and ran the Sydney Testers Meetup.

Anne-Marie is available for work through her company Testing Times where she offers consulting, training and coaching services.

APIs (Application Programming Interfaces) are becoming ever popular recently, particularly with the use of devices connected to the Internet of Things. It can be extremely useful for a tester to understand APIs and how to test them because they can test earlier and also more efficiently than testing predominantly through GUI (Graphical User Interfaces) such as websites or mobile apps. However, not everyone has the technical background to pick up technical subjects such as APIs.

This workshop aims to provide a fun and interactive way of learning what APIs are and how to test them. The workshop is specifically aimed at people with little to no experience and knowledge of APIs. I will provide a simple game that can only be interacted with through API endpoints, initially controlling a robot to navigate a room to a goal. They will learn to use Google Postman to interact with the API - making it relevant for work as they learn to use Postman.

We will start with a simple game that teaches the basic concepts of HTTP and status codes before moving on to more complex games that teach data types, authentication & authorisation, JSON and XML, REST and as a stretch goal - automation.

Matthew Bretten
Portrait %281%29

Matthew has been testing software for 7 years, starting as a video games tester and is currently a Test Team Lead. Having graduated in Computer Games Technology, he originally wanted to become a developer but quickly discovered a deep passion for testing. His career has followed the trend of the software industry, going from testing a long distance away from developers and code to pairing with developers and helping them test as they write code. Along the way he has gained a great variety of experience testing telephony exchanges, analytics systems, websites, video games (including motion controls, 3DTVs, augmented reality) and mobile apps.

Through this background in computer science and his experience as a tester, Matthew is keen to help breakdown technical subjects and jargon for testers and expand their arsenal of test techniques!

We believe that the future and magic of testing lies in the individual quality and mind-set of testers. Their unique, non-linear and detail-oriented expertise should be the number one priority in creating test-minded teams. Although we frequently hear about testing as being under threat, we believe that we all have a unique opportunity to design a culture of testing by sharing what makes us all love this field, what it offers and how other disciplines can contribute.

We address the continuing growth of the testing discipline, its multiple facets and the engagement of the whole team. Through sharing our personal journeys at Rabobank, and inviting others to share theirs, we offer a roadmap on how to decide upon the next steps in your own testing journey.

In our workshop, we focus on co-creating the roadmap with participants to visualize their journeys. Through a series of exercises, participants share their anecdotes, stories and ideas for shaping the future. Our goal is to enable participants to reignite interest in the future of testing for themselves and for their colleagues and (re)discover what fascination this role truly holds.


Attendees leave with a renewed enthusiasm for sharing their testing stories, remember what made them fall in love with this job in the first place and bring their roadmap back to their department to continue the conversation with their teams. They feel a sense of ownership and inspiration to advocate what added value testing and testers truly bring.

  1. Individual quality and mind-set will be the primary focus going forward.
  2. Your role in designing the next step in the evolution of testing.
  3. Your testing role is yours to create
Marianne Duijst
Marianne duijst Marianne Duijst works as an Agile Quality Coach at Sogeti, and held previous roles as a Tester, Software Engineer, Scrum Master, Developer and High School Teacher. She is a frequent speaker at testing conferences around the world and enjoys speaking about critical thinking, work culture and being a Girl Scout. She often sketchnotes to share and learn. Her love for IT and the Testing profession comes from a love for puzzles, logic, and structure mixed together with her creative, writing and crocheting mind. She loves to explore, meet people from different countries and cultures, read voraciously and dream outrageously.
Rick Tracy
Rick tracy

Rick is an avid Test Philosopher, always up for a good debate, discussion or exploration of the many facets of Testing and Software Development in general. He works at Rabobank WRR Finance in the Netherlands and has done development, testing, requirements analysis, Agile scrummastering and test coordination there for 5 years. When not testing, discussing, or listening at conferences and events, Rick enjoys writing his (one day to be published!) novel, sword fighting and cuddling his outrageously adorable cats.

Many of us have heard the phrase ‘Quality is a team responsibility’ meaning instead of quality being owned by one person (typically a tester) it’s something that many are responsible for. But what does the word quality mean for you, your team and importantly for your stakeholders? Is it simply another word for testing, or is there more to Quality than we think? Does it matter if we understand Quality or not?

This talk explores the importance of understanding quality in the context of a contemporary engineering practices such as Extreme Programming, CI/CD and Devops. When quality is owned collectively, it can facilitate testability and shift testing closer to the design process.

Do I believe testers have a place in this future? Absolutely! In fact, I think the role of a tester is needed more now than ever but perhaps not in a way we have traditionally seen our roles.

A must for anyone moving to contemporary engineering approaches.

Key takeaways from this talk:

  • Learn how testing fits into quality
  • How testing might fit into contemporary engineering practices
  • A way to have a conversation about quality at your workplace

Anne-Marie Charrett

Anne-Marie Charrett is a software tester, trainer and coach with a reputation of excellence and passion for Quality and the craft of software testing.

An electronic engineer by trade, software testing chose her when she started testing protocols against European standards.

Anne-Marie advocates a whole team approach to Quality. She sees software testing as a skilled activity that many might perform. She trains & coaches teams to help embrace this approach to quality with a contextual mindset.

In the past, Anne-Marie has developed software testing courses and lectured at the University of Technology, Sydney, and ran the Sydney Testers Meetup.

Anne-Marie is available for work through her company Testing Times where she offers consulting, training and coaching services.

Psychology is the science of mind and behaviour. Since the mind is every tester's most important tool and behaviour is the main driver for development, studying psychology should be a natural part of our strive for testing excellence.

In this session, we will look at some psychological subjects with scientific theory accompanied by storytelling from real-life experiences.

Topics covered include:

  • Biases and how they can play tricks with our perception
  • The effect of personality traits on behaviour and communication
  • Why metacognition is important to a tester
  • How knowledge of the dual process theory can be useful
  • Developing skills by training and education


Hopefully the attendees will learn something new about how the mind works, how it affects our behaviour and how this knowledge can be useful in testing. Also, I hope the people attending will get more interested in the science of psychology.

Göran Kero

Göran is a context-driven tester and an agile enthusiast who is always curious about learning new things. He is passionate about finding out what the customers really need and find ways for customers and developers to have better cooperation and interaction.

I have been diagnosed with anxiety. It means doing my job is difficult - fear of confrontation + imposter syndrome over a layer of constant worry is not ideal for a tester. Giving unwelcome news or information is never a fun time, especially when you're anxious about you're performance and skills, and being blamed for rocking the boat.

However, I have used some of the techniques taught to me in therapy to help me become a better tester.

The talk covers anxiety and how it affects me, then:

  • Focus/defocus and mindfulness
  • Note taking and how writing things down can be powerful
  • Responding vs. reacting and fight vs. flight
  • Empathy, and kindness

Each of these can help with testing regardless of mental health status, and I'll talk through how these work. I'll also flag how these can be used to monitor your own mental health, so you can keep yourself mentally healthy as well as physically healthy.

Gem Hill
Xr3kqjjw 400x400

Gem is a web tester, podcaster, and all round geek, living and working in Manchester.

She works at a digital agency, mostly testing Drupal sites (though she occasionally dabbles in Magento).

She has two podcasts, one about testing (Let's Talk About Tests, Baby), and one about mental health (Inner Pod). When she's not doing that, she's baking, reading comics, or going to the cinema.

Aging in technology can be an interesting and humbling experience. We might have significantly more experience in software projects than many of our colleagues, however as the years go by, it can feel like there is just less energy for pursuing individual learning opportunities... even when the desire and passion is still there. I remember reading Kent Beck’s extremely vulnerable and moving “Me an’ Algernon” last year, and found myself pausing to consider what it is that I contribute to the companies I work with. I have determined that it is my coaching and teaching experiences that are the key events that have effectively defined my career. They have helped me reach a place where I truly feel that I am now best contributing to software… even as I slowly creep closer to that magic number 50.

In this talk, I hope to share some of these life changing experiences, and describe what I have grown to believe is a very real need for apprenticeships in software testing: nourishing a life of learning through the support of compassionate benefactors. I will share some stories of the people who have deeply impacted my life, and in turn have taught me to share all that I know with those who now pursue levels of knowledge that I could never have achieved on my own.

The questions I will ask…

  • Is this a mission that should fall upon us as we age in technology?
  • Do we have an obligation to invest in, and build long term interests in our colleagues’ development?
  • How might we best ensure that they not only learn from us personally, but that we also assist them in identifying and accessing the subsequent paths for learning and career growth?

This goes beyond the notion of mentoring. The history of apprenticeship has existed ever since craftsmanship and skill carried any worth in society. Ensuring skills and knowledge were passed on to (and evolved by) future generations required consistent, supported investment by a guild’s most talented masters. But the essential phase of practicing journeymen rarely gets mentioned. It is here where we learn to not just apply our learnings, but also learn how to take an interest in the growth of others and pass on skills. Perhaps it is here where we need to focus our responsibility, and to learn how to foster the evolution of our beloved craft of testing. If so, where do we begin?

Martin Hynie

With over fifteen years of specialization in software testing and development, Martin Hynie’s attention has gradually focused towards embracing uncertainty, and redefining testing as a critical research activity. The greatest gains in quality can be found when we emphasize communication, team development, business alignment and organizational learning.

A self-confessed conference junkie, Martin travels the world incorporating ideas introduced by various sources of inspiration (including Cynefin, complexity theory, context-driven testing, the Satir Model, Pragmatic Marketing, trading zones, agile principles, and progressive movement training) to help teams iteratively learn, to embrace failures as opportunities and to simply enjoy working together.

Turning Good Testers Into Great Ones - Metacognition and what it can do for your testing.

According to my favourite definition of testing, a tester learns everything there is to know about the software in order to help improve both the product and the user experience.

Therefore, there are many learning strategies, like inquiry or problem based learning, which can make testing even better. One learning process which can turn a good tester into a great one is metacognition. As metacognition helps you to focus more on your own learning.

Metacognition is the reflection on cognitive functions such as learning, thinking, understanding and memoizing. There are many metacognitive strategies in learning sciences under the categories of planning, monitoring and rating.

Metacognition helps set awareness of the ongoing learning process and of its true results. The same awareness could help improve your testing skills. In my current project we discussed the different metacognitive strategies and used them to improve our testing, like focusing on what we learned in the last test session and what we still do not know.

So, what am I going to talk about in this session:

  • What is metacognition
  • Which metacognitive strategies are there?
  • How can these metacognitive strategies improve your learning?
  • And even more important how can they improve your testing (with project examples)


The attendees get an impression what metacognition is and how it could improve their testing and learning in general. I will explain certain strategies and combine them with examples of learning as well as what we have done in our project.

Vera Gehlen-Baum
Vgb ny

Vera finished her PhD in 'Learning with new media' in 2015 and started as a Requirements Engineer at QualityMinds right after. Her first project was to test a medical software and to improve the whole testing process - starting from the requirements. In this and other ongoing projects, Vera can facilitate several of her passions: combining well-researched learning theories with requirements and testing.

With automation rapidly becoming more a important part of any testing process, teams rely ever more on the result of their automated tests as an indicator of product quality. In moving towards a Continuous Delivery or Continuous Deployment model, automated tests are often the only gatekeeper before software is put into production. But can automation be trusted enough to play this important role in the software development and delivery process? And what can you do to make sure your automation can be trusted enough to be relied on?

In this talk, we'll take a look at the relationship between trust, confidence and test automation. We'll see a number of ways in which test automation can deceive you, how trust in test automation is lost and how you can build tests you can trust on.

  • Need for confidence in workings on application under test + application is (partly) tested in an automated manner = Automated tests need to be trusted
  • Don't trust automation blindly, as its results can be deceptive
  • Trustworthy automated tests can be created and maintained by applying good development practices (reviews, testing) to automation
Bas Dijkstra
Bas %281%29

I'm an independent test automation consultant with over 10 years of experience helping my clients improve their testing efforts through smart application of tools. A typical work week for me consists of a mixture of coding, consulting, writing and teaching, which is just the way I like it.

I love to unwind by going for a run or sitting down with a book and a glass of wine. I live in Amersfoort, the Netherlands, together with my wife and two sons.

What is exploratory testing? As with so many things in testing, there's a lot of confusion around the concept. For years, exploratory testing was dismissed by some as "ad hoc", "undocumented", "unstructured", "experience-based". Others talk of exploratory testing in terms of chartered, time-boxed sessions. Still others wonder how exploratory testing fits with Agile, Scrum, and DevOps. Is exploratory testing is manual testing? How can you use it to test an API, or software as a service?

In this talk, Michael Bolton will offer the Rapid Software Testing perspective on exploratory testing. He'll trace some of the history of ideas about ET, dispel some common misunderstandings about it, and show how exploratory work is woven through all of your testing.

Michael Bolton

Michael Bolton is a consulting software tester and testing teacher who helps people to solve testing problems that they didn't realize they could solve. He is the co-author (with senior author James Bach) of Rapid Software Testing, a methodology and mindset for testing software expertly and credibly in uncertain conditions and under extreme time pressure. Michael has 25 years of experience testing, developing, managing, and writing about software. For the last 18 years, he has led DevelopSense, a Toronto-based testing and development consultancy. Prior to that, he was with Quarterdeck Corporation for eight years, during which he managed the company’s flagship products and directed project and testing teams both in-house and around the world.

Accessibility is often the 'last mile' of web development. If the client/project sponsor won't pay for it and there's not enough time to squeeze it in, it probably won't get done. Even when accessibility is included in a project, it can sometimes feel like a box-ticking exercise. It doesn’t have to be that way!

In this talk, you’ll learn about the disabilities that affect how people can use the web, and the key building block needed for an accessible website. James will also introduce some tools and approaches for quick and effective accessibility testing. Finally, James will provide some business justifications and real-world context to help you advocate accessibility to colleagues and stakeholders.

  • Awareness of disabilities that can affect individuals' ability to use the web.
  • An understanding of the key concepts of accessibility and how they apply to the web.
  • An overview of free accessibility testing tools that are easy for beginners to use.
  • Business justifications for accessibility (and accessibility testing).
  • Suggested follow-up actions to help attendees introduce accessibility (and accessibility testing) to their own organisations.
James Sheasby Thomas
Img 3216 cropped

James Sheasby Thomas is an an agile web and mobile tester for Inviqa, a major open source technology partner based in the UK and Germany. After starting his career in digital marketing and communications for a software company, he made the switch to the hectic world of digital agency testing in 2014 and has never looked back.

James specialises in cross-browser/device testing and exploratory integration testing, and has a burning passion for usability, accessibility, tool-assisted testing and agile methodology (particularly Kanban). Since joining Inviqa he has worked closely with developers, PMs, AMs and clients to help facilitate a move towards Continuous Delivery and a truly collaborative QA process.

Outside of the 9 to 5 he spends as much time as possible in the countryside, museums, cafes and local breweries.

"I've just got where I am though luck!"
"I'm going to be found out at any moment!"
"I don't deserve the success I've achieved!"
"I'm a giant fraud!"

These are all pretty common thoughts someone suffering from Impostor Syndrome might have. I hear Impostor Syndrome mentioned frequently as something common in our industry, but hadn't even heard of it until a couple of years ago. It's something a lot of successful and really intelligent people suffer from. It's effects can be debilitating, and it shouldn't be dismissed as non-existent or unimportant. We need to acknowledge it, talk about it, and make it ok for people to admit they are affected by it.

I'll talk about how my own feelings of Impostor Syndrome have affected me throughout career, even when I didn't know what it was, what I've done to manage these negative feelings, and how it's enabled me to start making a positive contribution to the testing community.


  • An understanding of why people suffer from Impostor Syndrome and what it feels like.
  • If you suffer from Impostor syndrome, you aren't alone.
  • If you suffer from Impostor syndrome, it isn't a sign of weakness.
  • If you suffer from Impostor syndrome, you can manage it, and do amazing things.
  • If you don't suffer from Impostor syndrome, it doesn't make you arrogant, or a narcissist.
Claire Reckless
Img 3158

Claire is a Test Lead at MoneySuperMarket in Manchester, with prior experience in testing Financial and Security software.

A tester for over 10 years, she is active within the testing community, contributing articles, speaking at conferences including Testbash Manchester and Nordic Testing Days, as well as co-hosting Software Testing Clinic Manchester every month.

I would like to talk and share my experiences about testing microservices. Why I like it, why it scares me, where we went wrong and things we have done as a team which I am proud of. I feel there is a big change happening for a lot of software companies, to turn their big monolithic application into a bunch of smaller services which are easier to manage.

I am not the most technical of testers and this change in my team felt a bit daunting to me, however I felt like I learnt a huge amount in this time and I would like to share my experiences. I would like to talk about how it helps you understand the internet and how web applications work (especially the one you are testing!), how it can improve your coding skills (by adapting new methods that require more coding, such as service level testing and mock servers) and how everyone involved (Devs, QA, Users etc..) can benefit from microservices (and sometimes suffer!).

  • Basic principles of having a microservices architecture (pros and cons)
  • Basic principles of the testing pyramid and how this can be applied
  • Testing techniques that will help in a microservices architecture
  • Things to avoid and things to remember when testing microservices
Simon Dobson

I am a computer science graduate from the University of Nottingham and I am now living and working in Barcelona. Having spent some time working for a technology consultancy in London I decided to jet set and get stuck into a product based company in the shape of Typeform.

I started out as a manual tester and learnt the mindset of a QA while taking the ISTQB certificate. I soon found automation and found a passion for creating the best test suites possible! After using Selenium in a number of different projects I am now more focused on back end and API testing.

Aside from technology I like to play and watch sports, especially football!
Micro Sponsors: