TestBash Netherlands 2018

TestBash Netherlands was back for the second time on 13th April 2018. It was a fun-filled and jam-packed day with plenty to learn, much to take home and many opportunities to make new tester friends!

We hosted 200 software testers from across the globe, had 9 amazing 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. Here are all the TestBash Netherlands talks, get stuck in!

Join the discussion about TestBash Netherlands over at The Club.

We would like to thank our TestBash Netherlands 2018 event sponsors; Xebia, Improve, Alten, Info Support, Testpeople, Praegus and Bartosz 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 on our events pages.

Watch all the talks from the event:
TestBash Netherlands 2018



Wednesday, 11th April 2018

All Day Sessions | 9:00am - 5:30pm

As testing shifts left in an agile world, teams rely on the fast feedback of automated scenarios for continuous integration/deployment. Automation frameworks must be designed to be stable, robust, and flexible. The traditional way of automating UI scenarios in a silo doesn’t lend itself to agile practices.

In this hands-on workshop, you will build an advanced automation framework capable of keeping up with the demands of agile development. This single framework will be capable of supporting the automation of UI and web services, as well as Behavior-Driven Development (BDD) initiatives.

You will learn how to :

  • Utilize and optimize BDD specs for test automation
  • Use Cucumber to write steps that execute BDD specs
  • Use Rest-Assured to employ web services to make your UI tests quicker and less brittle

Upon completion of this interactive workshop, you will know how to utilize Cucumber and Rest-Assured to enhance your existing UI frameworks to be more agile-friendly.

Angie Jones
Angie Jones is a Senior Developer Advocate who specializes in test automation strategies and techniques. She shares her wealth of knowledge by speaking and teaching at software conferences all over the world, as well as writing tutorials and blogs on angiejones.tech. As a Master Inventor, Angie is known for her innovative and out-of-the-box thinking style which has resulted in more than 25 patented inventions in the US and China. In her spare time, Angie volunteers with Black Girls Code to teach coding workshops to young girls in an effort to attract more women and minorities to tech.
All Day Sessions | 9:00am - 5:30pm

The role of a tester on an agile team is so much more than “hey can you test this with your super testing skills”. Testers are, on the one hand, chameleons who need to adapt their skills to new situations within the team. On the other hand, we can’t just react to situations – we need to proactively lead the team, other testers, product owners and customers towards better quality. Yet agile teams don’t generally bestow formal authority. And, as testers, we’re often trying to lead from a position that is still not always appreciated (“agile teams don’t need testers”, “testers are just bad developers”, “you’re just a tester”…). We often need allies within the team –from the developers, and also from stakeholders for our product.

In complex situations where we’re dealing with unknown unknowns plus sticky, messy humans, communication is key. A degree in psychology would sometimes be helpful. Multiple years of cat-herding too. In this workshop, Zeb and Alex will focus on communication.

The workshop will consist of the following topics:

  • Communicating the value and role of testing
  • Testers as the communication glue for various stakeholders and within the team: talking about testing, risk and quality at the right level for the right audience
  • Enablement: Teaching, coaching, coercing and encouraging others within the team to take on quality-related tasks and to support the value of the product through testing
  • Contributing visibly to the success of a project without programming skills
  • What testers and other team members can do together, resulting in better and more effective results

The workshop will focus on hands-on exercises and activities, led by Zeb (our friendly developer) and Alex (our friendly tester/product owner). Participants will have the chance to write tests and review them with a developer, review application code with a developer, and work side-by-side with a developer to quickly identify and squash a bug! There will also be exercises on communicating and working with other testers and product owners. These experiences will give participants courage and experience to bring their ideas and questions to the table in their own teams, and will also pave the way for gathering more experience in closer collaboration with other team members.

Zeb Ford-Reitz

Zeb is a software developer and technical lead at Bredex in Germany. He is a huge fan of open source, and was an active Eclipse committer for many years. He works closely with testers in his teams to share understanding about quality and risk. He has a knack for effective code documentation and is not fond of acronyms.

