TestBash Netherlands 2017

Testers from all around world (re)united on January 26-27th 2017 in Utrecht for the most awesome, friendliest and jam packed software testing conference ever in the Netherlands!

Our TestBash Netherlands conference was a two-day event all about software testing. There was plenty to learn, much to take home and many new people to get to know. Here we present you with the 10 talks from our conference day, and of course the famous 99 second talks.

We would like to thank our TestBash Netherlands 2017 event sponsors, Improve, Polteq, Testpeople, Centric, and Xebia for supporting this software testing conference and the software testing community.

Watch all the talks from the event:
TestBash Netherlands 2017



Thursday, 26th January 2017

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

This session is not for the managers. This is for the people that actually want to do something. People that want to enforce their team by giving fast insight in the product quality. Using automation and automated tools on the right levels, augmented by exploratory testing.

In this session you'll host your first(?) online cloud application. You will use test automation to create an automated suite for this application. In a couple of iterations you'll get fast deliveries. Are you able to keep up the team pace? Can you give the right insight with the use of automation?

Take aways:

  • Inside knowledge about Test automation concepts, tips and tricks
    • Automation purposes
    • Characteristics of a good automated test
    • Asynchronous automated testing
  • Usage of test automation tools like Selenium, SoapUI, JUnit etc.

Pieter Withaar
Pieter Withaar
Manon Penning
Manon Penning

You know Exploratory Testing is not following a script. You know Exploratory Testing provides quick feedback. You know Exploratory Testing is a perfect fit to your context. You have notes from test sessions. What next? How do you share this information? What do you share? How do you produce metrics? What can you visualise? How can you visualise it? In this workshop Sharath and Tony will introduce you to a framework to help manage and report your testing sessions. This framework can be used to produce useful trends and metrics to quickly to share with your stakeholders.

  • Through a day of discussions, teamwork and exercises we will
  • Get familarised with the framework
  • Look at different ways of producing your notes
  • Produce trends and metrics from your test sessions
  • Give an idea of coverage

Attendees will leave with:

  • A understanding of different note taking methods
  • A method of producing trends and metrics
  • A view of coverage
  • Visualisation of their Exploratory Testing
Tony Bruce

Tony is a professional, constantly learning, coaching and teaching agile team member who specialises in Testing and people.

He works in an exploratory style with agile techniques and testing with different perspectives; ranging from functional testing through to performance testing, using appropriate tools. He believes there is a need to effectively communicate progress and provide information on testing performed and keep a constant stream of information flowing through the team.

He has worked in various industries with organisations such as Skillsmatter, Channel 4, Ernst & Young, LMAX and The Children’s Society. He is an active member of the Testing community, he hosts the London Tester Gathering and speaks at conferences all over the world.

And in case his accent has you confused, it’s 1-part Aussie, 1-part English and 1-part American.

Sharath Byregowda

Sharath Byregowda is an experienced software delivery consultant with a deep passion for testing and quality, developed through various roles across different domains.

He seeks to understand the specifics of each situation, selecting practices that fit the context. He also likes to work closely with developers, testers and other business functions to reduce bottlenecks and improve collaboration.

As a practitioner, Sharath is compelled by questions around what makes good quality, how to mitigate product risks and how to design tests to provide fast, valuable information to answer these questions. He is also the co-founder of Weekend Testing and blogs at testtotester.blogspot.co.uk.

Transitioning from the monolithic technology era to microservices implementation, one key component is the service oriented architecture (SOA) principle. At the core of SOA lie services which enable various consumer and clients to access the same functionality provided by a back-end server. Getting familiar with RESTful architectural approach is very useful when defining your automated checks strategy. Exploring the system, several questions may arise: how do I identify the APIs? How do I test them? How to write test scripts to against such services? What testing tool can do the job?

Many languages, many options - during this workshop, I will help you get started with testing rest services. During the session you will learn:

  • How to choose the right tool for you?
  • Identifying and defining heuristics to test RESTful APIs
  • Writing test scripts
  • Creating test data
  • Running tests

Prerequisites for this workshop:

This session is addressed to people without any programming knowledge nor high technical background. For this session we kindly ask to bring your laptop with prior installed PostMan (free version) or SoapUI (free version).

