Let’s Test 2019 South Africa

Let’s Test 2019 will take place in the Western Cape’s picturesque seaside town of Gordon’s Bay at the premium Krystal Beach Hotel. The hotel has a spa and beautiful blue pool on the sun deck. The elegantly appointed rooms feature stunning views of the marina and beautiful mountains in the area. The Krystal Beach Hotel is only 40km and a 35 minute drive from Cape Town International Airport.

Gordon’s Bay is a harbour town situated close to wine regions, 35kms from an African penguin colony at Stony Point, and the beautiful major attractions of Cape Town. It is named after Robert Jacob Gordon, the Dutch explorer of Scottish descent.

The conference runs for 2.5 days between 24 – 26 November 2019 and will have an intentional focus on the craft and community of Context Driven Testing. We will showcase not only South African talent, but also host new and familiar faces and minds from the global community.

If you are not already on our mailing list, please subscribe here to make sure you don’t miss any announcements!

And please have a look at our Sponsorship page if you are interested in becoming one of our valued sponsors!

Cindy, Louise and Matthew

Sunday (Day 1)

Let’s Test 2019- Sunday (Day 1) Talks & Speakers


Alison Gitelson & Regina Martins

@AlisonGitelson @gianamar &


Empowering the forgotten tester to take ownership of creating a better outcome for themselves & their teams. Conflict Circles is a tool that helps resolve disagreement and increase alignment, especially where there are silos of people, and capabilities, that need to deliver on a product together.


Often testers are the forgotten people, only remembered close to the deadline, normally imposed by business, when the code needs to be tested. This is usually the first time they get notice that their services are needed. They weren’t part of the original project scoping, or estimation. In Agile teams, they were not involved in the sizing of stories and yet sit with all the work at the end of the sprint. Conversations with testers also reveal that many feel that they don’t have a voice and when they do express themselves not much attention is paid.

In this workshop we are going to introduce and work with a tool from Human Systems Dynamics called Conflict Circles which will help testers to speak up, clarify what is happening and clear the way for open, productive dialogue and work. Participants will have the opportunity to take a real-world issue that they are dealing with and work with it to make the tool real.

Learning outcomes:

  • Learn to use a tool to clarify what is fact and what are assumptions and perceptions about that fact
  • Learn how to get clarity on what others see, think and feel about the fact
  • Be able to generate a set of questions to help people move forward generatively
  • Grow your confidence in speaking up to share your viewpoint
  • Enhance self-awareness and listening skills to improve communication


Regina aims for continuous improvement in her personal and professional lives and her daily mantra is to be a better version of herself each and every day. She is an Agile coach, trainer, and facilitator, and gets energised when she’s involved in facilitating teams of all shapes and sizes steer for better outcomes.
She started her career in banking and moved into ICT about 18 years ago where she has fulfilled many roles. Recently she led a software development team to successfully deliver strategic change to a bank in Mauritius using Lean and Agile methods.
As a facilitator and coach she spends much time getting teams from across the organisational hierarchies to communicate effectively. As a Radical Collaborator she also coaches people to get rid of defensiveness to collaborate better with each other and with other teams.
She has taken it upon herself to develop new conference speakers to help keep the agile community in South Africa fresh.
Certifications: CSP, CSM, CSPO, CLP, KMP, TBR Practitioner, HSD Professional, Certified Radical Collaboration Trainer.

Alison Gitelson of CanBeeDone is a maximizer, facilitator and growth enabler.
She combines over thirty years of technical and management experience (in healthcare, ICT, engineering, education, government and NGO sectors) with a deep understanding of human behaviour.
Hating to see time and effort wasted she helps leader-managers to bring out the best in themselves and the people they work with, so the people and the business can thrive.
Alison has successfully led teams through transformation and change, and mentored other leader managers to do the same.
Her workshops consistently receive high ratings and are received as informative, engaging, practical and transformative by clients from a broad spectrum of businesses. She is a popular presenter at Agile and Lean conferences and events.


Craig Risi



Unpacking the world of unit testing in a way that a tester can understand and contribute towards, bring the tester closer to the code and allowing for improve collaboration between developers and testers.