Alexandra Schladebeck

Alex fell into IT and testing in 2005 and has never looked back. She is now Head of Software Quality and Test Consulting at BREDEX GmbH and spends her time working with test consultants, developers and customers to help them towards great quality.

You’ll usually find Alex talking about quality and how it affects the whole development process. She’s also a frequent speaker at conferences where she likes to share her project experiences and learn from other practitioners.

Does your organization use Continuous Integration* (CI)? We see that tools as Jenkins, or Bamboo are common in most development teams. Developers use CI to automate a lot of the development process and create short feedback loops. You need to understand how a basic CI process works and what impact it has on the testing job. Take from this training how you can leverage CI to provide more value. When you understand how CI works and what you can do with it, it allows you to work more efficiently.

Richard and Jeroen will guide you through the CI process with various exercises in Jenkins. You will practice with e.g. starting automated jobs, working with pipelines, and investigating failures. So bring your laptop and get to know the world of Continuous Integration.

* Continuous Integration is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early.

Jeroen Mengerink

As a test consultant for Polteq Test Services B.V. Jeroen Mengerink has performed multiple TPI assessments worldwide. His technical skills allow him to team with developers in testing of e.g. websites, APIs, and web services. Jeroen performs both functional testing and performance testing. In addition to his work for clients, he is involved with test innovations in agile. Jeroen teaches Certified Agile Tester and courses on agile, TDD, CI, and cloud; coauthored Testing Cloud Services; and blogs at jmengerink.wordpress.com. Follow him on Twitter @AngusVB.

Robin van Groesen

As a test engineer for Polteq Test Services B.V. Robin van Groesen has performed assignments in performance testing and test automation using Selenium Webdriver in both Java and PHP. He specializes in test automation, aiming to transfer the skills and knowledge he acquired to people new in those fields. Robin teaches both Selenium Webdriver and Introductory Java for Testers courses.


Test automation, when done well, can be of great help in supporting testers (and development teams as a whole) in delivering high quality in testing, and hopefully in delivering high quality software at speed. There’s just one challenge, though: it’s bloody hard to do test automation well!

In this workshop, we’ll show you how to create and implement a solid test automation strategy by asking six simple but difficult questions: Why? When? Where? What? Who? and How?

By answering these questions, we’ll help you to:

  • Successfully manage expectations with regards to what automation can and cannot do for you
  • Debunk common myths with regards to test automation (‘If we automate all our tests we don’t need testers anymore!’, anyone?)
  • Decide what tests are suitable for automation, and what tests are better left to testers
  • Decide on what level and with what scope to automate tests
  • Make an informed decision on which tools to use
  • Define the impact of introducing (more) test automation in your team (and your organization)
  • Describe the role of test automation in the test and quality strategy of your organization

We’ll answer these questions in several rounds in smaller groups, using a variety of formats, which will allow you to learn not only from us, but also from your fellow participants.

Takeaways / next steps:

After attending this workshop, you’ll have insight into what it takes to create and implement a solid test automation strategy. You’ll have a checklist of questions to apply to your own current

or future test automation efforts, as well as a list of useful resources (books, blogs, code repositories, other web sites) that can help you to succeed with test automation. You will leave the workshop with answers to these questions that you can apply directly to your specific situation.

Target audience:

This workshop is targeted towards testers, developers, team leads and others that rely on test automation (or are looking to do so) as part of their software development and testing efforts and those who want to implement or adjust test automation within the limits of reasonable expectations.

Ard Kramer

I am a software tester from the Netherlands and I am working for Alten Nederland since 2008. I call myself a Qualisopher which stands for someone “who loves truth and wisdom and at the same time is decisive to improve man and his environment” . This means I am interested in the world around us, to see what I can learn and I can apply in software testing. That is one of the reason why I tell stories in books and at (test) conferences such as EuroSTAR, Expo:QA, Belgium Testing Days, CAST and Testnet conferences. My dream is to participate, as a good qualisopher, in all kind of projects such as sports, culture or software testing. Projects which add value to our community: I want to inspire other people by cooperation, fun and empathy and hopefully bring light in someone's life.

