Nordic Testing Days 2025

To be announced

In this deep-dive technical session, I'll share how Uber revamped its mobile testing approach using large language models (LLMs) to create DragonCrawl - a system that tests mobile applications with human-like intuition. I'll walk through how we transformed mobile testing from a maintenance-heavy, script-based approach to an intelligent, adaptive system that can handle UI changes automatically across multiple languages and cities.

The session will cover:

• The challenges of traditional mobile testing at scale (3,000+ simultaneous experiments)
• Architecture and implementation of DragonCrawl using MPNet and embedding techniques
• Real-world examples of DragonCrawl's adaptive behavior and problem-solving capabilities
• Practical strategies for handling LLM challenges like hallucinations and adversarial cases
• Results and metrics from production deployment
• Live demonstration of DragonCrawl in action

Key Takeaways:

• Understanding how to leverage LLMs for automated testing, including model selection criteria, architecture decisions, and implementation strategies that enable human-like testing behavior
• Practical techniques for handling LLM challenges in production systems, including specific approaches to manage hallucinations, adversarial cases, and edge scenarios
• Real-world insights into scaling automated testing across multiple languages and locations without maintaining separate test scripts, including specific metrics and benchmarks from Uber's production environment

There's a reason people in tech are notorious for answering questions with questions like "what do you mean by X?" or "that depends".

Human language is kinda vague and sloppy, but context usually fills in the blanks, and we're used to be able to clarify on the spot, but that doesn't work when we try to tell machines what to do, or when when we're putting words in documents that other people in other contexts are supposed to understand. This is, in my experience, where bugs usually occur – in the assumed understanding of constructs - the conceptual "things" we use in language, like "hour", "border", "flower", "write", "red" and "sound". In other words, things go wrong when we think that everyone must mean the same thing, when we think something is clarified enough.

The first step in uncovering these bug-generating mistakes is becoming aware of them and getting creative about alternative meanings, and that's part of why it's so much fun being a tester.

In this talk I will present some of my "favourite" constructs to challenge, and some useful cues to help you notice that a construct you're using should be investigated closer.

Key Takeaways:

• A structured way of using construct validity as an attack vector for finding bugs, even without looking under the hood, like you had x-ray vision.
• A list of very common problematic constructs, and why they keep tripping people up, again and again.
• Some phrases you may choose, to come across as less annoying, when you actually care about what others dismissively refer to as "just semantics" .

Playwright stands out as a powerful tool, but what exactly sets it apart from other automation solutions? This talk aims to introduce attendees to the key differentiators and capabilities that make Playwright a superior choice for web testing.
 
We will begin by exploring the fundamental strengths of Playwright, such as its ability to handle browser interactions with remarkable speed and efficiency. However, the true power of Playwright lies in its advanced features that go beyond basic functionalities.
 
Throughout the session, we will delve into a carefully curated list of real-world use cases where Playwright has demonstrated its superiority over other automation tools. These examples will highlight how Playwright excels in testing complex web applications within large organizations, showcasing its robustness and versatility.
 
One of the standout features of Playwright is its support for authentication contexts. This allows testers to simulate different user sessions and roles seamlessly, making it easier to test applications that require user authentication. Additionally, storage states enable the preservation of cookies and local storage data between tests, ensuring consistency and reliability in test scenarios.
 
Another powerful capability of Playwright is its tracing feature, which provides detailed insights into test execution. This includes capturing screenshots, network activity, and console logs, making it easier to diagnose and debug issues.
 
By the end of this talk, attendees will have a comprehensive understanding of how Playwright's advanced features can enhance their testing experience. They will learn how these capabilities not only improve the efficiency and effectiveness of their tests but also make the overall testing process more enjoyable and productive for engineers.
 
Key Takeaways:

• Superior Web Automation Capabilities: Understand what sets Playwright apart from other web automation tools, including its high execution speed and efficient browser interactions.
• Advanced Features for Enhanced Testing: Learn about Playwright's powerful features like authentication contexts, storage states, and tracing, which significantly improve the testing experience and make it more efficient.
• Real-World Use Cases: Gain insights from real-world examples where Playwright has proven its superiority in testing complex web applications within large organizations.
• Improved Debugging and Diagnostics: Discover how Playwright's tracing feature provides detailed insights into test execution, helping to diagnose and debug issues more effectively.
• Comprehensive Testing Framework: By the end of the talk, attendees will be equipped with the knowledge to leverage Playwright's advanced capabilities, making their testing processes more robust and enjoyable.

Modernizing the testing of payment systems in the Nordic region’s largest bank is a complex journey in a highly regulated, legacy environment. With millions of daily transactions  and billions of euros going through our systems, ensuring fault tolerance and system reliability is critical — not just for the bank, but for society at large. As the financial sector faced increasing pressure from regulatory demands, the need to move from mainframes to modern software, and demands for faster time-to-market, we recognized that our current traditional QA approach was unsustainable and  not scalable for future demands.

This presentation will share our journey of transforming QA into a business enabler. We navigated significant hurdles, including securing senior management buy-in, managing high delivery pressures, and shifting mindsets from manual testing to automation-driven quality. By focusing on foundational improvements — such as evolving our test automation framework, updating our tool stack, including integrating CI/CD, optimizing test environments, and implementing fast technical checks — we achieved remarkable results.

We reduced test cycle times from three weeks to just three hours, increased automation coverage to 75% across all test levels, and improved production quality by minimizing incidents. This transformation accelerated software releases and strengthened trust across teams and leadership.

Join us to learn the critical lessons, challenges, and best practices for modernizing QA in a large-scale, complex financial ecosystem.

Key Takeaways:

• What you should consider when you start your journey of uplifting your QA
• What are the pre-requisites of your journey, what you should do it
• How to convice people around you that you are doing correct things

In a world where over 1 billion people live with disabilities, accessibility is no longer optional — it’s essential. The European Accessibility Act (EAA), coming into full effect in June 2025, sets a legal framework that requires businesses to provide accessible digital goods and services. This creates both a compliance mandate and an opportunity to unlock new markets, improve user experiences, and foster innovation.

We’ll explore the current challenges in accessibility testing, such as the limitations of automated tools, the importance of real-user feedback, and the complexities of testing emerging technologies like AR/VR. Learn from real-world examples, including how Accenture has partnered with clients to integrate accessibility into their digital ecosystems by integrating it into their design and development pipelines.

The talk will also introduce cutting-edge trends, such as AI-powered accessibility tools, inclusive design thinking, and the integration of accessibility into CI/CD workflows. Practical steps will be shared, including how to involve diverse users in testing and the critical role of an accessibility statement in building trust and driving continuous improvement.

Attendees will leave inspired to champion accessibility as a mindset and practice, equipped with actionable insights to create inclusive, user-friendly digital experiences that benefit everyone. Whether you’re a tester, developer, or decision-maker, this talk will show you how accessibility can be a catalyst for innovation and inclusion in your projects.

Key Takeaways:

• Accessibility Drives Innovation and Opportunity: Embrace accessibility to unlock new markets, improve user experiences, and future-proof your business.
• Think Beyond Compliance: Leverage cutting-edge tools and inclusive design to create meaningful, barrier-free digital experiences.
• Commit to Inclusivity: An accessibility statement isn’t just a policy—it’s a promise to your users and a tool for continuous improvement.

To be announced

To be announced

Often you will not be aware of how your mindset is influencing your behaviour and testing skills. Experience a mindset shift and learn how to get back on track.

Join me in an exciting experiment and allow me to transform your mindset! I will demonstrate (live!) how easily your mindset can be influenced and how to break free from its limitations. We will do this together, in a live experiment. Me and you: The audience (or, my test subjects).

Your state of mind not only affects your behavior, but also that of those around you. You can utilize your mindset to enhance team communication and productivity.
In testing, maintaining an open and flexible mindset is crucial, especially in the face of distractions and unexpected events. It's essential to adopt the right mindset to uncover the quality of your test object. If you enter the testing process with the wrong mindset, you may overlook critical bugs or assume quality.