Bringing testers closer to the code. We talk a lot about the testing triangle and how we need to focus more on the lower level unit and component tests for most of our coverage. However, in my experience unit tests and how to effectively write them remains a mystery for many testers and in this workshop I want to unlock the idea behind unit tests, how to write them in an effective way that ensures a high coverage, mitigates the need for too many higher integration tests and most importantly, makes them easy to read and contribute to for testers.

In this workshop I want to share my experience as both a developer and a tester in highlighting the mind-sets of both and how through collaboration between developers and testers, software quality can be greatly improved through effective unit testing. The workshop will focus on elements like reading code, discussing the different unit testing approaches, tips on how to write unit tests in a simple way and cover things like mocking and coverage analysis to improve coverage and scope of unit tests.

The workshop will be mostly technical, but also include a few soft skill tips to aid the communication and provide testers with more confidence to help change the unit testing culture in their teams.


A man of many talents, but no sense how to use them. I could be out changing the world, but would prefer to make software instead. I have a passion for software design, but more importantly software quality and designing systems that can achieve this in a technically diverse and constantly evolving tech world. When not playing with software I can often be found writing, designing board games or running long distances for no apparent reason.


Lyle McCreesh


In the world of professional E-sports, the metagame or meta refers to how gamers develop strategies and techniques in order to win.
I believe that thinking about software testing from this point of view can help testers develop strategies to be successful in their current role and beyond.


The metagame describes the highest level of strategy in gaming. Early references to it could include chess, poker or even rock paper scissors.
It describes a strategic way to play a game in order to increase the chances of receiving a desired outcome. For example in rock paper scissors, if you have shown three rocks in a row,
your opponent could think there is a chance that you will show a rock again. However you are banking on this strategy and end up showing scissors, in the hope that your opponent shows paper,
thus increasing your chances of winning a hand. In E-sports, there are rules that determine how games are played, and there are ways to take advantage of these rules to increase efficiency,
maximise resources and play the game optimally. Successful teams learn the basics and strategise around the normalised way to play a game and take advantage of this in order to win.


Software test analyst with a particular interest in context driven testing, clean code, software craftmanship, using lean and agile approaches to help add business value, electronic music and football and online gaming.


David Coomber


We’re used to time pressure, but having only a few months to verify years of data without adequate tools and budget just seemed too much. Necessity is, however, the mother of invention! My talk focuses on the novel ways we approached meeting our stakeholder expectations for data migration testing.


Data migration testing can be a daunting task – having to validate years of data in very little time. Managing the expectations of your stakeholders requires a solid understanding of the data being migrated as well as the tools needed to verify the fidelity of data post migration to a new data warehouse.  My team and I worked on multiple projects between 2012 and 2017 to move our organisations reporting data, changing data warehouse providers as well as underlying database management systems.

Delivering a large testing project without adequate budget is never great, but it is something that we have all become used to. I needed to find some creative solutions to help my team deliver and, ultimately, protect my organisations data.

My talk will delve into some of the detail of how we approached the above challenges – not only relating to the utilities we used, but also some of the politics around getting permission from management to buy or build the tools.


I have spent the last 20 years learning to be a better tester (but I’m not done yet).  I gathered my experience working in several industries as a team member, a team leader, a coach and a mentor – doing all that I can to inspire a love for quality.  As a member of the Cape Town Testing planning team, I assist in arranging quarterly conference-style meetups with a focus on software quality and making quality friends.

I recently joined Takealot in Stellenbosch, South Africa as an engineering team lead.


Beren Van Daele


RiskStorming is a visual, collaborative way of generating a visible Test Strategy. Which Quality Aspects matter most for your product? Which risks endanger those Quality Aspects? How do we test to make sure those risks don’t happen?


Testing is a craft, but it is also and for many foremost a job. A job you do day in day out, evolving with all the rituals every employee develops over time. These rituals, together with all sorts of other external factors (deadlines, pressure, etc.) often means that we don’t have a
test strategy or that we are no longer reconsidering the strategies we set out from the start. Having the right strategy in testing is important to stay as efficient and effective as you can be.
This workshop wants to reignite your strategic fire by placing you in small groups with your fellow testers, developers, analysts… Together you will devise a strategy for a hypothetical feature of a real life product which includes methods, tools and planning.
The workshop will use the TestSphere cards as a support to spark discussions and for bolstering your strategy.