Bas Dijkstra

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.

Dave Snowden’s work in complexity theory seems to have really caught the attention of many in the software testing community of late, but why? And with all this attention, why have there been so few talks or workshops on the topic? Is Cynefin a tool? A model? What do people mean when they speak about complexity theory? More importantly, why should this matter to software testers? In this experiential workshop, Ben and Martin will introduce some of the basic concepts of Cynefin, but with a special focus on how it can be immensely interesting and useful to software testing professionals.

In this session, the group will:

  • Explore the Cynefin sensemaking framework itself with real examples you bring from work
  • Use exercises and discussions to help uncover how Cynefin and complexity theory complement testing methodologies
  • Explore the notion of shifting tester mindsets from "thinking differently" to "gaining better access to different thoughts”

Ben and Martin aim to get testers excited about a field of study that is:

  • Over two decades old
  • Being extensively used by governments and international agencies
  • Proven to be highly successful for studying, describing and successfully impacting extremely complex systems

Cynefin might look simple, but there’s a lot going on under the hood and it truly needs to be experienced rather than observed. Come experiment safely, and discover for yourself what might make this topic so interesting, and be part of the paradigm shift.

Ben Kelly

For me, the various software development disciplines are complimentary and they are more effective when each discipline understands the fundamentals of the others. Testers especially need to have many strings to their bow as they are also an information conduit, seeking information and getting it to people who can benefit from it.

My view of testing and software development is heavily influenced by my martial arts background. I hold a 5th Dan in kendo and represented Australia several times at the world kendo championships. Just as with kendo, or anything worth mastering, software testing requires consistent and deliberate practice with the intent to improve.

Software testing has been a huge part of my life for more than fifteen years now. I’ve built and led teams in Australia, Japan and the United Kingdom at companies ranging from small start-ups to enterprise level multinational corporations, including heading up software testing for the European Product Development department at eBay. I’m now the managing director of House of Test UK.

In addition to my company duties, I like to run workshops and speak at conferences around the world. There are some really interesting developments in the software testing industry. There’s a critical mass of skilled practitioners connecting with one another to share their experience and skills and I’m excited to be a part of it.

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.

Variously defined as “fallible methods for solving problems” (Bach & Bolton) or “rules of thumb”, heuristics are essential tools for thinking test practitioners. When you construct a test around a model like “follow the money”, or adopt a leadership pattern where you challenge your team members with stretch goals, you are working with a heuristic. In each case, the model may be applicable and useful in some contexts, and irrelevant or even detrimental in others.

One of the keys to using heuristics successfully is to do so consciously. If you aren’t aware that you are operating with a heuristic model, it can become an unchallenged assumption. But if you consciously use a model as a heuristic, then you are in a better position to see its weaknesses and potential failure points in a given situation.

In this workshop, we will explore the use of heuristics in problem solving and software testing. Working in groups, participants will have opportunities to design heuristics to solve particular problems, apply them to problem solutions, then critique their models and share their conclusions with other groups.

The session will be highly interactive, consisting principally of problem-solving exercises and debriefs. Conscious use of heuristics requires both creativity and critical thinking skills. Come prepared to practice and extend yours! Participants are invited to bring testing problems from their own experience to share and work with in the second half of the session.

Fiona Charles
I’m Fiona Charles, owner and principal consultant at Quality Intelligence, Inc., a small independent business offering consulting services in software testing and test management. I formed the company early in 2007, after nearly 13 years working for IT services companies as a consultant and test manager on client projects.

