TestBash New Zealand 2019

TestBash New Zealand 2019, our first software testing conference in New Zealand, took place on 29th October at the beautiful Te Papa Museum in Wellington. 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 250 software testers from across the globe, had 8 choice talks, lots of sweet as 99 second talks and all who attended took part in community activities and socials! It was a blast! Thanks, heaps!

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 San Francisco talks, get stuck in!

Join the discussion about TestBash New Zealand over at The Club.

We would like to thank our TestBash New Zealand 2019 event sponsors;  Flux and Assurity 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 New Zealand 2019



Wednesday, 30th October 2019

What Do We Mean By ‘Automation in Testing’?

Automation in Testing is a new namespace designed by Richard Bradshaw and Mark Winteringham. The use of automation within testing is changing, and in our opinion, existing terminology such as Test Automation is tarnished and no longer fit for purpose. So instead of having lengthy discussions about what Test Automation is, we’ve created our own namespace which provides a holistic experienced view on how you can and should be utilising automation in your testing.

Why You Should Take This Course

Automation is everywhere, it’s popularity and uptake has rocketed in recent years and it’s showing little sign of slowing down. So in order to remain relevant, you need to know how to code, right? No. While knowing how to code is a great tool in your toolbelt, there is far more to automation than writing code.

Automation doesn’t tell you:

  • what tests you should create
  • what data your tests require
  • what layer in your application you should write them at
  • what language or framework to use
  • if your testability is good enough
  • if it’s helping you solve your testing problems

It’s down to you to answer those questions and make those decisions. Answering those questions is significantly harder than writing the code. Yet our industry is pushing people straight into code and bypassing the theory. We hope to address that with this course by focusing on the theory that will give you a foundation of knowledge to master automation.

This is an intensive three-day course where we are going to use our sample product and go on an automation journey. This product already has some automated tests, it already has some tools designed to help test it. Throughout the three days we are going explore the tests, why those tests exist, our decision behind the tools we chose to implement them in, why that design and why those assertions. Then there are tools, we'll show you how to expand your thinking and strategy beyond automated tests to identify tools that can support other testing activities. As a group, we will then add more automation to the project exploring the why, where, when, who, what and how of each piece we add.

What You Will Learn On This Course

To maximise our face to face time, we’ve created some online content to set the foundation for the class, allowing us to hit the ground running with some example scenarios.

After completing the online courses attendees will be able to:

  • Describe and explain some key concepts/terminology associated with programming
  • Interpret and explain real code examples
  • Design pseudocode for a potential automated test
  • Develop a basic understanding of programming languages relevant to the AiT course
  • Explain the basic functionality of a test framework

Day One
The first half of day one is all about the current state of automation, why AiT is important and discussing all the skills required to succeed with automation in the context of testing.

The second half of the day will be spent exploring our test product along with all its automation and openly discussing our choices. Reversing the decisions we’ve made to understand why we implemented those tests and built those tools.

By the end of day one, attendees will be able to:

  • Survey and dissect the current state of automation usage in the industry
  • Compare their companies usage of automation to other attendees
  • Describe the principles of Automation in Testing
  • Describe the difference between checking and testing
  • Recognize and elaborate on all the skills required to succeed with automation
  • Model the ideal automation specialist
  • Dissect existing automated checks to determine their purpose and intentions
  • Show the value of automated checking

Day Two
The first half of day two will continue with our focus on automated checking. We are going to explore what it takes to design and implement reliable focused automated checks. We’ll do this at many interfaces of the applications.

The second half of the day focuses on the techniques and skills a toolsmith employs. Building tools to support all types of testing is at the heart of AiT. We’re going to explore how to spot opportunities for tools, and how the skills required to build tools are nearly identical to building automated checks.

