Technical Testing & Test Automation

Spor 2 | Track 2

Kl.10.30 | In English

Humans, Code & Agents: The New Test Automation Era

By Richard Seidl from Richard Seidl Consulting

Abstract:

The role of the Test Automation Engineer (TAE) is becoming increasingly important - it sounds simple like combining "technical development skills" with "testing and quality skills" - but the real effects are huge. Test Automation Engineers often build an important bridge between the business and the technical side.

Richard will explain how testers can grow into automation by learning coding skills - and how developers can strengthen their quality focus by adopting a testing mindset.

Often testers fear the transition into "technical" automation. With modern learning methods and AI-assisted tools, testers can learn, create, maintain, and analyze automation more efficiently.

When we look into the future, where intelligent agents take over specific tasks in the test automation lifecycle - such as test generation, optimization, and environment control - there is someone who will orchestrate this "team". And the TAE is ideally suited for this.

You will leave with a clear understanding of the current and future skills required in test automation.

Learning Objectives:

You will learn:

  • To understand the evolving role of the Test Automation Engineer

  • To overcome fear of code through practical entry points

  • To differentiate between classical automation and agent-based approaches

  • To define a personal upskilling roadmap towards becoming a TAE

  • To prepare for future collaboration with AI and autonomous testing tools

Session Outline:

  • Testing as an activity vs. testware as a product

  • Identifying business needs and expectations for testware

  • Considering users and designing testware accordingly

  • Implementing and maintaining testware as a product

  • Roadmap and current progress

Target Audience:

Advanced (hands-on experience with the topic)

Kl. 11.30 | In English

WebDriver BiDi: The Future of Browser Automation is Now

By Boni García from Universidad Carlos III de Madrid

Abstract:

Browser automation is a software technique that allows automated execution of user actions on a web browser. This technique, mainly used for test automation, is implemented by popular tools like Selenium, Cypress, Puppeteer, and Playwright.

W3C WebDriver BiDi (bidirectional) marks a significant milestone in browser automation. This new standard revolutionizes how developers interact with web browsers by enabling real-time, bidirectional communication.

WebDriver BiDi is already supported in Selenium and Puppeteer. Moreover, Playwright and Cypress have started adopting WebDriver BiDi to handle browser automation, particularly in response to the Chrome DevTools Protocol (CDP) deprecation for Firefox by the end of 2024. This talk illustrates through examples how the new features supported by BiDi (i.e., browsing context, actions, scripting, logging, and network) are being implemented in these four tools.

Learning Objectives:

You will learn:

  • the fundamentals of WebDriver BiDi - learn how it differs from traditional WebDriver and why it represents the future of browser automation.

  • how WebDriver BiDi enables advanced automation scenarios like listening to browser events, intercepting network requests, and debugging through real-world use cases.

  • how to set up and use WebDriver BiDi in Selenium, Playwright, Puppeteer, and Cypress through practical examples and hands-on experience

Session Outline:

  • Browser Automation tools: Selenium, Playwright, Puppeteer, and Cypress

  • WebDriver BiDi modules: browsing context, actions, scripting, logging, network

  • Examples: BiDi in Selenium, Playwright, Puppeteer, and Cypress

Target Audience:

Basic (no prior knowledge)

Kl. 13.15 | In English

BUILDing Quality: Test Automation strategy definition for decentralized applications (dApps)

By Arthur Mkrtchyan from TestingArt

Abstract:

The Web3 industry delivers groundbreaking solutions but also introduces unique complexities that make traditional testing approaches insufficient. Many teams underinvest in testing or skip it entirely, leading to unstable products and dissatisfied users.

This session presents a practical, layered approach to testing decentralized applications (dApps). The discussion covers unit testing for smart contracts, efficient UI-level automation, and handling integrations such as Metamask and wallet interactions. It also includes designing reliable test environments using development chains and testnets, and combining all these elements into a complete test automation strategy. Addressing testing across all key levels ensures dApps meet quality standards, reduce defects, and deliver a reliable user experience from launch onward.

Learning Objectives:

You will learn:

  • Core concepts of Web3 and decentralized applications (dApps)

  • Unique testing challenges in Web3 development

  • Design and implementation of tests at the smart contract, API, and UI levels

  • Reliable test environment setup for different dApp phases

  • Complete test automation strategy for dApps

Session Outline:

  • The evolution of the web, Web3, blockchain, smart contracts, dApps

  • Key challenges of dApp testing

  • Real-world examples across test levels: smart contract unit testing, integration testing, UI-level automation

  • Designing effective test environments using development chains and testnets

  • Bringing all layers together into a comprehensive test automation strategy

Target Audience:

Intermediate (basic understanding of the topic)

Kl. 14.15 | In English

Practice Overwrites Textbooks: Challenging the Test Pyramid

By Arturo Mora-Rioja from Business Academy Copenhagen

Abstract:

The test automation pyramid (Cohn, 2009) has been praised by literature on software testing and implemented by companies for years, valued for its logic and ease of implementation. However, recent critiques (Axelrod, 2018; Ferrera, 2023; Gupta, 2024) highlight its limited applicability to certain project types.

This presentation examines its strengths and limitations through recent surveys of Copenhagen-area software companies and an in-house case study. Findings reveal that exhaustive unit testing can harm codebase quality when business logic is minimal or architectures are highly distributed (e.g., microservices). Integration testing has grown in importance, while modern tools have made end-to-end testing more robust than previously assumed. These insights challenge the pyramid’s traditional hierarchy, suggesting that alternative models may better reflect the complexities of contemporary software development.

You will gain a nuanced perspective on when to embrace—or deviate from—the pyramid, informed by empirical data and practical experience.

Learning Objectives:

You will learn:

  • How to understand the rationale behind the test automation pyramid

  • Why the test pyramid is not as applicable today as it was when originally conceived

  • Gain a deeper understanding of the relevance of each test level for different types of software development project

  • How to explore alternatives to the test automation pyramid for specific software development project types

Session Outline:

  • Background: why the test automation pyramid came into existence

  • Literature review

    • Definition and redefinition of the test pyramid

    • Challenges to the test pyramid

  • Practice assessment

    • Experiences by companies in the Copenhagen area

    • Case study: the CIRCE project

  • Conclusions

Target Audience:

Intermediate (basic understanding of the topic)