Specification by Example has been described in two successful books by Gojko Adzic, who explains that there is far more to the success of high-performing agile teams than just automated testing and continuous integration. Specification by Example is a set of practices and patterns that successful teams use to derive scope from business goals, specify solution details collaboratively, make key acceptance conditions explicit through the use of concrete testable examples, and provide fast and frequent verification that our system behaviour matches our expectations.

This tutorial, for testers, developers and agile business customers, will enable you to apply the practices and patterns of Specification by Example to reach a shared understanding of business problems, discover hidden assumptions and domain concepts, highlight important exceptions and edge cases, and recognise when a specification is incomplete.

Through a series of practical exercises using a sample domain, you will learn how to collaboratively translate business requirements into user stories that are directly illustrated and elaborated by concrete examples, which can in turn be directly represented as automated acceptance tests. We will also look at how those tests are represented and automated in popular open-source agile testing frameworks such as Fitnesse.

Key learning points include:

  • How to overcome problems of incomplete, unclear or ambiguous requirements
  • How to use Story Maps to derive iteration-level stories from higher level business goals
  • How to illustrate specifications with concrete examples to create a single source of truth for testing and development
  • How to identify and avoid functional gaps and inconsistencies in specifications and tests
  • How to run workshops to facilitate collaboration, shared understanding and communication of intent
  • Good practices for designing specifications with examples and acceptance tests for agile teams
  • How to create a living documentation system to add value to your process long-term

David Evans
David Evans is an experienced agile consultant, coach and trainer with over 25 years of IT experience. A thought-leader in the field of agile quality, he has provided training and consultancy for clients worldwide. An in-demand speaker at events and conferences across Europe, David was voted Best Keynote Speaker at Agile Testing Days 2013. He is co-author of the best-selling books “50 Quick Ideas to Improve your User Stories” and “50 Quick Ideas to improve Your Tests”, was a contributor to the book “More Agile Testing”, and has also had several papers published in international IT journals. He currently lives and works in the UK, where he is a partner in Neuri Consulting LLP.

Friday, 13th April 2018

We are often not aware of the unintentional bias we apply in our work, especially with regard to roles and our self-identification with certain groups.

Assumptions we make about what testers and developers do, or do not do, sometimes amount to a level of prejudice that we would never want to be guilty of in social or cultural contexts.

I think these biases can lead to limiting the potential of the roles people can play in healthy, agile cross-functional teams.

In this talk I will explore the kind of language that we often use at work that may be negatively affecting the way we think of ourselves and others.

I will also share current research revealing the communication secrets behind the most effective teams.

David Evans
David Evans is an experienced agile consultant, coach and trainer with over 25 years of IT experience. A thought-leader in the field of agile quality, he has provided training and consultancy for clients worldwide. An in-demand speaker at events and conferences across Europe, David was voted Best Keynote Speaker at Agile Testing Days 2013. He is co-author of the best-selling books “50 Quick Ideas to Improve your User Stories” and “50 Quick Ideas to improve Your Tests”, was a contributor to the book “More Agile Testing”, and has also had several papers published in international IT journals. He currently lives and works in the UK, where he is a partner in Neuri Consulting LLP.

In today's environment a lot of emphasis is put on automation and being a more technical tester - it's all well and good learning Python or Ruby and picking up a tool but how do we hone our innate skills as testers? What if there was a way of putting your 'bug-goggles' on? Would you be interested in that?

Test Techniques have got a lot of bad press over the last few years often being seen as outdated and unwieldy however applied in the right areas with the correct focus they can yield useful results - let me reintroduce you to some of the old favourites and show how they can be rebooted!

Sue Atkins

Sue is a highly motivated test consultant having spent over 25 years evangelising about testing. Her skills include performance testing, usability testing, test training and test process improvement. She has spent the last few years concentrating on bringing new testers into the fold and is currently the chairperson of the Scottish Testing Group.

As a software engineer, you know how important it is to have a well-equipped set of automated tests. Such a set will help you to make changes to the code quickly and with confidence. Therefore, engineers agree on the percentage code to be covered by automated testing. Automated testing verifies the operation of the source code, but how do you verify the operation of your tests?