Product Owner, Tester
I lead a company: Together with like-minded people who value communication and transparency above all else, we wish to grow a company that enables people to be themselves. Experts to the outside, a fellowship on the inside. Each member has the freedom to pursue their own merit,
whatever that looks like, while also bearing a responsibility to the continuation and growth of the company. With full transparency, we aim to facilitate communication between members to find a balance that makes sense for themselves.
I am a consultant: I am a Freelance consultant who shapes software delivery teams to improve on their work and their understanding of quality. Once a Software Tester, now a Remote Product Owner, I travel around, meeting software crafters all across Europe to learn from and teach.
I create things: – TestSphere, a testing card game that inspires and supports knowledge sharing – RiskStorming, a workshop that focusses the team on quality and risks
I run a conference & meetup: – BREWT is a place where software testing experts & peers share knowledge and learn from one another.


Gil Zilberfeld


The workshop is about organization, refactoring and managing automated tests and getting out of the “thousands of tests nobody knows what to do with”. Attendees get code and tests with different anti-patterns and testability issues and make them better.


As the code changes, the tests change too. This session is about the actual work we call “maintaining the tests”.
We will discuss test relevancy and value, as the requirements change and when to (heaven forbid) abandon tests. We’ll see cases where we need to change the level of existing tests (unit, API, UI or any other type) as we add and change functionality, and replace them with the appropriate level.
We’ll see how to approach it from either test-first (BDD or TDD) or test-after. We’ll refactor the tests to make them generic, as the code becomes more generic, and change the language they describe the examples.
As we go we’ll touch on what makes them “maintainable”. This session is interactive, as I’ll explain the code and walk through the changes, as suggested by the audience. The code will also be available to the attendees to work on their laptops as we go.


Gil Zilberfeld has been in software since childhood, writing BASIC programs on his trusty Sinclair ZX81. With more than twenty years of developing commercial software, he has vast experience in software methodology and practices.
Gil is a lean consultant, applying agile principles for more than a decade. From automated testing to exploratory testing, design practices to team collaboration, scrum to kanban, and lean startup methods – he’s done it all. He is still learning from his successes and failures.
Gil speaks frequently in international conferences about unit testing, TDD, agile practices and communication. He is the author of “Everyday Unit Testing”, blogs at [] and in his spare time he shoots zombies, for fun.

Monday (Day 2)

Let’s Test 2019- Monday (Day 2) Talks & Speakers

Keynote: It’s Context-Driven, not Cult-Driven, Testing

Leo Hepis



“Context Matters. But does it matter nearly as much as our long-held beliefs?”


Once, Leo produced and co-edited a book on software testing, by putting strangers into one room, and asking them to share their testing experience on paper. It worked.

Tools for Complexity

Joanne Perold


Talk Abstract

We live in a world characterized by volatility, uncertainty, chaos, and ambiguity. What tools do we need to shift a system? How can we use the system’s inherent properties to shift patterns of behaviour to a more suitable fit for function? Join us in this workshop and experience the answers!


Canceled software projects litter the landscape like the galleons in the Graveyard of ships. Projects escaping the graveyard resemble Frankenstein. They lurch, not quite dead, but not that useful. Wrecks happen not to lack of will, character or effort, but due to insufficient skill in quickly changing conditions. We need different tools.

Testing is not just about software, very often it’s also about the humans in the system and the behaviours of those humans. In this workshop, we use the ABIDE* mnemonic to navigate the system properties. I look at how these properties have an influence on the system and how we can start to use them to shift behaviours, and create new patterns.

ABIDE Attractors Boundaries Identity Diversity, Difference, Dissent Environment

*(ABIDE comes from Dave Snowdens work on complexity and complex systems)

Workshop Takeaways:

Learn and experience how context variance results in different stories even for identical functionality By understanding what context really is, you will better identify your context at work and incorporate context aspects when describing your product You will walk away with a list of factors that affect context. When back at work, with each project you can grow the list, which in turn will help you identify context even better in future projects. Uncovering and adapting to context will make you deliver a greater value to your stakeholders


Joanne is passionate about helping teams and people grow and improve.

She is a graduate of PSL (Problem Solving Leadership) and has worked for more than a decade in the software industry in all areas of software development. She is interested in Complexity, Scrum, Lean, XP, Kanban, Neuroscience and many other topics and strives to create a toolbox of ideas from all of these that can be applied in context.