Andrei Contan
Andrei Contan
Carmen Sighiartau
Carmen Sighiartau - Java Developer with over 10 years of experience in the industry she recently found out how awesome testing conferences can be. Besides her daily development and managerial activities, she's involved in helping both testers and developers to bring more value to their work by providing training and coaching sessions. Currently she is a software consultant constantly looking for new challenges.
Morning Sessions | 9:00am - 12:30pm

This session will be on testing robots! Besides that testing a robot is a just fun, you also have to think differently as a tester when hardware is involved. Does your team have what it takes to create a winning robot? In this workshop we will test robot's with multiple teams to have a bit of competition as well. For an impression have a look at: https://www.youtube.com/watch?v=qe-u6HdPl-g Because we will work with teams we need multiple presenters for the workshop.

Take aways:

  • Working with Arduino Robots
  • Learn how testing with hardware is different from just software
  • Working with and creating specifications
  • Writing automated unit and acceptance tests for a robot framework

Attendees will use JavaScript, NodeJs and CucumberJS.

Jöchum Borger
Jöchum Borger
Erik Zeedijk
Erik Zeedijk
Xavier Viuda
Xavier Viuda
Fin Kingma
Fin Kingma

Once I made an exercise for a peer meeting about Testing and Mind Mapping. It took me months to get proper test ideas. I obviously lacked speed. Then I went back to the drawing board and found new test ideas.

Finding a way to test right is achievable. Finding a fast way to test right is difficult. Join me on my travel to find another way to test time outs, counters, and statuses. Expect hand drawn models, markers, and stickies in order to create a flow of test ideas. Test ideas, which can be understood by a PO or business. Test ahoy.


  • 3 ways to test using visual stuff
  • drawing can catch up with your thoughts
  • visualize test ideas for a PO or business
  • how to visualise test ideas using domain knowledge

Han Toan Lim
Han Toan Lim

Specification by Example (SBE) is an Acceptance Test Driven Development (ATDD) practice. The goal is to help teams create software based on collaboratively defined requirements determined through realistic examples. This half day workshop will teach you:

  1. the power of effective collaboration
  2. how to improve the clarity of requirements (with examples)
  3. how to create common understanding
  4. how examples can serve as living documentation
This workshop is aimed at people of all levels, although it is specifically interesting for those who haven’t worked with an ATDD practice before. Even if you think ATDD isn’t suited for your environment, we invite you to come to our workshop. We will show you that parts of Spec by Example are always useful and usable.

Cirilo Wortel
Cirilo Wortel
Maaike Brinkhof
Maaike is an independent agile tester. She loves testing because there are so many ways to add value to a team, be it by thinking critically about the product, working on the team dynamics, working to clarify the specs and testability of the product, getting the whole team to test with Exploratory Testing…the options are almost endless! She likes to help teams who are not sure where or what to test. After reading “Thinking, Fast and Slow” by Daniel Kahneman she developed a special interest in the role of psychology in software development. During ‘analogue time’ Maaike likes to practice yoga, go for a run, check out new local beers, play her clarinet and travel with her boyfriend.
Afternoon Sessions | 1:30pm - 5:30pm

With more than 2.1 billion smart phones worldwide and 4 million mobile apps, the world of software testing is changing. The domain of testing is changing with respect to context, skillset and complexity.

When it comes to mobile app testing some of the questions asked are:
  • What is a mobile app tester?
  • What are the biggest challenges in mobile testing?
  • How to choose your test devices?
  • What is the test approach of mobile testing?