During this session, we explain which problems can occur if the engineers concentrate solely on achieving the agreed coverage rate. For example, a high degree of coverage is not a guarantee of a well-tested application. In addition, we explain what mutation testing and how to test with mutation testing which code is still insufficiently tested. During the session we demonstrate mutation testing using Stryker. Stryker is an open source mutation test framework that we have developed for performing mutation testing on JavaScript projects. More information about Stryker can be found at: https://stryker-mutator.github.io/

Nico Jansen
Nico Jansen
Simon de Lang
Simon (24, DevOps engineer @InfoSupport) and Nico (31, full-stack developer and trainer @InfoSupport) both love open source and testing. Together they founded Stryker, the mutation testing framework for the modern web.

My department is transitioning to DevOps as the next step from working Agile. In the process, Test Analysts and Developers have seen their roles merge. The need to bridge the previous barriers between the roles required more of a cultural change than a polishing up of our technical skills. I believe our work culture is created by myself and my colleagues with small actions every day. Every month, we celebrate events, people and achievements, where a successful go-live is just as important as the latest team outing. All these small actions help foster a culture in which respect, cooperation and personal connection are at the forefront. As a natural result, not only do the former testers learn more technical coding skills, but the former developers are increasingly helping out with test automation and facilitation. I wish to challenge others to think on how to proactively chart a course of your own liking. How do you encourage engagement? What actions do you take every day that bring you and colleagues to work with a smile?

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.

Business processes rely more and more on increasingly complex ICT services. This means our problems will become more complex, but also the solving process will also become more complex. The World Eco Forum’s report “Future of Jobs” indicates Complex Problem Solving as the number 1 skill required in 2020. So how do we get ready for that?

  • What makes a problem complex or seem complex?
  • What will be different from problem-solving in the past?
  • How can you develop your problem-solving skills to the match the future demand?
  • Why is it important to apply structured powerful problem-solving approach?

In this presentation you'll find out the answers to the questions above and get started on your way to future proof problem solving.

Martijn Maas

Martijn Maas is a senior expert of incident, problem and crisis management. He combines 20 years of experience in ICT with a background in psychology and leadership development. "My biggest passion is inspiring people to look at issues in a new way so that they are able to take the next step themselves. I consider approaching complexity in a simple way as the key to improvement and growth." Martijn developed an innovative approach to quality improvement in operational ICT environments. An important part of this is combining people’s intrinsic skills and motivation with structured methods aimed at the goal, not the process.He is a Complex Problem Solver and senior consultant at CoThink.

  • More about Martijn: https://www.cothink.com/martijn-maas/
  • and on https://www.linkedin.com/in/martijn-maas-1303a0/

For many test automation initiatives, an ultimate goal is to eventually have the automated scenarios run as part of Continuous Integration (CI). However, even with stable and reliable scripts, there are still a few pitfalls that may not be obvious to those new to CI, especially as the number of automated scenarios continues to grow.

How do you manage a suite of thousands of tests within a CI environment and yet still get fast feedback? How do you move away from the “everyone owns everything = no one owns anything” mindset and instead leverage the “small team” agile approach?

In this talk, Angie will answer these pertinent questions by sharing some of the lessons she has learned over the years about managing a large suite of automated scenarios within a CI process.

Angie Jones
Angie Jones is a Senior Developer Advocate who specializes in test automation strategies and techniques. She shares her wealth of knowledge by speaking and teaching at software conferences all over the world, as well as writing tutorials and blogs on angiejones.tech. As a Master Inventor, Angie is known for her innovative and out-of-the-box thinking style which has resulted in more than 25 patented inventions in the US and China. In her spare time, Angie volunteers with Black Girls Code to teach coding workshops to young girls in an effort to attract more women and minorities to tech.