Interested in both people and process improvement, she is continuously learning and finding better ways to solve problems. Joanne has been a Scrum Master and Agile coach since 2009. She has spoken at conferences in SA, USA, Europe, Australia and Turkey

Paul Holland

Talk Abstract

Do you have to create Test Strategy/Test Plan documents? How about Test Reports? Are the documents you create just templated, cookie-cutter paperwork to check a box in the project plan?
This workshop will show you what it takes to make concise and effective Test Strategies and Test Reports.


In this workshop, Paul will describe what he feels should be included in Test Strategy and Test Report documents. He will show real examples and present a checklist of what could (and should) be included.
He will not present you with a template as he feels that test documentation needs to adjust to the specific context of the project but Paul will give a summary of the type of information that is critical to include.
He will also describe, and show examples, of what has worked for him in the past and what has not worked well.
Most participants should come to this workshop with a laptop so they can create their own test documentation.
If you do not have a laptop then you will have to pair up with someone who brought one.

Workshop Takeaways:

Learn and experience how context variance results in different stories even for identical functionality By understanding what context really is, you will better identify your context at work and incorporate context aspects when describing your product You will walk away with a list of factors that affect context. When back at work, with each project you can grow the list, which in turn will help you identify context even better in future projects. Uncovering and adapting to context will make you deliver a greater value to your stakeholders


Paul Holland is a Senior Director of Test Engineering at Medidata Solutions, Inc. in New York City.
Paul has over 20 years experience in software testing. Prior to joining Medidata in August 2016 he was Head of Testing at a small New York based consultancy for 2 years.
Previously he spent 2 years as the principal consultant and owner at Testing Thoughts, and 17 years at Alcatel-Lucent.
Paul specializes in adapting testing methodologies to reduce waste, and be more effective and efficient. Finding ways to document only that which needs to be documented.
Modifying reporting of test activities to provide actionable information to stakeholders and reduce/eliminate potentially harmful metrics.
Paul is one of only five instructors of the Rapid Software Testing course, developed by James Bach and Michael Bolton.
Before beginning his career as a software tester, Paul flew Sea King helicopters for the Canadian military.

Wander With A Purpose: Writing Charters For Your Exploratory Test Sessions

Elizabeth Zagroba



Do you chase weird bugs only to forget the purpose of your testing? Stay on track while capturing all the roads less travelled using charters. We’ll practice writing charters, and see how that affect what information we uncover while pursuing multi-threaded thoughtful questions about our product.


Ever find yourself in the middle of some weird behavior in your software wondering how you got there and whether anyone will care about what you find? Do you get the “why were you even looking there?” question when you report bugs? In my years of practice pair and mob testing with testers and developers from my product teams, I’ve see how easy it is to spend time getting lost in the product without looking for the information you need. Get lost no more! Learn to stay on track while capturing all the roads less travelled you discover while exploratory testing by using charters.

In this workshop, we’ll experiment with testing whatever we want without a focus and compare that to more focused exploratory testing using charters. We’ll see how writing charters affects what information we uncover. We’ll get feedback on the specificity of our charters when we hand them off to other participants and review their test reports. We’ll practice describing our ability to go down multiple levels into thoughtful questions about our product. And we’ll discover how focusing our testing through charters changes the story we tell about our testing to our stakeholders.


Elizabeth tests software at Mendix in Rotterdam, The Netherlands. She was the keynote speaker at Let’s Test in South Africa in 2018, and she’s spoken at Agile Testing Days’ and other conferences in North America and Europe. Her article about mind maps became one of the most viewed on Ministry of Testing Dojo in 2017. You can find Elizabeth on the internet on Twitter and Medium.

Bring Your Self

Bev Christensen


Apply Your context to the QA context.

A novel idea: What if we not only do a good job, but actually thrive and are energized by the work we do? Spend some time in this workshop getting to understand the unique value you add at present and the talents and interests you can bring to the party


We spend approximately 30% of our waking hours at work. For many, our ‘real life’ and interests remain outside of this block of time. This workshop will enable attendees to highlight their interests and passions and have the time to think of how these can be incorporated into their QA endeavour. The learning techniques incorporated into this interactive workshop are focussed and diffused thinking, peer sessions, writing, listening and speaking. The exciting thing about this, is that the ‘ah ha’ moments will continue even after the workshop ends, as the sub-conscious highlights even more ways of ‘bringing yourself’ to the place where you spend so much of your time. Let that time be well-spent and work not only in the QA space, but towards developing who you are.