By the end of day two, attendees will be able to:

  • Differentiate between human testing and an automated check, and teach it to others
  • Describe the anatomy of an automated check
  • Be able to model an application to determine the best interface to create an automated check at
  • How to discover new libraries and frameworks to assists us with our automated checking
  • Implement automated checks at the API, JavaScript, UI and Visual interface
  • Discover opportunities to design automation to assist testing
  • An appreciation that techniques and tools like CI, virtualisation, stubbing, data management, state management, bash scripts and more are within reach of all testers
  • Propose potential tools for their current testing contexts

Day Three
We’ll start day three by concluding our exploration of toolsmithing. Creating some new tools for the test app and discussing the potential for tools in the attendee's companies. The middle part of day three will be spent talking about how to talk about automation.

It’s commonly said that testers aren’t very good at talking about testing, well the same is true about automation. We need to change this.

By the end of day three, attendees will be able to:

  • Justify the need for tooling beyond automated checks, and convince others
  • Design and implement some custom tools
  • Debate the use of automation in modern testing
  • Devise and coherently explain an AIT strategy

What You Will Need To Bring

Please bring a laptop, OS X, Linux or Windows with all the prerequisites installed that will be sent to you.

Is This Course For You?

Are you currently working in automation?
If yes, we believe this course will provide you with numerous new ways to think and talk about automation, allowing you to maximise your skills in the workplace.
If no, this course will show you that the majority of skill in automation is about risk identification, strategy and test design, and you can add a lot of value to automation efforts within testing.

I don’t have any programming skills, should I attend?
Yes. The online courses will be made available several months before the class, allowing you to establish a foundation ready for the face to face class. Then full support will be available from us and other attendees during the class.

I don’t work in the web space, should I attend?
The majority of the tooling we will use and demo is web-based, however, AiT is a mindset, so we believe you will benefit from attending the class and learning a theory to apply to any product/language.

I’m a manager who is interested in strategy but not programming, should I attend?
Yes, one of core drivers to educate others in identifying and strategizing problems before automating them. We will offer techniques and teach you skills to become better at analysing your context and using that information to build a plan towards successful automation.

What languages and tools will we be using?
The current setup is using Java and JS. Importantly though, we focus more on the thinking then the implementation, so while we’ll be reading and writing code, the languages are just a vehicle for the context of the class.

Richard Bradshaw
Richard Bradshaw is an experienced tester, consultant and generally a friendly guy. He shares his passion for testing through consulting, training and giving presentation on a variety of topics related to testing. He is a fan of automation that supports testing. With over 10 years testing experience, he has a lot of insights into the world of testing and software development. Richard is a very active member of the testing community, and is currently the FriendlyBoss at The Ministry of Testing. Richard blogs at thefriendlytester.co.uk and tweets as @FriendlyTester. He is also the creator of the YouTube channel, Whiteboard Testing.
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

October 29th 2019 08:00 - 18:00

It is a common perception that one has to have authority over others in order to have a voice of opinion and make them do the right thing. When things don’t go our way, we often blame our superiors for not doing their job well and think the only way of changing this is for me to replace them and be the manager. But once you are in that role, you will realise there is always someone above you making the decisions, unless you work for yourself of course. This was my way of thinking until I worked in different organisations and realised the grass is not greener on the other side, and the only constant is myself. I have found that I can effectively lead by using empathy to influence behaviour change in my team and the wider company.
In this talk I will share with you my own experience of “leading” in various different organisations ranging from startups to large enterprises without any official title. I’ve found that as an individual contributor, I have often underestimated my ability to create outcomes that benefit everyone. The key factor in creating behaviour change in organisations is influence, and this talk will cover how to create influence and wield it for good. Testers often talk about empathy, and I’d like to extend our understanding of it to include how to use it to influence consensus inside our teams.


The key takeaways of this talk are:
  • What it means to lead 
  • How to gain trust through empathy and understanding of context
  • How can you lead others without any authority
  • How to influence behaviour change in your organisation
