Book A Workshop or Tutorial

I offer several workshops and tutorials that you can book with me. Both formats are highly interactive and work best when participants actively work on the tasks and exercises. Depending on your team, their background in the specific topic and, last but not least, cost, workshops are 1:45 to 3:00 hours long, tutorials 4: to 6:00 hours.

Here’s how it works: If you’re interested, email workshops.by@seasidetesting.com, and we’ll set an appointment to clarify what’s best.

Fast Feedback Using Ruby

Previously presented at a London Tester Gatherings Workshop in London, BoosterConf in Bergen and the Agile Testing Days in Potsdam, this session will introduce ways to get feedback about code behaviour in Ruby.
The subheadline is ‘From interactive code experiments to automatically running code’, and a teaser video prepared for the Agile Testing Days is available on Vimeo.
This session includes a 110-page booklet for every participant.

Summary

Do you spend too much time manually performing tasks like running automated tests and reformatting files? Would you like to know how to make these tasks happen whenever you save a file to disk? In this workshop, you’ll learn ways to get the fastest possible feedback on changes you make in your project.

This workshop shows you how to resolve these pain points by reformatting a text file. The same technique can be used to achieve much more complex tasks!

We take the following steps in the workshop:

  • We explore how to express a simple task in Ruby using an interactive Ruby shell. We are running Ruby code on the command line and immediately see the result of your code.
  • We’ll write a Ruby script that we can call from the command line. This allows us to run the same task with various input files.
  • We’ll set up a tool to watch our files for changes and run the Ruby script whenever the file is changed, i.e. when we save it to disk.

The workshop assumes some programming knowledge: if you can program in a language like Python, Java, or JavaScript, you will be able to play along. If you already know Ruby, you’re fine.

Here are some examples to illustrate how I use this kind of automation: In one project, I run all unit tests whenever production or test code changes. In this case, a system notification displays the test result. In my e-book projects, I automated checking cross-links in the book, i.e. references to chapter titles defined elsewhere. A third project used text-based tables to express workflows. The tables are transformed into a kind of flow diagram. This visual representation was helpful in finding test scenarios I needed to cover.

The workshop is packed with exercises, and attendees will get an e-book covering everything from the session and help you set things up after the workshop.

Fun with U̡̟ͩ̊̏ͬͯni͑c͐̀͢od̲̎ͅḕ̶̩͙͆

Presented at the Agile Testing Days 2023 in Potsdam, participants had fun and immediately understood what this is about. A ‘xeet’ and a toot show this:

Summary

❧❦☙ 

Annoying customers by not accepting their input is expensive. Imagine Jørn, the tester: He found a new tool to make his work much more straightforward and wanted to buy it.

However, when trying to enter his delivery and payment details, the website wouldn’t accept his entries. Instead, it displayed error messages: 

  • One field claimed: “Your name is invalid.”
  • Another one said: “E-Mail too long.”
  • The third one complained: “Invalid input.”

Jørn may decide to buy from another website or use a different product. Claiming that a potential buyer’s name is invalid is rude and may cause you not to get the sale. Chances are high that Jørn takes his business to a place that can properly handle his name.

This workshop covers essential aspects of testing applications with processing Unicode in mind. After a definition and overview of Unicode, we will look deeper into UTF-8, the most used Unicode encoding.

You can try out the concepts or ideas presented just before in exercises. Among other topics, the activities will cover the following:

  • Different kinds of spaces
  • ‘Soft hyphens’ and other usually invisible characters
  • A good number of ‘special characters.’

❧❦☙