Bev Christensen is a Software Quality Engineer working in Johannesburg. She started her career as a Developer and was introduced to Quality Assurance in 2004. She was so excited about this discipline that she immediately changed professions. This excitement has never abated. She has been involved in mentoring and training graduates and has been blessed to see them develop into strong, rigourous Software Quality Engineers. Bev is also passionate about experiential learning and enjoys sharing what she has learned with colleagues by incorporating many brain-engaged learning techniques into her workshops.

Git Like A Pro

Simon Berner



Have you ever wondered how the version control system Git works? Have you ever wanted to learn Git hands-on in a safe environment with a learning partner? Then this workshop is the perfect spot for you to experiment!


How valuable is your test code to you? Is it as important as your production code? If so, having a version control system in place which takes care of your test code is a must. But not only the selection and usage of a version control system makes you knowledgeable, no, mastering by failing, pairing, exploring and finally explaining it to others is what makes a cool kid.
Starting to use the version control System Git can be daunting and frustrating. But knowing how Git works and how to use it in your context is getting more and more essential, especially if you want to take care and share the test code in your team.
It’s a long way to the top if you want to Rock ‘n’ Roll with Git and this workshop is the perfect start for it. You will learn how to use the basic and more advanced commands on the cli. You will pair up with a tester fellow of the workshop group and explore the Git models and concepts which I will present to you hands-on.
Whether you are working with Git and want to refresh your knowledge or are a novice and eager to learn it, this workshop is for you. Don’t be shy, come in and explore with a learning partner in the group what Git feels like!

Key Learnings:

  • How Git works and not just which commands you have to execute
  • How to explore Git with the help of its concepts, models and a learning partner
  • How to setup and run your own Git repository manager
  • How to apply merge strategies on the client and server side
  • How to create your first Pull Request (if you haven’t done already)
  • How to have tremendously fun with Git and get addicted to it

For this workshop you should bring the following things along:

  • A modern laptop (OS: Linux, macOS or Windows10)
  • Admin privileges on your laptop!
  • Please install all the things described here, prior to the workshop
  • A portion of humor and explorer enthusiasm!


Simon says: Check my site:

Learning Integration: Getting the best value from my time here

Alison Gitelson


We learn by comparing new knowledge to old, making sense of it & moving it into stored memory. Without the space & time to do this we forget most of the new. This comfortable session will deepen your thinking, make sure you remember all the great things you have learnt & can use them back at work.


By the end of the session you will have:

  • Reflected on your experiences of the conference so far
  • More deeply explored your thinking or understanding of at least one session that you attended
  • Prepared yourself to use one (or more) new thought/tool/learning in your own work


Alison Gitelson of CanBeeDone is a maximizer, facilitator and growth enabler.

Tuesday (Day 3)

Let’s Test 2019- Tuesday (Day 3) Talks & Speakers

Building teams that pull together

Brian Van Vuuren


Image result for brian van vuuren cape town


‘High performing teams’ is a well-known concept in IT, and yet, we so often find that technical teams composed of individual superstars struggle to perform consistently well as a unit. This begs the question – if not individual ability alone, what other elements should we be focusing on in order to build and grow teams who pull together and perform well, even in a high pressure, highly competitive industry?

Fortunately; biologists, psychologists, business strategists have been researching this exact topic for many years – and it turns out that their principle findings hold true across the tech industry too.

And so, at a time in my life when I needed my team more than ever, I turned to the theory to help understand these concepts better. And what I learnt not only benefited me (and my team), but it inspired me to spread the simple truths about people, tech and people in tech, that make us more similar than we think and can be quite easily harnessed to uplift our teams to reach their full potential.


I studied Mechatronic Engineering at an undergrad level from 2010-1013. And hated it – so I studied some more…

This time I transitioned to Industrial Engineering, in the field of simulation modelling. It was here that my eyes were opened to the weird and wonderful world of tech, and I kept studying to PhD level, working as a lecturer while I completed my studies.

Once qualified, I yearned to be part of a large-scale, real-world IT department, so I took a position at Allan Gray in Cape Town in 2018 as a developer and I’ve worked there ever since.