Francis Ho
Francis Ho is a Quality Analyst at Auror, a startup that prevents retail crime. He has previously worked in mobile and web app testing in companies ranging from tiny startups to large corporates. He is currently focusing on levelling up the testing practices of the Auror team at the moment. In his spare time, he runs a photography and video business with his wife because releasing to production isn’t stressful enough.

The message is loud and clear: Learn to code or hit the road. Don’t hesitate; automate!

The demand for technical skills has never been higher. It seems the days of the manual tester are over.

How much truth is there to this? How do we truly need to adapt for the future? Is there a future for non-technical testers? If so, what will that look like?

In this talk, Aaron will look at the current market demands, and compare that to what his vision for the future of testing is.


Aaron Hodder hails from Wellington, New Zealand, where he works for Assurity Consulting to coach testers to develop and deliver new and innovative testing practices to better suit the demands of modern-day software development.

Aaron is a passionate software tester with a particular enthusiasm for visual test modelling and structured exploratory testing techniques. He regularly blogs and tweets about testing and is a co-founder of Wellington Testing Workshops.

Have you ever found yourself feeling overwhelmed about learning new technology? Wondering if it possible for me to learn all of this? This is where Kim found herself earlier in 2018 when it was decided by the business to build a new product. They wanted to provide a way for clients to purchase bullion backed cryptocurrency using blockchain technology. 
Join Kim on the education pathway around blockchain, cryptocurrency and the different kinds of testing applied. Highlighting the lessons learnt of bringing such a product to market and the steep learning curve she had to ascend.


  • Learning new things can be daunting but taking the right approach will make it successful
  • Simple explanation of blockchain terminology and its applications
  • Different kinds of testing from Design to Pre-Production Release phase
  • Examples of UX product blockers that displayed in early testing
  • Demonstration of API testing with explanations of the results
  • Demonstration of using Selenium IDE to automate tests 
Kim has a diverse background professionally and has been working as a test resource within a varied range of development teams in Brisbane, Australia. She is currently working as an agile business analyst, supporting development teams to achieve quality through streamlined processes, and effective cross team communication. Kim’s passion is always with testing, and actively finds ways to support the testing community globally. She is a blog writer on her experiences within testing, co-founder of Lean Unwind meetup in Brisbane, international speaker, ardent support of driving professional development and mother of an awesome daughter plus two fur monsters.

Full stack UI driven tests are routinely criticised and shown to be inefficient, wasteful and brittle. But what are the alternatives? How can we successfully move away from full stack tests and develop valuable automated tests? We can achieve this by using our knowledge of our systems along with task analysis techniques to identify opportunities to move away from fill stack tests and towards smaller, focused, tests that are more maintainable, give better feedback and are fast to run.

In this talk, I will introduce and demonstrate task analysis techniques that can help us break down a system. We will identify the different technologies a system is comprised of, the actions each technology carry out and their integration with other parts of the system. From there, we will learn how these actions and integrations can have automated tests run against them using a varied range of automation tools. Examples would include JavaScript unit tests for JS components, Visual comparison tests for rendered HTML and API tests for contract changes between services.

Through the demonstration of task analysis and range of tools, we will learn that by breaking down a complex action, we can identify and create multiple targeted tests that when ran together give us richer feedback and are more maintainable than a full stack test can.


By the end of this session, attendees will be able to:

  • Describe the task analysis process and its value when applied to complex systems
  • Break down a complex system using task analysis to identify specific system actions
  • Review specific system actions to help identify different automated testing activities
  • Produce automated tests that run against specific system actions that when combined give us a wider view of our systems current state
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

In a dark, windowless room hidden in a top-secret facility in the middle of a military compound, I was faced with two choices – stay where I was and risk missing out on key moments in my children’s lives, or leave the safety and security of the job I knew and leap into the unknown, risking everything.

Well, that all sounds a bit dramatic!