Instead, embrace a mindset that will uncover bugs and quality. To take control, you must be aware of your mindset and develop the skills to change it. I will share tips and tricks on how to become aware, and how to adapt your mindset to reach your goals.

Key Takeaways:

• External influences affect your mindset
• Break a negative spiral in your own mindset
• Your behavior influences others

When I started my current assignment as a Test Manager, the clients organisation was trying to visualize how good the teams were working with test and quality by counting bugs the teams filed during development. Since then, we have thankfully come a long way.

Inspired by the Quality Criteria in the Heuristic Test Strategy Model we decided to collect and visualize test data in accordance of the Quality Criteria (QC) in ISO 25000. In this presentation I will share how we have setup all reporting, from bugs to test case results to exploratory test sessions, so that it connects to the QC's. This way, we can have an automatically updated board, created in Power BI, to visualize the current status as well as trends.

The idea is to help the organisation to understand not only what have been tested (and the results) but also what have not been tested. The aim is not to provide an objective truth but expose information so that the right questions can be asked to the development organisation. For example: Why have there not been any testing performed on usability? Do we need usability tests or is this out of scope?

Key Takeaways:

• Theory behind using Quality Characteristics and the value of tracking the affected QC for test cases, test sessions and issues, and the overview that helps the organisation to understand the current status. 
• A little bit how practical add of new fields in test management tools such as Azure DevOps Test. 
• How information can be read and visualized in business intelligence tools such as PowerBI

In the rapidly evolving landscape of software development, ensuring robust and reliable testing is critical for delivering high-quality applications. This session will explore the powerful synergy between Playwright, a cutting-edge testing framework, and AI technologies, to revolutionize UI and API testing. Playwright’s capability to handle complex scenarios across multiple browsers and platforms makes it an indispensable tool for modern development teams. By integrating AI tools such as ChatGPT, Cursor, and Claude with Playwright, we can dramatically accelerate test creation, reduce manual effort, and improve overall test coverage. This session will feature practical examples of how AI can be leveraged to: Generate efficient test cases Automate the creation of Page Objects Streamline API testing workflows A live demo will highlight the real-time integration of AI with Playwright, showcasing how to create and execute UI and API tests seamlessly. Attendees will gain tangible insights into the benefits of AI-enhanced automation, including increased efficiency, scalability, and reliability. Whether you are a QA engineer, developer, or test automation enthusiast, this session will equip you with actionable strategies and tools to optimize your testing processes. Join us to discover how AI-driven test automation with Playwright can shape the future of quality assurance.

Key Takeaways:

• AI-Powered Test Automation – Utilize AI tools like ChatGPT and Claude to automate test case generation, create robust Page Objects, and build reusable components, streamlining the test automation process.
• Integration with Playwright – Leverage AI with Playwright’s code generation (playwright codegen) to speed up automated test creation while reducing manual effort.
• Maximized Coverage & Efficiency – Enhance test coverage and productivity by combining AI-driven prompts with Playwright’s multi-browser capabilities, optimized Page Object patterns, and automated API testing workflows.
  

At Nordic Testing Days, I’m excited to share my journey at Wolt and provide actionable tips on how to unlock faster, more robust mobile releases. I’ll present four key strategies that I hope every audience member can take away and apply to their own release processes.

Over my 14-year career in IT, I’ve experienced a variety of approaches to production releases across desktop, web, and native mobile applications. For the past four years at Wolt, I’ve focused on testing and refining the release processes for our native mobile apps. When I joined, Wolt’s small consumer mobile team followed a release cycle that took 3–4 weeks to ship updates to customers. Over time, we transformed our approach, evolving our release strategy to achieve faster, more efficient, and higher-quality releases—ultimately reducing the cycle to just one week.