5 Levels of API Automation

Shekhar Ramphal


Talk Abstract

API testing usually involves calling an endpoint and asserting either response codes or response bodies. I’ll explain how to split that into 5 different levels to give you faster feedback and better scenario coverage by making use of technologies like docker kubernetes and mocking frameworks.


In my context we run a micro service architecture with a number (300+) of API endpoints both synchronous and asynchronous. Testing these in a shared environment with cross dependencies is both challenging and very necessary to make sure this distributed monolith operates correctly. Traditionally we would test by invoking an endpoint with the relevant query params or payload and then assert the response code or body for valid data / type definitions. This proved to be more and challenging as the push for CI and having common data sources meant dependencies would go up and down per deployment which meant flaky tests.

I will demonstrate how we leveraged newer technologies and split our API testing into 5 levels to increase our overall confidence.

I would like to elaborate and demonstrate these layers and execution and how this has changes the way we test and look at APIs. Would also touch on the tooling we use to achieve this and the pros/cons of using this approach.


Passionate about software testing, Computer engineer by qualification. Full stack testing in all areas from manual QA, system design and architecture, to Performance and security as well as automation in different languages.

Becoming a Better Mobile Tester

Kamlesh Bansal



Mobile app testing can be complex, time-consuming, error-prone and sometimes expensive. It is absolutely necessary that you make sure that the user experience is awesome for every user every time they use your app, and that starts from their first try. This is where you need a great mobile tester.

Attendee Requirements: Attendees should bring a Mobile device and a laptop with the Xcode/Android studio installed. The workshop can be attended by developers, testers and also product managers.


Mobile app testing can be complicated, time-consuming, error-prone and sometimes expensive – if not done properly. Mobile app testing is a yet critical task to ensure your end-users have a positive user experience when they use your mobile app. It is absolutely necessary that you make sure that the user experience is awesome for every user every time they use your app, and that starts from their first try. Testing mobile apps is a unique craft. It needs specific skills and mindset. According to various data analytics, nearly 1 in 4 people abandon mobile apps after only one use. Therefore, it’s very important to have a great user experience in mobile apps for its sustainability in this competitive market. Testing applications on mobile devices have their own set of challenges with the constantly changing operating systems, platforms, and technologies. Most of the mobile applications are easy to use but they are equally difficult to test and it’s very easy to miss critical defects. It’s very important to think out of the box while testing the mobile apps and take into consideration various external/internal factors that can adversely impact your mobile app. During my career in the mobile testing field, I have encountered different unique bugs and I have created various artefacts learning from them. This session will give users on how to approach mobile application testing focusing on all aspects like functional, security and performance. In this workshop, you will learn about mobile application testing through hands-on activities, exercises, and discussions. You will also learn about various tools which can help you in testing mobile apps. You will explore mobile testing techniques on your mobile device, so a mobile device, smartphone, or tablet is required.

Key takeaways: Experience report from real life mobile testing. Unique Mobile app bugs encountered Learning the tricks of mobile testing Sample Mindmap to cover mobile testing Learning about various mobile testing tools Learning debugging the mobile app issues Learning about various CI tools for mobile


Kamlesh Bansal is a highly experienced software professional with more than 12 years of diverse experience spanning different industries like life sciences and telecommunication. He has been involved in several challenging projects and had the chance to work in several different countries, including USA, UK and India. He has written articles and papers on software testing, and regularly attends international and national conferences. He is known for his coaching and mentoring skills, and has built various testing teams from scratch. During his career, he worked extensively in software testing, development and automation; software testing has become his passion. He is currently working as a Manager, Test Engineering at Medidata Solutions and has experience leading & building the Mobile testing team

Load Testing with Gatling

Gerald Mücke & Simon Berner

@gmuecke & @alientester &


Gatling is a modern load testing tool in which scripts, scenarios and tests are written in a programming language. In this workshop we walk through the basics, record and create a full test scenario and put our example webshop application under stress until it breaks using Gatling.

Attendee Requirements: Participants should bring their own laptops with sufficient privileges to execute Java programs (hardened corporate laptops often won’t work).


Load & Performance Testing is an important part in developing software. It reveals crucial information such as response times, capacity and throughput which are important to any stakeholder having to make a decision. Putting load onto a system until it crashes is nothing new. But in practice, load or stress tests often go short because of time or budget constraints. Gatling is a modern tool to address this shortcoming allowing to efficiently write and maintain performance tests and include their execution into CI/CD pipelines.