My talk is about how I went from being a Communications Warfare Specialist for the Royal New Zealand Navy (with no experience in software, let alone testing), to launching into a career in testing and becoming an active member of the software testing community in Auckland.

I’ll tell tales of uncertainty and success, then leave you with some tips on how to make progress in your testing career.


  • How to take steps to grow your testing career
  • How to get started in a field you don't know much about
  • Where to find the people who can support your testing journey

Mike is the sole tester at Erudite Software, a software development company that specialises in web applications for the healthcare industry.

He writes a blog on testing and is involved in the Ministry of Testing Auckland chapter as a co-organiser for regular meetups and activities.

Find Mike on the following channels:

  • Twitter: https://twitter.com/TesterMikeNZ
  • LinkedIn: https://www.linkedin.com/in/michael-clarke-nz/
  • Blog: https://mikethetesternz.wordpress.com/
  • And in the Ministry of Testing Auckland Slack group

What does the term "integration test" mean to you? Something between a unit test and an end-to-end test? Integration tests are the most poorly-defined category of automated testing and also the most poorly understood.

Trish explains how to use both functional and dependency scope as a guide to understanding the wide range of integration tests. She also draws upon her deep experience in automated testing to describe examples of integration tests and the purpose of each. You will learn about hermetic tests, contract tests, data pipeline tests, and more in this engaging talk.


  • You will learn how to use functional and dependency scope to understand integration tests
  • You will go back to work equipped to explain what integration tests are to a range of audiences

Trish Khoo is a software development consultant and international keynote speaker. She has over 15 years of experience in the software industry, specialising in software testing, infrastructure and automation. Her journey has taken her from Microsoft to Google, from London to San Francisco, and many places in between. Now she helps companies all over the world with their software needs from her home base of Brisbane, Australia. She also dedicates time towards fostering a strong local tech startup community and mentoring other technologists. When she’s not doing this, she’s working on her creative pursuits – artwork, singing and writing. Learn more about Trish at her website http://trishkhoo.com

We will share stories of how we have helped teams embrace agile testing, and techniques you can implement immediately to become a more mindful and deliberate tester.

All the techniques are things anyone can do regardless of your work environment. You won’t need permission from your boss or buy in from you team to start, and we are sure that soon you will be influencing them. These techniques aren’t just for testers either, anyone that cares about quality and delivering great outcomes for customers can use them.

Come learn ways to be more curious, focus on deliberate learning, and foster a community. The only requirement is that you will need to be generous.


  • Prevent bugs by asking questions that surface assumptions and bring shared clarity
  • Make connections that help you understand and empathise with your users
  • Learn automation tricks that help you maximise your time testing even if you can’t code
  • Create a deliberate learning plan that focuses on increasing your productivity and skills

Observability is a term that is gaining in popularity and driving new thinking in the operation of software. It's an example of a word with a lot of momentum behind it, which may or may not have any impact to the testing role. You can probably think of some other examples of buzzwords floating around our industry that make you feel uncertain whether you need to learn about them or how much you need to know.

This session will give you an introduction to observability, with a twist. Katrina will present the journey that she followed to discover more about this emerging field. Her practical tips will help you to determine your own learning pathways in areas that interest you. Discover the people, practices, and potential within observability and be inspired to find out more about something else that is unfamiliar to you.


  • A basic understanding of observability and how the idea is maturing
  • How observability has an impact on organisations and ideas that I have seen applied
  • An approach to just-in-time and just-enough learning for new ideas

Katrina Clokie has over a decade of experience in the IT industry. She currently serves a team of around 100 testers as a Test Practice Manager in Wellington, New Zealand.

Katrina is an active contributor to the international testing community as the founder and editor of Testing Trapeze magazine, a co-founder of the WeTest New Zealand testing community, a mentor with Speak Easy, an international conference speaker, frequent blogger and tweeter.

Katrina is also the author of the fantastic book 'A Practical Guide to Testing in DevOps'.