1. Quality Assurance to Quality Assistance
Transitioning from the traditional quality assurance model to a quality assistance approach significantly streamlined Wolt’s mobile release process. Historically, a small group of QA engineers handled release testing, but as the company rapidly scaled, this assurance-based model became unsustainable. By adopting the assistance model, we empowered teams to take ownership of their testing, involving everyone in the testing phase throughout the development cycle. This shift not only accelerated release timelines but also fostered collaboration and accountability across teams.

2. Defect Prioritization
Over the years, developers, QA engineers and stakeholders at Wolt actively addressed issues as they were discovered, whether from team feedback, support reports, or App Store reviews. While this approach showed great responsiveness, it often resulted in fixing too many issues and significantly slowing down the release process. The constant flow of new commits also increased the risk of new regressions in the application. To tackle this, we introduced a prioritization framework to rank the issues identified during the release process. This framework helps us decide which issues are critical to fix and which can be deferred, ensuring a smoother and more predictable path to production.

3. Automation
Test automation was a game-changer in shortening the release cycle. Manually running hundreds of tests was neither efficient nor scalable, so we explored and experimented with various tools and approaches to find the most effective solution.  The key was identifying the most critical parts of the app to test at both the UI and unit test levels. Additionally, we revamped our CI pipeline to better support the release process, enabling faster, more reliable builds and deployments. Automation became a cornerstone in ensuring speed and quality while reducing the manual workload on the team.

4. Be Brave and Roll!
While Android and iOS ecosystems have their own default release processes, we discovered that following them too cautiously can be both time-consuming and unnecessary. Most issues are typically caught early in the rollout, allowing for faster adjustments if needed. Emphasizing the importance of feedback loops, tools like Crashlytics and other third-party providers play a crucial role in monitoring releases and ensuring a smoother journey. Sometimes, taking a confident approach and accelerating the rollout can save time while maintaining quality.


In this talk, I’ll share how we transformed Wolt’s mobile release process—from 3–4 weeks to just one week—by adopting a Quality Assistance model, prioritizing defects effectively, leveraging automation, and embracing faster rollouts with robust feedback loops.

Key Takeaways:

• Testing is not just QA’s responsibility, it’s a team effort.
• Defect prioritization: making the right fix at the right time.
• Release automation is more than just unit and UI tests.
• Releasing native apps isn’t always about following Google and Apple’s standard flow.
  

In an era where speed and seamless interactions define digital success, website performance can make or break the user experience. Core Web Vitals (CWV), a standardized set of performance metrics defined by Google, have become essential for measuring web quality from a user-centric perspective. This session will introduce the three CWV—Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS)—highlighting their direct impact on both user satisfaction and business outcomes.

Designed specifically by a software tester with extensive experience in CWV, this talk will uncover why CWV are critical in  web application quality strategies, demonstrating how they expose performance bottlenecks often overlooked during development and testing. Attendees will gain useful insights into measuring and analyzing these metrics using tools like Lighthouse, PageSpeed Insights, and Real User Monitoring (a technique that captures actual user interactions to assess real-world performance).

Beyond the theory, this session will provide actionable guidance on integrating CWV into your testing pipelines, reporting performance issues with more detail and clarity, and collaborating effectively with developers to drive meaningful improvements. Whether you're new to performance testing or seeking to expand your expertise, you'll leave equipped with practical techniques to embed performance accountability into your quality culture.

Key Takeaways:

• Core Web Vitals Help to Quantify the Web Performance Quality
  • Metrics like LCP, INP, and CLS directly measure the user’s experience with loading speed, responsiveness, and visual stability.
  • Good performance enhances user satisfaction, retention, and even SEO rankings.
• Software Testers Play a Critical Role in Helping to Discover Performance Issues
  • Testers can identify performance risks early by integrating Core Web Vitals checks into their test plans, CI/CD pipelines, and monitoring.
  • Performance testing isn’t just a developer’s task—collaboration between testers and developers drives a shared quality mindset.
• Practical Tools Make Performance Testing Accessible to Testers
  • Tools like Lighthouse, PageSpeed Insights, and Real User Monitoring simplify measuring Core Web Vitals.
  • Testers can track, report, and prioritize performance issues alongside functional defects for a more complete quality strategy.

To be announced