In this workshop you will learn the foundations of performance testing, how to create and execute user scenarios and load models with Gatling.To juice up theoretical basics, you’ll be faced with challenging practical exercises.


Gerald Mücke is a Java developer and Test Automation Engineer with more than 14 years of industry experience starting in various roles around software development and testing. He is an independent software development consultant and is especially interested in test and operational topics. Apart from practicing the software craft in general his focal point lies on test automation strategies and performance testing.

Simon says: Check my site:

When You Think There Is No Time For Learning Or Coding

Eleftheria Batsou



Do you want to learn something new, expand your knowledge, develop yourself and be the best you can be? I am going to share my story, how I make time to work and how you can grow and advance in your career. After this talk, you ‘ll be inspired to work smarter, make new habits and push yourself.


Do you ever feel like you’re stuck in your career? Do you constantly feel like you don’t have time to work on your projects? Do you want to learn something new, expand your knowledge, develop yourself and be the best you can be?

In this session, I am going to share my story on how I started coding, how I make time to work on side projects and how you can grow and advance in your career. After this talk, I hope you ‘ll be inspired to work smarter, make new habits and continue pushing yourself even when things fall apart.

I will present some helpful tips about self-motivation, time-management, setting priorities and goals, staying organized, believing in yourself and keeping a balance between your career and personal life. To do so, I’m going to use as an example my personal story of how I got into the tech world, the struggles, the rejections, what I’ve learned and how you can succeed by being consistent and determined. Additionally, in this session, we are going to talk about building the habit of coding and the benefits of it. We are going to explore ways of finding mentors in your job and outside of it and also expanding your social network.

This talk is not only about getting better at your 9 to 5 job but also about developing yourself.


The speaker is a passionate front-end developer and UI designer from Greece. She is working as an AngularJS developer while taking up a master’s degree in Graphic Arts and Multimedia. She is also creating educational content for several platforms such as Packt, Udemy, Skillshare, at the same time, she produces motivational talks and how-to videos on her youtube channel. She is self-motivated and working hard to make this world a little bit better every day. When she isn’t glued to a computer screen, Eleftheria spends time working out and strolling in the nature. Her friends would describe her as easy-going, passionate about life and the fastest chocolate eater.

What’s in your ‘go-bag’? How I landed my next Quality gig.

Sandra Kambo



Hang around the testing field long enough, and you will probably find yourself having to make a role transition in the ways we test depending on the trends, organisation or maybe even the applications you’re testing. I recently went on a hunt for a role that would allow me to continue on my chosen path of quality assistance and automation. In this talk, I’ll fill you in on my experiences interviewing to find this fit, share trends I noticed across applications, practical things I did to prepare, as well as skills that you should probably stay on top of given the current trends. Hopefully, you pack a few more essentials, skills and tips into your go-bag as a tester.


My software testing career spans years with local and international startups and organizations, coming from a background in software engineering. I’m an event organizer and sometimes speaker, for the Quality engineering meetup in Nairobi and the Agile KE  meetup locally. After my selection as an emerging leader for TechWomen in 2014,  I gravitated toward actively contributing via mentorship to community projects focussed on education and enablement of young girls and women teaching experiential STEM skills. This has become a large part of my happy place that has grown me loads and I keep learning from to date.  This I do, from my role as co-founder and project coordinator for TechWomen Kenya.

Our sponsors

To find out how you can become a sponsor, visit our sponsoring page or contact us directly at info(at)

We’d like to say thank you to our sponsors who make Let’s Test South Africa possible.

Click on the sponsor logos to find out more!



23366_AG Logo_Australia.indd





Let's Test Conferences on Context-Driven Testing - For Testers, By Testers

When we say ”for testers, by testers” we mean that our main goal for these conferences is to make them a valuable experience for all participants, not to make a profit. We are ourselves a team made up of serious, passionate and professional testers. After attending the original Let’s Test conferences that started in Sweden in 2012, we decided to bring the magic to beautiful South Africa to foster the testing community in Africa and provide an opportunity for others to visit our gorgeous country and share and learn at the same time! You can be sure that we’ll never compromise on the “for testers, by testers” principle.