This talk is about the exploring part of testing. Where/When details matter, investigating information properly and knowing how to spend your time wisely with the enormous time pressure. This is something detectives also do. Only there goal is to tackle the mysterious this world has to offer and trying to solve them. But we as testers will not focus on solving crimes, capturing killers or finding missing persons. No, we tackle the mystery of delivering high quality software.

During this talk we will discover how detectives do their job. How do they solve crimes? How do they spot so many details? How do they process the great amount of information? How do they organize important information from the rest? I will show how we can apply their practices to become better testers.

We will dive into the world of the great detectives(also fictional ones) like Sherlock Holmes & Doctor Watson, J Edgar Hoover & John Luther.

Geoffrey van der Tas
Geoffrey works as though leader for Ordina Auto|Q. Geoffrey has focus on more the agile side of testing and exploratory side of testing. Together Geoffrey and Mark worked on this workshop to combine both their skill sets.

As a tester, I have two ways to provide value in my teams. As in individual contributor doing tasks I have productivity. As a member of a group, enabling others I have generativity. Growing in seniority in Agile teams, I’ve moved from an individual contributor to collaborator. I’ve found that the balance of productivity (information I provide) and generativity (information others provide because of me) has become a key part of my tester role.

In this talk, I will share my experience of learning to step back and hold space, actively do less to enable others to do more. I’ll show the ways I’ve learned to use to make my contributions visible to my managers and how I’ve redefined my tester role with 4C’s: I’m a Conscience, a Catalyst, a Cheerleader and a Critical Thinker.

Join me for a experience-packed talk that teaches you experimenting with doing less and achieving more.

Maaret Pyhäjärvi

Maaret Pyhäjärvi is a software professional with testing emphasis. She identifies as an empirical technologist, a tester and a programmer, a catalyst for improvement and a speaker. Her day job is working with a software product development team as a hands-on testing specialist. On the side, she teaches exploratory testing and makes a point of adding new, relevant feedback for test-automation heavy projects through skilled exploratory testing. In addition to being a tester and a teacher, she is a serial volunteer for different non-profits driving forward the state of software development. She was recently awarded as Most Influential Agile Testing Professional Person 2016. She blogs regularly at http://visible-quality.blogspot.fi and is the author of Mob Programming Guidebook.

Negative Tests are always tricky to automate - it's different than automating a positive/happy path test. Initially, while the negative test is developed often it's productive but over time as the application/testable product changes the negative tests may result in false positives or altogether irrelevant! In this talk, I like to share my experiences using real-life project examples that helped me to come up with concrete negative assertions, assertions that were relevant to the expected behavior of the application. I would share with actual and/or pseudo code examples to demonstrate the assertions. The talk would describe the lessons that I learned over time, resulting in better negative assertions.

Negative testing ensures the application behaves gracefully with invalid user input or unexpected user behavior. It improves product quality and finds it weak points. The difference between +ve and -ve is throwing an exception is not an unexpected behavior for the latter.

Negative testing is the process of applying as much creativity as possible and validating the application against invalid data. This means its intended purpose is to check if the errors are being shown to the user where it’s supposed to, or handling a bad value more gracefully. The application or software’s functional reliability can be quantified only with effectively designed negative scenarios. Negative testing not only aims to bring out any potential flaws that could cause serious impact on the consumption of the product on the whole, but can be instrumental in determining the conditions under which the application can crash. Finally, it ensures that there is sufficient error validation present in the software.

Tuhin Subhra Mitra

I am Tuhin, currently working as a Test Engineer in a product development company called Mendix at Rotterdam, Netherlands. I was born and raised in Kolkata, India – started my career as Test Analyst back in 2009 post my graduation. Testing to me is a culmination of thought process and preparations – effective, creative, and fast – that help me to validate the software or application properly, eventually providing a valuable feedback to my team.

Cooking, reading, exploring restaurants, Netflix, running, sports, Spotify, classical music – are the things that help me awake, apart from work, when I am not sleeping.