In this interactive workshop, we will go through some exercises which will enable participants to answer the above questions.
To make it effective, please don’t forget to:
  • Download the free version of Xmind (http://www.xmind.net/download/)
  • Bring your mobile device
  • Enjoy
Paul Groothuis

Paul started his career at one of the biggest consultancy companies of Europe. As a consultant in multiple projects he quickly discovered his passion for mobile testing and decided he wanted to focus on mobile exclusively. He therefore joined IceMobile where he continues to enjoy his expertise in testing both the frontend and backend systems of mobile apps.

Desmond Delissen

Desmond started his testing career at a big consultancy company in 2009. In 2012 he had the chance to work on the mobile app of the biggest retailer of the Netherlands. Desmond enjoyed this so much that he decided to start working for IceMobile, who is specialized in mobile apps for food retailers with over 1.5 million active users worldwide, where he became an expert in testing mobile apps and their backend systems.

Engage in a workshop where we explore the aspects of courage and vulnerability. To work with agile you need to be brave. But what is courage? Why do we need it? How will it help us be better at our jobs? What does vulnerability have to do with courage?

Gitte has explored this area for several years and even has a tattoo with “Be Brave” for her courage is very much about being who you are. Participants will learn to understand what courage is. They’ll discover their own capacity for it and learn tactics to be more courageous

This she accomplishes by sharing her experience and through exercises that will draw out the participants’ unique potential for courage.

Pitch: It is so much easier to see other people’s courage than your own. I know that each of us are brave in our own way. Come explore your courage and get tools to take the next step.

Gitte Klitgaard
Gitte Klitgaard

Software development is changing rapidly. Waterfall projects are fewer and fewer. Even agile seems to be ever more replaced by DevOps. These changes to the context in which testing is taking place pose ever growing demands on those who test to keep up and to integrate into the team. No longer is there time for long reviews, test plans and detailed test scripts. Stakeholders expect and demand ever faster feedback from the team and testing plays a special role in this. As such testing has re-invented itself and stepped away from only scripted tests to more dynamic ways of testing, especially test automation. But there is still a lot to be learned and in this workshop I will try to provide an updated meaning to testing and introduce exploratory testing in a way that invites to use the good elements of the old, makes use of the new and focusses on that what stakeholders need to know.

Learning points:

  • Learn what it means to test and to explore software
  • How to do exploratory testing
  • The relationship between (exploratory) testing and software development
  • Bring and keep structure into your (exploratory) testing
  • Telling the testing story

Jean-Paul Varwijk
Jean-Paul Varwijk

Friday, 27th January 2017

We often hear about how ‘test automation’ can go wrong, which is all fine and dandy for the pessimists in the audience, and balancing feel good positive case studies exist for the optimists. But what about the anarchists? What about the rule breakers? What about the pragmatists? In this talk Alan will explain how to ‘misuse’ the ‘automation’ tools you’ve heard so much about, because you need to get things done. You’ve no doubt heard that ‘Cucumber is not a test tool’, and you’ve no doubt noticed that people use Cucumber during their testing. It’s misuse cases like this that we will celebrate, and as a bonus, you’ll learn what Cucumber ‘really' is. We’ll look at other tools; to find out their true nature and how you can turn it to your personal advantage. To further groom you for success, we’ll explain the mental models which give you guilt free flexibility in your approach. If you’ve ever wanted an ‘expert’ to quote to give you permission to use the tools how you want, this is the talk for you.

Alan Richardson

Alan Richardson has over twenty years of professional IT experience: as a programmer, tester, and test manager. Author of four books and several online training courses to help people learn Java, Technical Web Testing, and Selenium WebDriver. He works as an independent consultant, helping companies improve their automated execution, agile, and exploratory technical testing. Alan posts his writing and training videos on EvilTester.com, and CompendiumDev.co.uk.

You have to be brave in order to change the world! This holds true professionally and personally. “So what does this have to do with me” you might think; “I just want to do my job – not change the world.”

At work we face challenges all the time that require courage; from asking for help to quitting your job; from admitting a mistake to saying that you did something good. Being brave and vulnerable is necessary. Standing by who you are, having the courage to be different, making yourself vulnerable, speaking up when there is something important to you, sharing your fears and joys requires courage. Courage is individual and there is no such thing as a little courage. Being brave is not about removing fear or not being afraid – it is about doing what is necessary even when you are afraid.

I live this personally; I have to be brave (even have a tattoo with it). And it is a big learning I try to pass on to the people, I coach. In my session I will talk about why I have to be brave and vulnerable, give examples of how I am courageous, and why being brave is a big part of my work life.

Gitte Klitgaard
Gitte Klitgaard

Have you ever stopped to ask yourself why the testing profession involves so many other things beside testing - how much of your working week, month or year do you actually spend in test design or execution mode? Is it these 'other' (maybe less fun) activities what you really get rewarded for excelling at, with promotion and career advancement? Is the best career path for testers to become managers and stop practicing testing altogether? Sharath and Tom will explore answers to these questions and provide ideas so that more of your days are spent performing both high value and enjoyable work. They will also show how doing this can actually be better for your long term success and well-being!!

Learn about 'appropriate minimalism' and how to apply it to your context - to areas like documentation, reporting, bug triage, test estimation, planning and preparation - so that you can spend more time testing and supporting the delivery of high quality products. In this increasingly agile world, find out how mastery of the craft of testing can be even more rewarding and valuable for your future as learning management.

Sharath Byregowda

Sharath Byregowda is an experienced software delivery consultant with a deep passion for testing and quality, developed through various roles across different domains.

He seeks to understand the specifics of each situation, selecting practices that fit the context. He also likes to work closely with developers, testers and other business functions to reduce bottlenecks and improve collaboration.

As a practitioner, Sharath is compelled by questions around what makes good quality, how to mitigate product risks and how to design tests to provide fast, valuable information to answer these questions. He is also the co-founder of Weekend Testing and blogs at testtotester.blogspot.co.uk.

Tom Roden
Tom Roden

An embedded tester's task is to assist a team during development through testing. This basically means gathering and reflecting information. But how do we get to the essence of the data that can boost up the testing which is needed? In order to have a wide test coverage, it is crucial that the information flow from tester to developer is as close and as accurate as possible. Not less important is the communication flow from developer to tester. This social relationship between tester and developer, and of course other team members, needs to be build up in a respectful, natural way over time. People over tools is the credo, e.g. talk first to the people before raising the bug flag. This seems to be simple in theory but it is quite difficult to apply in practice. Once you succeed with it, you can get an increased awareness of testability in the team.

Building up the right amount of business know-how to master your testing challenges takes some time and the right people to get in touch with. Usually they don’t fall out of the clear blue sky and serve all their knowledge to you. In our projects, we’ve come up with an efficient way for finding the right sources.

In this talk we are going to share our experiences as embedded testers in a wide variety of projects. We are going to highlight different approaches and roles used in the past in testing, pitfalls and how to avoid them. To sum up the things, we’ll have a look with you together into what could be next in the future as embedded testers.

Diana Flores
Diana Flores
Simon Berner
Simon Berner

In 2016 I started within ING Bank to help a DevOps Squad with Test and Quality.

Their questions were as follows:

  • Help us to figure out how we are testing, and if we are testing enough?
  • How do we deal with non-functional testing?
  • What about Performance and load testing?
  • Are there any limitations within our current Continuous Delivery Pipeline?
  • We are currently testing within Docker containers. Is this ok?

In this talk I will take you on my journey as an Agile test coach to help a DevOps team get more mature. This team is working in a DevOps environment and is responsible for the processing of incoming transactions. Only after this processing there will be a mutation on the clients account.

How does this team test their software? What challenges did they face? How did they balance manual and automated testing? What where the traps they walked into? You will get a better understanding of their way of testing and working. What are the pro and cons and what is featured next? Furthermore, I will tell you what did the team learn, what were my key learning’s and what tools did I use to help the team.

Rutger van Faassen
Rutger van Faassen

You know what we don't talk about enough. Testability. I don't just mean testers either. Everybody. The benefits of testability are often forgotten, left until it’s too late, we are left scratching our heads as to why the system is doing that and how unaware we were.

If we know how to talk about testability in a compelling way, showing the benefits for all stakeholders, I believe it can be a central part of a product and seen as essential. In the age of focus on the narrowing gap between development and operations, testability shares many those goals, with feature flagging, effective monitoring and log management (to name but a few) synonymous with control and observability. And that is just the start of the benefits of a testability focus can bring.

I'll share a few stories that have taught me a great deal, plus the how the work of others has helped me along the way. All in hope of energizing those in attendance to use their new found testability focus in their workplace. After all, if its controllable and observable to some degree, its testable. If it’s not, how effective is your testing? And if it’s not testable, then how will you support it when its live?

Ash Winter
Ash Winter is a consulting tester and conference speaker, working as an independent consultant providing testing, performance engineering, and automation of both build and test. He has been a team member delivering mobile apps and web services for start ups and a leader of teams and change for testing consultancies and their clients. He spends most of his time helping teams think about testing problems, asking questions and coaching when invited.

Ever read an article about a data leak and wonder if there is anything you can do as part of your testing routine to prevent that? While Security can be all doom and gloom, it turns out that Test can share more of the security burden in a way that’s agile and minimal. In this session I will introduce you to what you need to know to minimize the security risk to your organisation.

What they can do for any project that will improve security that does not involve any programming. Also some ideas of where to start with sprinkling security tests into automation.

Mary Gilmartin
Mary Gilmartin

As people we like to categorize things around us. Likewise, we'd like to do that with leadership too. There are various models of leadership styles. For the rapidly changing world around us those seem no longer sufficient. We do Software development in an adaptive, agile way. What kind of leadership does that require? Also adaptive leadership or is there a need for an inspiring leader who has his own style? Compare Mark Rutte with Louis van Gaal: what kind of leader do you prefer or do you want to be? Jeanine Mechelinck, agile coach previously at bol.com and now at Stater, shares her stories full of examples from the sport and from her own experience. She shares her views on adaptive and authentic leadership.

Jeanine Mechelinck
Jeanine Mechelinck

In Agile things are going very fast. We cannot achieve good testing with only manual testing. We need test automation to speed us up, and to cover the regression testing. UI testing is not the only thing to be automated, due to the constant changes. API should be also covered with tests. Even with this coverage, can we rely on the test automation only? No. This is where exploratory testing comes into spotlight – to find defects which are not covered with automation.

During this talk I will explain why test automation is not a silver bullet. Also, it is not a special kind of testing. I’ll explain why and how do I see it as an adjunct to the exploratory testing and try to define a healthy balance between those two.

You will learn:

  • how I organize testing on my projects
  • about the tools I use
  • it's not about the tools, but a mindset
  • when to use automated testing and when to use exploratory testing and how to make the outcome of one be the input for the other

Mirjana Kolarov
Mirjana Kolarov

“I don’t know.”

These might just be the hardest words to say in any language. We avoid saying them, scared of coming across as doubtful and uncertain. This fear is understandable; we admire those who are knowledgeable and oozing with confidence - even more so in a professional context.

As testers, our team members and managers expect us to be firm and certain, providing clear answers. They want us to hand them that comforting blanket of certainty. Over the past years, I grew increasingly uncomfortable with that. I ended up having a hard time being sure of anything, to the extent that my confidence as a tester started suffering.

"You're rejecting certainty, just like Socrates", someone said. "That's skepticism. You're a tester, embrace it!". That sounded like a good way to get out of my little Socratic crisis, but it left me with a new challenge: how does one embrace skepticism, and how can this help me improve my testing?

I wanted to get to the bottom of this and, for a year, decided to submerge myself in all things skeptic in hope of finding clues to help me with my testing and my struggles with doubt. It was a fascinating journey that brought me to both sides of the spectrum, ranging from philosophy, religion, critical thinking to science and even pseudo-science. The latter proved to be a portal into the world of the odd, the awkward and the downright bizarre.

Now that I surfaced safely, it is time to reflect and make sense of what happened. This presentation will tell the story of how I embraced skepticism and became a proud and reasonable doubter. I will share how this influenced my testing and how I harnessed the power of doubt: by creating a portfolio of critical thinking heuristics that can be valuable addition to any tester's toolbox.

Zeger Van Hese

Zeger Van Hese has a background in Commercial Engineering and Cultural Science. He started his professional career in the motion picture industry but switched to IT in 1999. A year later he got bitten by the software testing bug (pun intended) and has never been cured since. He has a passion for exploratory testing, testing in agile projects and, above all, continuous learning from different perspectives.

Zeger considers himself a lifelong student of the software testing craft. He was program chair of Eurostar 2012 and co-founder of the Dutch Exploratory Workshop on Testing (DEWT). He muses about testing on his TestSideStory blog and is a regular speaker at national and international conferences. In 2013, Zeger founded his own company, Z-sharp.