Nordic Testing Days 2025

Teams in software delivery come in all shapes, sizes and methodologies. There are a lot of things they have in common such as tools, documents and processes. They have documents that confirm how they start work on a story called a definition of ready. How they know they are done is called a definition of done. Some even have their ceremonies documented such as stand ups and retrospectives etc. 


What is also very common in every team is the undocumented or “unwritten rules”. 
As the name implies they are not discussed and you should just know them. From someone new coming into the team or with a different neurodiverse background. It makes working together just a little more difficult or frustrating at the beginning.
As an example the unwritten rules could be about not taking meetings before 9.15 to accommodate the school run. There are so many others. 


In this tutorial you will learn all about the unspoken communication that happens between a team focused on the area of accessibility. It will cover what you can do to bring these unwritten rules into the light and work better together. 


This full day tutorial teaches how to create and maintain team charters while using a focus of accessibility. On June 28th 2025 the European Accessibility Act (EAA) will become law. It will apply to all businesses trading in the European Union. Digital Accessibility is not something you can do once and it is done. Establishing accessibility practices as part of everyday or ongoing practices should be the norm. For those companies who are working towards compliance, this tutorial will help you embed digital accessibility in your process and ensure it becomes part of your quality journey. Digital Accessibility is not a nice to have or an optional choice anymore. Now is the time to act. 


Key takeaways:

• Understand the basics of accessibility 
• Become aware of the European Accessibility Act (EAA) 
• Understand what Charters are 
• Understand what accessibility Charters are 
• How they can help your team communicate better 
• Experience exercises that you can do with your team 

Improvisational comedy—sometimes called improv—is a form of theather in which the performance is created in the moment. Successful improv involves learning and using a variety of skills and techniques which allow performers to quickly adapt to a constantly changing environment and new information. Now reread the previous sentence, but replace the word improv with testing.
 
In many ways, improv is a great analogy for testing. As both an experienced improviser and tester, Damian Synadinos presents some of the many similarities between improv and testing. Each improv tip and trick is thoroughly described and demonstrated with help from the audience. Damian then explains and shows how the very same idea can be applied in a testing context. Using creative metaphors and critical analysis, old ideas about testing are reframed in novel and notable ways.
 
Whether novice or experienced, you are sure to laugh, learn, and leave with ways to help improv(e) your testing!

Key takeaways:

• Discover the purpose of testing
• Important testing fundamentals and techniques
• Have some Fun!

Playwright has become one of the main tools for testing web applications. In this packed 1-day tutorial, we'll learn how we can use it to automate and test web UI.

We'll see how to write, run and debug Playwright tests. We'll go over locators and expectations, the building blocks of Playwright, and also talk about the async aspect of the operations. We'll talk about refactoring the tests using the Page Object Model, and  also see how we can use it for API testing.  

On top of that, we'll discuss where Playwright fits into the testing work - what types of tests fit Playwright more, and when they can be replaced with simpler tests. We'll also see how to run the tests in CI environment. 

The exercises will be in JavaScript and Python. Attendees will download the exercise from GitHub before the session start.

Key takeaways:

• How to write Playwright tests with navigation, locators and expectations. 
• How to plan tests and scenarios 
• How to debug tests