BEGIN:VCALENDAR
VERSION:2.0
X-WR-CALNAME:ntd2026
X-WR-CALDESC:Event Calendar
METHOD:PUBLISH
CALSCALE:GREGORIAN
PRODID:-//Sched.com Nordic Testing Days 2026//EN
X-WR-TIMEZONE:UTC
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260603T053000Z
DTEND:20260603T060000Z
SUMMARY:Registration And Morning Coffee
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:D-Saal\, Kultuurikatel
SEQUENCE:0
UID:0ae52b2de79665b00472b63668c35e0c
URL:http://ntd2026.sched.com/event/0ae52b2de79665b00472b63668c35e0c
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260603T060000Z
DTEND:20260603T140000Z
SUMMARY:Ai-Powered E2E Mobile Testing With Appium And Mobile Mcp
DESCRIPTION:Writing mobile tests with Appium can be challenging. Many of us have dealt with unstable selectors\, differences between Android and iOS\, or slow progress. What if we could use artificial intelligence with Appium? And what exactly is Mobile MCP?\n\nTutorial Overview\n\nThis tutorial is for anyone interested in starting mobile testing with a modern approach. We’ll use Python throughout. Together\, we will build an end-to-end framework where AI supports us from the beginning. We will see how tools like Mobile MCP can find elements without needing static IDs or XPath.\n\nWe’ll focus on building full end-to-end scenarios. We’ll test whether self-healing really works or is just hype. We’ll also look at where AI can speed up our work\, and where we still need the Appium Inspector.\n\nNote: This is a hands-on tutorial and requires some preparation upfront. We’ll send you detailed instructions in advance.\n\n\nAgenda\nAI in Appium: We’ll talk about the main challenges in classic mobile testing and what AI can help solve.E2E framework architecture: How to set up a project for AI-powered end-to-end testing\, going beyond the basic Page Pattern.What is "Mobile MCP"? We’ll give a practical introduction to the tool and show how it works with Appium.AI vs. Appium Inspector: We’ll see how AI can find elements in an app as they change.Building an E2E Scenario: Step by step\, we’ll create a full test path\, like logging in\, searching\, and adding to the cart.Intelligent assertions and self-healing: We’ll see how AI helps check the app’s state and what it does when the UI changes.Results analysis: We’ll look at how AI can help us figure out why an end-to-end test failed.Summary: AI in mobile - revolution or evolution? We’ll finish with a Q&A session.\n\n
CATEGORIES:TUTORIAL
LOCATION:Puupakusaal\, Kultuurikatel
SEQUENCE:0
UID:db2ae27d45eb81bbea870e7031fc00a4
URL:http://ntd2026.sched.com/event/db2ae27d45eb81bbea870e7031fc00a4
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260603T060000Z
DTEND:20260603T140000Z
SUMMARY:Beyond Assert(True): Hands-On Testing For LLMs And AI Agents
DESCRIPTION:Traditional software is deterministic: the same input yields the same output. Large Language Models (LLMs) and AI Agents have shattered this rule\, introducing an inherently probabilistic paradigm. How do we ensure quality when the ground truth is shifting? This tutorial bridges the gap between traditional QA and AI evaluation. We will move beyond simple prompt testing into validating complex multi-agent systems. Participants will learn to build test oracles that evaluate intent and semantics rather than exact matches\, evolving the QA role from a code verifier to an evaluation framework architect.\n\nLearning Objectives\nBy the end of this workshop\, participants will be able to:Deconstruct AI Architectures: Identify specific testable layers such as Shell (API/UI)\, Orchestration (Context/Tools)\, and Inference Core (Probabilistic).Build Modern Test Oracles: Implement aggregated and property-based oracles using Python to handle non-deterministic outputs.Validate Multi-Agent Systems: Apply a four-level framework to test communication\, delegation\, and error propagation between AI agents.Execute AI Red Teaming: Identify vulnerabilities such as prompt injection\, hallucinations\, and safety bypasses.Automate Quality Metrics: Integrate BERTScore and RAG-specific metrics such as Faithfulness and Relevance into CI/CD pipelines.Target Audience & PrerequisitesTarget Audience: QA Engineers\, SDETs\, and Developers working with or transitioning to Generative AI systems.Prerequisites: Basic knowledge of Python and API fundamentals. Participants must bring a laptop with VS Code and Python installed.\nWorkshop OutlineThe Paradigm ShiftTheory: Deterministic vs. probabilistic testing. Agent taxonomy.Practice: Environment setup and executing your first fuzzy test.Oracles & OrchestrationTheory: Atomic vs. aggregated oracles. Testing the orchestration layer.Practice: Writing scripts to validate JSON schemas and output consistency.Semantic EvaluationTheory: RAG metrics such as Faithfulness and Relevance. Introduction to BERTScore.Practice: Building an LLM-as-a-Judge evaluator to grade complex answers.Multi-Agent TestingTheory: Inter-agent communication and task delegation loops.Practice: Debugging a workflow where a Travel Agent delegates to a Finance Agent.Red Teaming & SecurityTheory: Prompt injection\, mutation testing\, and metamorphic testing.Practice: Simulated attack scenarios\, bypassing safety filters\, and implementing guardrail fixes.QA Strategy & GovernanceTheory: Human-in-the-loop workflows and production monitoring.Practice: Designing a full-scale QA strategy for a real-world GenAI product.\n
CATEGORIES:TUTORIAL
LOCATION:TBD\, Kultuurikatel
SEQUENCE:0
UID:359e71bdd8ec64fc8e4575fabe498faa
URL:http://ntd2026.sched.com/event/359e71bdd8ec64fc8e4575fabe498faa
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260603T060000Z
DTEND:20260603T140000Z
SUMMARY:How to Lead Testing at the Organizational Level?
DESCRIPTION:Test leadership is required at organizational and operational levels in many organizations. In this tutorial\, we explain the fundamentals of test leadership and have practical exercises to understand it. We discuss what leadership means in different scenarios\, where effective test leadership is needed\, and where leadership is all too often missing.\nTesting leadership is always needed\, even if testing or development is subcontracted. Especially in larger organizations\, organizational leadership is needed for testing\, for example\, to set the vision\, harmonize testing across teams\, increase productivity\, align testing activities\, and support different management levels and teams involved in testing.\n\nThe tutorial utilizes the ACT2LEAD heuristic about software testing leadership. To understand it properly\, the audience is divided into teams with a brief exercise for each part of the heuristic. The ACT2LEAD heuristic consists of eight core practices of testing leadership.\n\nWe’ll go through eight principles in practice:ACT - how to add testing into all software development actionsCONTEXT - how to choose the right testing based on contextTRANSPARENCY - how to create visibility for the quality of testing practices and test results2 - how to strike the perfect balance between automated testing and human-driven explorationLEARN - learning as a way to improveENABLE - enabling a culture of quality and continuous improvementADAPT - aligning testing efforts with product risksDIVERSE - implementing diverse testing approaches for finding diverse sets of defects and observationsThe tutorial uses most of its time on several exercises set in the context of a large\, imaginary corporation case study. In teams\, participants create software testing leadership artefacts for the case study organization. The exercises are designed for the organizational level\, but they also fit the team level.\n\nThe tutorial is ideal for roles like Head of Testing\, QA Lead\, and Test Manager. It is also good for anyone who wants to develop their competencies toward test leadership.\n\nEach participant is encouraged to bring a laptop\, though one per four people is sufficient. Internet access is needed\, too.\n\nEach participant gets an ACT 2 LEAD Software Testing Leadership Handbook as an e-book\, which they can use to study this topic further.\n\nA high-level outline of the tutorialWhat is testing leadershipACT2LEAD heuristic for testing leadership\, including a brief exerciseOrganizational and operational levels of testing leadershipShort introduction to leading people and changeExercise: Stakeholder mappingExercise: Create an organizational-level testing policy (principles)Exercise: Create an organizational-level strategy (guidelines)Exercise: Extended retrospective for visibility and continuous improvementExercise: Testing in contractsExercise: Competence developmentOptional Exercises\, e.g.\, on Shift Left\, Recruiting\, Visibility\, People\, OKR\n
CATEGORIES:TUTORIAL
LOCATION:D-Saal\, Kultuurikatel
SEQUENCE:0
UID:42b45c546d7cd7dc1530deaf7e650a18
URL:http://ntd2026.sched.com/event/42b45c546d7cd7dc1530deaf7e650a18
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260603T060000Z
DTEND:20260603T140000Z
SUMMARY:MCP Playwright & Playwright Agents Workshop
DESCRIPTION:This full-day\, hands-on tutorial dives into test automation using the Model Context Protocol (MCP) and AI agents. Participants will first master the MCP architecture\, the standardized foundation for AI-driven applications.\n\nThe core of the tutorial focuses on Playwright's AI Agents (Planner\, Generator\, Healer). You will learn to leverage these agents to:Intelligently discover and map application test surfaces (Planner).Automatically generate executable Playwright code from natural language specifications (Generator).Implement self-healing mechanisms to automatically detect and repair broken tests after UI changes (Healer).The session covers integration techniques\, including connecting MCP with GitHub Copilot for an issue-to-implementation workflow\, and best practices for production-ready\, CI/CD-integrated test suites.\n\nPrerequisites:Basic understanding of JavaScript/TypeScriptFamiliarity with web testing conceptsNode.js 18+ installedVS Code or similar IDE\nTutorial Objectives:\nBy the end of this tutorial\, participants will be able to:Understand the Model Context Protocol (MCP) architecture and its role in AI-driven automationSet up and configure MCP Playwright servers in multiple environmentsLeverage AI agents (Planner\, Generator\, Healer) for test automationBuild intelligent\, self-healing test automation frameworksIntegrate MCP with GitHub Copilot and other AI toolsImplement best practices for production-ready test automationTutorial Agenda\nMorning Session (9:00 AM - 12:30 PM)9:00 - 9:30 AM: Welcome & Tutorial IntroductionParticipant introductions and icebreakerTutorial objectives and expected outcomesOverview of the day's scheduleEnvironment setup verification9:30 - 10:45 AM: Module 1 - Understanding MCP (Model Context Protocol)What is MCP and why it mattersThe evolution from custom integrations to standardized protocolsMCP as the "USB-C for AI applications"MCP Architecture deep diveClient-Server architectureMCP Host\, Client\, and Server relationshipsData layer: JSON-RPC 2.0 protocolTransport layer: stdio\, SSE\, WebSocketsMCP vs traditional approaches (ChatGPT plugins\, custom APIs)Real-world use cases and success storiesHands-on Exercise 1:Setting up your first MCP serverConfiguring Claude Desktop/VS Code with MCPTesting basic MCP connectivityResources Provided:MCP architecture diagramsConfiguration templatesTroubleshooting guide10:45 - 11:00 AM: Coffee Break11:00 AM - 12:30 PM: Module 2 - Playwright MCP FundamentalsIntroduction to Playwright MCP ServerMicrosoft's official implementation vs community alternativesKey features: accessibility tree usage\, deterministic actionsSupported capabilities: vision\, PDF handlingMCP Server architecture for PlaywrightBrowser automation via MCP protocolTools\, Resources\, and Prompts in MCP contextStorage modes: persistent vs isolated profilesDemo Session:Installing Playwright MCP:&nbsp\;npx @playwright/mcp@latestConfiguration options and argumentsConnecting MCP to different clients (Claude Desktop\, VS Code\, Cursor)Live demonstration of browser automation via MCPHands-on Exercise 2:Configure Playwright MCP in your development environmentCreate your first AI-driven browser automationUse natural language prompts to navigate and interact with a demo websiteCapture and analyze accessibility snapshotsChallenge: Automate a simple e-commerce flow (browse → add to cart → checkout) using only natural language prompts through MCP.Lunch Break (12:30 - 1:30 PM)\nAfternoon Session (1:30 PM - 5:00 PM)1:30 - 3:00 PM: Module 3 - Playwright AI AgentsIntroduction to Playwright Test AgentsThe three agents: Planner\, Generator\, HealerAgent workflows and lifecyclePlanner Agent: Intelligent test discoveryHow it explores applicationsGenerating comprehensive test plansGenerator Agent: Automated test creationConverting test plans to Playwright codeNatural language to code translationHealer Agent: Self-healing testsDetecting and fixing broken testsAutomatic locator updatesHandling UI changesDemo Session:Setting up Playwright Agents:&nbsp\;npx @playwright/test init-agentsLive demo: Planner agent exploring a web applicationLive demo: Generator creating tests from specificationsLive demo: Healer fixing failing tests after UI changesHands-on Exercise 3:Initialize agents in your projectUse Planner agent to explore a sample applicationGenerate test specs in Markdown formatConvert specs to executable Playwright tests with GeneratorIntroduce breaking changes and use Healer to repair testsGroup Activity: Teams work on different sections of an e-commerce application\, comparing agent-generated tests vs manually written tests.3:00 - 3:15 PM: Coffee Break3:15 - 5:00 PM: Module 4 - Advanced Integration & Best PracticesIntegrating MCP with GitHub Copilot Coding AgentHow Copilot uses Playwright MCPVerifying code changes in real browsersIssue-to-implementation workflowAdvanced MCP featuresCustom MCP servers for specific needsMulti-tool workflows (MCP + web search + internal tools)Security considerations and sandb...
CATEGORIES:TUTORIAL
LOCATION:Stalker\, Kultuurikatel
SEQUENCE:0
UID:26da8073d1871d2cbcb648b7abe603f1
URL:http://ntd2026.sched.com/event/26da8073d1871d2cbcb648b7abe603f1
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T051500Z
DTEND:20260604T060000Z
SUMMARY:Registration And Morning Coffee
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:8596317ad470ab886a6ae19f2e60ab47
URL:http://ntd2026.sched.com/event/8596317ad470ab886a6ae19f2e60ab47
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T060000Z
DTEND:20260604T070000Z
SUMMARY:KEYNOTE: The Irreplaceable 40%
DESCRIPTION:Artificial Intelligence is increasingly used to write test code. Today it is estimated that 60% of new test code is written by AI tools and this number will only continue to rise. Surprisingly\, however\, the testing is now the critical component needed is to ‘test’ the 40% that AI is unable to test itself\, that is where the future of testers.\n\nThat 40% is not busy work. This is not your typical motivational speech dressed up as another AI testing keynote. What I will talk about in the keynote is the three critical capabilities that are becoming more valuable not less\, and the underlying reason for this is that all of them depend on something that current models lack: the human intent behind engineering quality software for other humans to use.\nEngineer the Context Understanding: While AI can greatly amplify the effectiveness of testing\, the quality of results is only as good as the input you give it. In 2026\, the testers who will rise to the top will not be the ones who came up with the cutest prompt for the AI to answer. Rather\, they will be those who can successfully engineer the context of the problem for the AI to solve. We will look at real-world best practices for testing with AI\, and I will share an AI Assurance playbook for context engineering that will immediately raise the quality of your AI-infused testing. Review with Heuristic Judgment: AI generated test suites look good - until they fail to test what really matters silently. Green pipelines are the most dangerous artefact in organisations today. No one asks: what are we not testing? This capability helps organisations audit test suites generated by AI with a sense of heuristic judgement. I can explain how to design world class AI augmented tests like an experienced navigator reading a map to identify the blank spaces where organisation specific risks reside. Orchestrate Trust: Humans trust humans they still need decide when the machine is wrong. That is not a technical skill - it is a quality leadership act. This capability describes the shifting role of quality engineers to trust AI Assurance oracles. This capability explores the new role of orchestrating AI Assurance that trust across teams\, tools\, and stakeholders\, and answers the question: “Who is really responsible for quality?” \nBy the end of this keynote\, you will have an assessment of your skills in planning\, architecting\, designing and leading AI governance\, a practical plan of action to implement in the real world\, and the assurance that you will be “ready” to become part of the “Irreplaceable 40%”.\n\nKey Takeaways:\nContext Engineering is our New Superpower: AI-augmented tests are only as valuable as the context a human provides. Attendees will leave with a repeatable framework for curating system\, user\, and business context that transforms AI output from "technically correct" into "intent driven tests" - a skill that compounds in value as the important of testing of AI infused systems improve.Heuristic Auditing Catches the Real Truth: A passing automated test regression suite is not proof of quality\; it is proof that the tests you wrote passed. Attendees will gain practical heuristic-led auditing patterns to interrogate value-driven testing\, identify dangerous blind spots\, and ask the questions that thinking machines are structurally incapable of asking themselves.Trust Orchestration is the Quality Engineer's Next Career: The highest-value skill in an AI-augmented team is not technical testing - it is the ability to calibrate\, communicate\, and own confidence decisions across people\, tools\, and stakeholders. Attendees will understand how to position themselves as the trust architect oracles in their organisation increasingly needs\, turning a perceived threat into their most durable career advantage.\n\n\n\n
CATEGORIES:KEYNOTE
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:079dbc0aa871108006bc515f8ead616c
URL:http://ntd2026.sched.com/event/079dbc0aa871108006bc515f8ead616c
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T070000Z
DTEND:20260604T073000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Puupakusaal\, Kultuurikatel
SEQUENCE:0
UID:205de3866ee81d753aa55db0e423155b
URL:http://ntd2026.sched.com/event/205de3866ee81d753aa55db0e423155b
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T070000Z
DTEND:20260604T073000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:D-Saal\, Kultuurikatel
SEQUENCE:0
UID:7cdb1fd4815ea547aa41f540977d09cd
URL:http://ntd2026.sched.com/event/7cdb1fd4815ea547aa41f540977d09cd
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T070000Z
DTEND:20260604T073000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Terrassi\, Kultuurikatel
SEQUENCE:0
UID:8d3794b12eb7efa6e4f9ff839aa1dd5e
URL:http://ntd2026.sched.com/event/8d3794b12eb7efa6e4f9ff839aa1dd5e
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T070000Z
DTEND:20260604T073000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:b36bf34eba124529463f77dba03c54d1
URL:http://ntd2026.sched.com/event/b36bf34eba124529463f77dba03c54d1
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T070000Z
DTEND:20260604T073000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Stalker\, Kultuurikatel
SEQUENCE:0
UID:c9458258f34052abd67318f2e3a2588e
URL:http://ntd2026.sched.com/event/c9458258f34052abd67318f2e3a2588e
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T073000Z
DTEND:20260604T081000Z
SUMMARY:Building Quality Into LLM Powered Solutions
DESCRIPTION:As organizations rush to adopt Large Language Models (LLMs)\, many discover that building reliable\, trustworthy applications is far from straightforward. Unlike traditional software\, LLM outputs are non-deterministic\, context-dependent\, and vulnerable to issues like bias\, hallucinations\, and prompt injection. Ensuring quality requires more than testing—it demands&nbsp\;a holistic approach&nbsp\;that blends architecture\, safety\, observability\, and continuous feedback.&nbsp\;This talk explores practical strategies for embedding quality into LLM-powered systems from the ground up.&nbsp\;We’ll&nbsp\;cover methods for prompt design\, evaluation frameworks\, guardrails\, and hybrid architectures that improve accuracy and safety. Attendees will leave with a clearer understanding of how to balance innovation with reliability and how to design AI applications that are not only powerful but also consistent\, secure\, and&nbsp\;user-focused.\n\n\nKey takeaways:\n\nTesting LLMs requires new methods\, not just old QA practices.Combine automation + human oversight for best results.Build feedback and safety into the system from the start.Quality is a continuous journey\, not a release milestone.\n
CATEGORIES:TRACK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:c932899d49408e44846e6f4c38bc3b26
URL:http://ntd2026.sched.com/event/c932899d49408e44846e6f4c38bc3b26
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T073000Z
DTEND:20260604T093000Z
SUMMARY:Vibe-Coding For Testers: Building Custom Testing Tools Without Pinging Your Engineering Team
DESCRIPTION:Testers often need custom tools - data generators\, mock services\, internal dashboards\, or CI helpers - but building them traditionally requires significant development effort and prioritization. With modern AI-assisted coding\, we can now prototype and build these tools themselves\, minimizing both engineering and maintenance efforts.&nbsp\;In this session\, I’ll show real examples of using vibe-coding to create internal testing workflows\, interfaces\, and CI/CD helpers. I’ll focus on where AI significantly accelerates development\, where it introduces risks\, and how to apply guardrails to keep these tools maintainable\, secure and trustworthy.Rather than promoting “AI replaces engineers\,” this talk presents AI as a practical productivity amplifier for experienced testers who understand their systems and constraints.\n\n\nKey takeaways:\n\nHow to design and build tester-owned tools using vibe-coding without creating technical debtAttendees will learn how to approach AI-assisted development of internal testing tools (data generators\, mock services\, dashboards\, CI helpers) with clear ownership boundaries\, architectural decisions\, and sustainability in mind.A realistic mental model for AI-assisted coding in testing workflowsParticipants will gain a clear understanding of where vibe-coding provides real leverage for experienced testers\, where it breaks down\, and how to critically evaluate AI-generated code instead of blindly trusting it.Practical guardrails for security\, maintainability\, and long-term useAttendees will leave with concrete strategies for applying constraints - such as validation\, code structure\, reviews\, and documentation - to ensure AI-built tools remain trustworthy\, auditable\, and safe to evolve over time.
CATEGORIES:WORKSHOP 2H
LOCATION:Stalker\, Kultuurikatel
SEQUENCE:0
UID:6c6030e9002bf916dbf6264ce773390b
URL:http://ntd2026.sched.com/event/6c6030e9002bf916dbf6264ce773390b
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T073000Z
DTEND:20260604T123000Z
SUMMARY:Breaking Things On Purpose: Getting Started With K6 Load Testing
DESCRIPTION:Performance issues often surface only when it’s too late - after deployment\, when real users start to feel the impact. Load testing helps prevent that\, but many teams still see it as a complex or time-consuming task. This workshop aims to show how accessible and powerful it can be using k6\, an open-source\, developer-friendly tool designed for modern performance testing.The session starts with a short introduction to the fundamentals of load testing: what it is\, when to use it\, and the different test types supported by k6 - average\, stress\, spike\, soak\, breakpoint and smoke. Participants will also get a quick overview of how k6 works under the hood and how it integrates into a development workflow.From there\, we’ll move into a hands-on\, guided session\, beginning with a simple GET request and gradually expanding it into a complete load testing project. Each step introduces a new concept: adding thresholds and stages\, randomizing requests\, implementing assertions\, handling errors\, and organizing the project using npm and Prettier. We’ll then extend the script with multiple endpoints\, visualize live results on the web dashboard\, and perform authenticated requests using JWT tokens.Throughout the workshop\, I’ll share real-world experiences and lessons learned from conducting load tests on different projects—what to watch out for\, common pitfalls\, and how to interpret the results effectively.Participants will leave with both the theoretical foundation and practical skills to start creating their own performance testing setup using k6. All examples will be built live\, and attendees can follow along on their own laptops. Only basic JavaScript knowledge is required.\n\n\nKey takeaways:\nUnderstand the core principles of load testing and how to apply them effectively using k6 in real-world scenarios.Gain hands-on experience building and running performance tests step by step—from a simple request to a full\, maintainable testing suite. Learn practical insights and troubleshooting techniques drawn from real project experiences\, helping you avoid common pitfalls and get meaningful results faster.\n
CATEGORIES:WORKSHOP 4H
LOCATION:Puupakusaal\, Kultuurikatel
SEQUENCE:0
UID:edff733b6d4602966b6123ce95142592
URL:http://ntd2026.sched.com/event/edff733b6d4602966b6123ce95142592
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T073000Z
DTEND:20260604T123000Z
SUMMARY:Your Personal Leadership Pitstop
DESCRIPTION:How do you define yourself as a leader? How do you see your leadership? In this personal pitstop we will go over what being a leader means to you. At work\, at home\, or at your hobby\, your leadership skills matter. &nbsp\;They play a huge role in how you perceive the world around you\, and how others perceive you.&nbsp\;As a leadership coach\, I’ve picked up a lot of knowledge on how to help and train people on their leadership skills. In this workshop I’m sharing my best tips.We’ll look at where in your process you currently are\, and where you would like to go. We will do this via small games\, assessments\, and observations from the group. As a group we will help each other. We will set (achievable) goals for you to work on in your ‘Leadership Plan’ that you will take home.\n\n\nKey takeaways:\n\nAssess and identify your leadership styleUnderstand your communication styleCreate an achievable Leadership Plan to take home (that works!)
CATEGORIES:WORKSHOP 4H
LOCATION:Terrassi\, Kultuurikatel
SEQUENCE:0
UID:4ff4e14a5f087accbe0716ec3fd3c2cb
URL:http://ntd2026.sched.com/event/4ff4e14a5f087accbe0716ec3fd3c2cb
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T081000Z
DTEND:20260604T085000Z
SUMMARY:Koalas\, Branches & Pull Requests - A Tester’s Guide To Pull Request Reviews
DESCRIPTION:Pull requests\, aka merge requests\, are a goldmine of information that many testers are missing out on. Although pull requests are often seen as a tool mainly for developers\, they offer testers an equal opportunity to provide feedback.&nbsp\;When joining the review process testers can contribute to the software quality before changes are added to the codebase. They can use their unique perspective to uncover insights that go beyond the code. They will learn more about the bigger picture of the application. And ultimately\, testers can apply these observations to their testing and help the team prevent bugs.In this talk\, Andrea will introduce how testers can get involved in the pull request review process. She will demonstrate how testers can shift left and proactively engage with the source code changes. The step-by-step approach covers everything from checking policies and standards. It also includes looking at build pipelines\, code changes\, and unit tests. Starting with the basics\, the session gives clear examples at every stage\, making it easy to follow along.Andrea will highlight practical examples and insights drawn from real-life experiences\, providing actionable tips on how to get the most out of pull request reviews. The session illustrates how testers can analyze pull requests for quality\, learn more about the source code\, and make a real impact through their feedback.At the end of the session\, attendees will have a hands-on guide to reviewing pull requests. They will be ready to take a closer look at their team’s work and discover new insights\, just as curious koalas explore branches to find tasty leaves of eucalyptus. It’s time for testers and their teams to realise the untapped potential of making pull request reviews a shared responsibility.\n\n\nKey takeaways:\nUnderstand the elements of a pull request and know about the basic principles of the Git workflowLearn how to shift-left and contribute to the pull request review processBy the end of the session\, participants will be able to start reviewing pull requests
CATEGORIES:TRACK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:e80d0b799ef453b068038f93ec42d67a
URL:http://ntd2026.sched.com/event/e80d0b799ef453b068038f93ec42d67a
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T085000Z
DTEND:20260604T093000Z
SUMMARY:How To Survive In The Ai Jungle: Rethinking Test Strategies For An Ai Era
DESCRIPTION:Intro:Artificial Intelligence challenges almost every assumption the testing discipline is built on. Traditional testing depends on fixed inputs and predictable logic\, but AI systems are adaptive\, probabilistic\, and context-dependent. That means our classical test cases are no longer stable reference points.\n\n\nIn this 20-minute talk\, Nicole van Gijn explores what testing looks like when your system learns\, reasons\, and occasionally hallucinates. She introduces the AI Quality Grid\, a structured framework co-developed with John Kronenberg\, that helps define quality attributes\, risks\, and validation strategies for AI applications. The session bridges theory and practice through concrete examples from a real AI test project\, showing how LLM-evals and risk-based thinking can be combined to test prompt robustness\, output consistency\, and bias control within modern CI/CD pipelines.\n\n\nAttendees will walk away with a lightweight but actionable structure for AI quality assessment and a new mindset: understanding quality not as a checklist\, but as an intelligent\, adaptive discipline. Why this topic is relevant:\nAI systems are rapidly entering production pipelines\, yet testing methods lag behind.Testers and QA leads urgently need practical models to evaluate non-deterministic outputs. The AI Quality Grid offers a bridge between AI model evaluation (LLM-evals) and classical test strategy\, providing testers with new tools and thinking patterns to stay relevant in the AI era.\n
CATEGORIES:TRACK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:46288ea86b6ae52069060ba2bdf2218a
URL:http://ntd2026.sched.com/event/46288ea86b6ae52069060ba2bdf2218a
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T093000Z
DTEND:20260604T103000Z
SUMMARY:Lunch
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Puupakusaal\, Kultuurikatel
SEQUENCE:0
UID:189ff1641a957019d331a74b53b81d33
URL:http://ntd2026.sched.com/event/189ff1641a957019d331a74b53b81d33
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T093000Z
DTEND:20260604T103000Z
SUMMARY:Lunch
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:D-Saal\, Kultuurikatel
SEQUENCE:0
UID:3a5cdd1457769b7d6290ec8c3ae62765
URL:http://ntd2026.sched.com/event/3a5cdd1457769b7d6290ec8c3ae62765
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T093000Z
DTEND:20260604T103000Z
SUMMARY:Lunch
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:674867b8daba2ac85bf7d2feb6bfaa12
URL:http://ntd2026.sched.com/event/674867b8daba2ac85bf7d2feb6bfaa12
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T093000Z
DTEND:20260604T103000Z
SUMMARY:Lunch
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Terrassi\, Kultuurikatel
SEQUENCE:0
UID:79179be69ebd4359ce53621716bc5732
URL:http://ntd2026.sched.com/event/79179be69ebd4359ce53621716bc5732
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T093000Z
DTEND:20260604T103000Z
SUMMARY:Lunch
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Stalker\, Kultuurikatel
SEQUENCE:0
UID:8d011ef9b32375193ebbddd2a87603ae
URL:http://ntd2026.sched.com/event/8d011ef9b32375193ebbddd2a87603ae
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T103000Z
DTEND:20260604T111000Z
SUMMARY:Demystifying Continuous Deployment: From Weekly Tension To Daily Confidence
DESCRIPTION:Deploying to production shouldn't require a meeting\, three approvals\, and a prayer. Yet most teams treat every release like launching a rocket - mission control on standby\, everyone watching the countdown\, but no one wanting to press the red button. \n\nAt Sokos Hotels\, our web booking system handles thousands of reservations daily\, processing millions monthly across 50 hotels all over Finland and Estonia. One critical bug means lost revenue\; one outage means thousands of unhappy guests. We were trapped in weekly releases\, manual verification\, and the kind of Thursday tension that put everyone in the mission control room.&nbsp\;We asked ourselves if Continuous Deployment is just a myth.\n\nIn less than a year\, we broke the cycle. We went from weekly manual releases to deploying seven times per day with higher confidence than ever. The results? 4.5/5.0 customer effort score\, 40% higher conversion rates and 4.3+/5.0 overall team happiness. The secret? A testing strategy that made deployment boring for the last 2 years.\n\nJoin my talk to find out how we did it!\n\nWhat you’ll get from this talk:\nThe three signs your team is not ready for Continuous Deployment\, and the technical enabler that breaks the testing tension.&nbsp\;How we shifted from “QA signs off on releases” to "Quality is built-in"\, and why the cultural change was harder than the technical one.&nbsp\;The valuable failure lessons we learned along the way and what it taught us about green pipeline.\nYour takeaway: A practical\, battle-tested roadmap for testing-enabled Continuous Deployment. You'll leave knowing which tests to automate first\, how to build confidence without sacrificing speed\, and how to prove to skeptics that this isn't just another risky experiment. Real patterns\, real failures\, real results - ready to implement Monday morning.\n\nWho should attend: QA engineers\, test automation engineers\, developers\, engineering managers\, and DevOps practitioners who believe testing should accelerate delivery\, not slow it down.
CATEGORIES:TRACK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:67aa3fafed363121731a41a0b02a148e
URL:http://ntd2026.sched.com/event/67aa3fafed363121731a41a0b02a148e
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T103000Z
DTEND:20260604T123000Z
SUMMARY:Every Day Security Testing
DESCRIPTION:SummarySecurity testing sounds like it might be best left to the “experts”\, whoever they are\, but I will share how we can include it in our day-to-day testing. From exploratory testing to API and automated testing\, there are things that we can and should be doing.Through this workshop we will learn about the scope of security testing\, find out about the automated tools available and then spend some time practicing basic security testing techniques like SQL Injection\, Insecure Direct Object Reference and using browser developer tools.Setup- Attendees will need to bring a laptop or pair up. Any browser is fine but Chrome recommended.&nbsp\;- Screen & HDMI/equivalent for presenting slide & demos.ActivitiesFor a 2 hour workshop:- IDOR / URL manipulation- Bypassing UI using developer tools- Cross site scripting (XSS)- SQL injectionIf a 4 hour workshop is preferred\, I can add in additional activities including analysing session data and a Capture the Flag exercise.\n\nKey takeaways:\nRecognise that security testing is something that you can & should be doingIdentify the "low hanging fruit" security bugs in softwareExecute basic penetration tests against an online system
CATEGORIES:WORKSHOP 2H
LOCATION:Stalker\, Kultuurikatel
SEQUENCE:0
UID:78c6cb62ad08e45f341cf7297343aefc
URL:http://ntd2026.sched.com/event/78c6cb62ad08e45f341cf7297343aefc
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T111000Z
DTEND:20260604T115000Z
SUMMARY:I'll Let You Be The Judge? Testing Non-Deterministic Ai Systems
DESCRIPTION:The problem: it is too hard to understand and improve GenAI quality\, and yet organizations are moving ahead regardless.For AI engineers it’s hard to:- Increase accuracy due to lack of repeatable & representative testing- Understand reliability: know how\, why\, or when an agent will failThis leads to poor reliability and accuracy\, which:- Increases operational costs and can increase reputational damage- Erodes user trust\, reduces customer engagement\, and increases churn- Reduces business confidence\, slowing down AI adoptionIn this talk I will discuss the limitations of how we are current testing AI agents\, and why this means we are not adequately ensuring the safety of agentic AI systems. With non-deterministic systems like Generative/Agentic AI\, we need to simulate a large number of inputs (millions) and measure the outputs using judge agents to find the statistical success rate. This a process that is more similar to how we traditionally do load testing rather than the simple functional testing we’re using with AI right now. I will explain how you can instead use tools like AgentCore to create orchestration agents that build other types of agent to make this new type of non-deterministic testing possible.This approach will be for GenAI what traditional automated tests are for deterministic code- Auto generate representative testing material- Orchestrate tests against real AI endpoints- Judge outputs (minimum standards\, accuracy quantification)- Improve accuracy and reliability\n\n\nKey takeaways:\nCurrent functional testing techniques are inadequate for testing agentic/generative AI systemsWhat does it mean to use LLM as Judge agents? What are input agents?How can you create an AI testing orchestration pipeline for testing AI agents\n
CATEGORIES:TRACK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:d9d44abab65f90766e2212b8909a1a06
URL:http://ntd2026.sched.com/event/d9d44abab65f90766e2212b8909a1a06
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T115000Z
DTEND:20260604T123000Z
SUMMARY:Yes To Growth: How Adopting A Growth Mindset Can Change Your Life
DESCRIPTION:Most of us unknowingly carry limiting beliefs about our abilities\, often in the very areas where we have the most room to grow! A talented developer won't apply for a senior role because they think “I'm just not a natural leader”\, never considering that leadership can be learned. Or a designer brushes off feedback believing\, "Either you have an eye for design or you don't." Sound familiar?These are not signs of missing innate talent\, but rather the result of a fixed mindset\, a belief that your innate talent is set in stone. The good news is that this belief can be changed by adopting a growth mindset\, a belief that you are capable of growing and improving.&nbsp\;Drawing on insights from Dr. Carol S. Dweck’s pioneering research\, this talk explores how a fixed mindset makes us avoid challenges and crumble at criticism\, while a growth mindset helps us see both as fuel for improvement. I'll break down the real difference between fixed and growth mindset and we'll do an interactive exercise where you'll experience the shift yourself.The best part? Your potential isn't fixed. You will walk away with a practical strategy to stop protecting your ego and start building the skills necessary to get that senior role and tackling the challenges you've been avoiding.\n\n\nKey takeaways:\n\nParticipants will leave this session with:\nAn understanding of how we overestimate our knowledgeA clear distinction between fixed mindset and growth mindsetPractical strategies for adopting a growth mindset\n
CATEGORIES:TRACK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:c4976a618e0d8234403f37ae788de088
URL:http://ntd2026.sched.com/event/c4976a618e0d8234403f37ae788de088
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T123000Z
DTEND:20260604T130000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:05f25323d83bbdf4dcf29638d52b9541
URL:http://ntd2026.sched.com/event/05f25323d83bbdf4dcf29638d52b9541
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T123000Z
DTEND:20260604T130000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Puupakusaal\, Kultuurikatel
SEQUENCE:0
UID:59b0531ab871cf16887e3deb2716d120
URL:http://ntd2026.sched.com/event/59b0531ab871cf16887e3deb2716d120
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T123000Z
DTEND:20260604T130000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Terrassi\, Kultuurikatel
SEQUENCE:0
UID:a81153da54a6a932ba551dd8bf7b9027
URL:http://ntd2026.sched.com/event/a81153da54a6a932ba551dd8bf7b9027
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T123000Z
DTEND:20260604T130000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Stalker\, Kultuurikatel
SEQUENCE:0
UID:db55cbdc25e2cfdf4d94456ab13733bd
URL:http://ntd2026.sched.com/event/db55cbdc25e2cfdf4d94456ab13733bd
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T123000Z
DTEND:20260604T130000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:D-Saal\, Kultuurikatel
SEQUENCE:0
UID:f2611907e49f30fb7710388321c1913d
URL:http://ntd2026.sched.com/event/f2611907e49f30fb7710388321c1913d
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T130000Z
DTEND:20260604T140000Z
SUMMARY:KEYNOTE: What to Do When Your Industry Won’t Stop Changing
DESCRIPTION:Every few years\, software testing gets a new existential threat. Outsourcing was going to end QA careers. So was automation. Now it's AI. The doomsday headlines feel new each time\, but the pattern stays the same. You’re met with the same anxiety and the same conversations with peers wondering if QA careers have a future. The problem is that we treat disruption as destruction\, when in reality it’s an opportunity to reinvent yourself. And the people who do that well often share the same set of qualities. In this keynote\, Kristel Kruustük draws on 15 years in software testing and her experience as a founder to uncover the mindset\, habits\, and decisions that have kept testers relevant through every wave of change and will continue to do so when the next wave hits.\n\nKey Takeaways:&nbsp\;\nWhy disruption in software testing is a pattern\, not a one-time eventWhy the "AI will replace us" story misses what's actually happening in the industryReal examples of companies and roles that have come back stronger after changesHow to build resilience as a practical skill\, not an abstract traitWhat to do in the next 6 to 12 months to position yourself for what comes next\n
CATEGORIES:KEYNOTE
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:4b785f23ae23f422ce727f776282b183
URL:http://ntd2026.sched.com/event/4b785f23ae23f422ce727f776282b183
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T141500Z
DTEND:20260604T200000Z
SUMMARY:Dinner & Party
DESCRIPTION:\n
CATEGORIES:ACTIVITIES
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:1c56af39527af9477227010e36cf907f
URL:http://ntd2026.sched.com/event/1c56af39527af9477227010e36cf907f
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T160000Z
DTEND:20260604T200000Z
SUMMARY:Boardgames
DESCRIPTION:\n
CATEGORIES:ACTIVITIES
LOCATION:Puupakusaal\, Kultuurikatel
SEQUENCE:0
UID:001deef54f689572366e618791c4921e
URL:http://ntd2026.sched.com/event/001deef54f689572366e618791c4921e
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T160000Z
DTEND:20260604T170000Z
SUMMARY:Lighting Talks
DESCRIPTION:\n
CATEGORIES:ACTIVITIES
LOCATION:Stalker\, Kultuurikatel
SEQUENCE:0
UID:7d1026927d67049d795b4f1abc727936
URL:http://ntd2026.sched.com/event/7d1026927d67049d795b4f1abc727936
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260604T170000Z
DTEND:20260604T180000Z
SUMMARY:Powerpoint Karaoke
DESCRIPTION:\n
CATEGORIES:ACTIVITIES
LOCATION:Stalker\, Kultuurikatel
SEQUENCE:0
UID:e3f5310a7e8420619b8568710e0a4644
URL:http://ntd2026.sched.com/event/e3f5310a7e8420619b8568710e0a4644
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T060000Z
DTEND:20260605T070000Z
SUMMARY:Discussion Panel
DESCRIPTION:Join us for an exciting panel discussion with industry experts as they share perspectives on the state of AI\, Quality Engineering\, and Software Testing in 2026
CATEGORIES:KEYNOTE
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:f4835948e1f31bc4c7c7207a3c9c5641
URL:http://ntd2026.sched.com/event/f4835948e1f31bc4c7c7207a3c9c5641
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T070000Z
DTEND:20260605T073000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:113ec6670c1f36b895285a5c29adedb4
URL:http://ntd2026.sched.com/event/113ec6670c1f36b895285a5c29adedb4
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T070000Z
DTEND:20260605T073000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Puupakusaal\, Kultuurikatel
SEQUENCE:0
UID:2b17b855484eb232668e0d64549e900a
URL:http://ntd2026.sched.com/event/2b17b855484eb232668e0d64549e900a
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T070000Z
DTEND:20260605T073000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:D-Saal\, Kultuurikatel
SEQUENCE:0
UID:431f0dde3c0a1c7262139016c1b1769f
URL:http://ntd2026.sched.com/event/431f0dde3c0a1c7262139016c1b1769f
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T070000Z
DTEND:20260605T073000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Stalker\, Kultuurikatel
SEQUENCE:0
UID:5a04e109c1dcddb30ac9066b67ca3c7e
URL:http://ntd2026.sched.com/event/5a04e109c1dcddb30ac9066b67ca3c7e
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T070000Z
DTEND:20260605T073000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Terrassi\, Kultuurikatel
SEQUENCE:0
UID:de1bc1401ac84ab3977f8636c3d6b6c0
URL:http://ntd2026.sched.com/event/de1bc1401ac84ab3977f8636c3d6b6c0
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T073000Z
DTEND:20260605T081000Z
SUMMARY:Reinventing The Wheel
DESCRIPTION:Back in 2016 at trivago\, we were building a new Selenium-based test framework with Cucumber\, but the standard reporting tool wasn't quite fitting our needs. It showed lots of information\, but finding the key details about which scenarios failed and why meant digging through charts and stats that weren't really helpful for our workflow. During a company hackathon\, I decided to build something more focused on what we actually needed to see.\n\n\nI used Cucumber's JSON output and some templating to create Cluecumber—a cleaner way to view test results that puts the important stuff up front. It worked well enough that we open sourced it with company backing\, and eight years later it's had about 90 releases and is being used by testing teams around the world. It's been rewarding to see something that started as a weekend project actually help other people solve similar problems.\n\n\nThis talk covers the technical choices behind Cluecumber\, but focuses more on what I learned from maintaining an open source project. From handling feature requests and common questions to keeping code clean while adding new functionality\, plus the benefits of company-backed open source for everyone involved. I'll share why sometimes building your own solution makes sense\, what works well for creating tools people want to use\, and some insights from eight years of project maintenance.\n\n\nKey takeaways:\nUnderstand why clear and concise reporting of test results is beneficial for all parties of the software development lifecycleLearn about when and where our test reports help in further exploratory testing and bug trackingSee why it can be better to reinvent the wheel instead of going with using existing ones
CATEGORIES:TRACK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:d335a43436771bf842532c110f6340f9
URL:http://ntd2026.sched.com/event/d335a43436771bf842532c110f6340f9
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T073000Z
DTEND:20260605T093000Z
SUMMARY:Experience Test-Driven Development (TDD)
DESCRIPTION:People who practice test-driven development (TDD) often describe it as a powerful approach. And while they make a convincing case\, nothing beats experiencing it for yourself. So that's exactly what we'll do in this workshop.\n\n\nWe'll start with a brief explanation of TDD's red-green-refactor cycle. Red: write a test for the next bit of functionality you want to add. Green: write the code needed to make the test pass. Refactor: improve the code and the tests. Next\, it's time to put that cycle into practice implementing a fairly simple algorithm. There's very little setup needed\, so you can do this in any programming language you like.\n\n\nIn the last part of the workshop you'll share you experiences and your code. We'll reflect on those as a group\, drawing lessons from it. And we'll discuss how the red-green-refactor cycle applies\, even when you're writing something that's not unit testable\, like test automation.\n\n\nPlease complete the setup of this workshop beforehand\, by following the instructions in the "Setup for the kata"-section of the workshop repo: https://codeberg.org/joeposaurus/counterstring-codekata#setup-for-the-kata. The absolute minimum setup you need to do\, is make sure you're able to write code and tests in a programming languague of your choice.\n\n\nKey takeaways:\nTDD lets you take small steps with feedback at every step.&nbsp\;TDD lets you discover the right implementation as you go. &nbsp\; &nbsp\;The ideas of TDD still apply when you're writing test automation.
CATEGORIES:WORKSHOP 2H
LOCATION:D-Saal\, Kultuurikatel
SEQUENCE:0
UID:930ae4f4b9c83ba41c306aaf6eb9aeb7
URL:http://ntd2026.sched.com/event/930ae4f4b9c83ba41c306aaf6eb9aeb7
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T073000Z
DTEND:20260605T093000Z
SUMMARY:Lights\, Camera\, Test! Let'S Put The Fun In Non-Functional Testing!
DESCRIPTION:ISO 25010\, not the topic that ignites the fire in our test-hearts\, right?&nbsp\;Non-functional testing and quality characteristics are often seen as a hassle and don’t get the attention they deserve. So\, what can we do to make non-functional testing fun?&nbsp\;Let’s do something completely different!How about we make a short film script about a quality characteristic of our choice?&nbsp\;Let's go!&nbsp\;&nbsp\;Pre-screening:&nbsp\;We show you some examples of famous films and what they can teach us about quality characteristics. We also explain what these quality characteristics mean and why they are important. &nbsp\;&nbsp\;Take 1:&nbsp\;Welcome to Testlywood\, film crew! Let’s get acquainted. Create your production company and distribute the roles in your film-crew. We will explain you the various roles\, such as director\, art director\, movie critic and others.&nbsp\;&nbsp\;&nbsp\;Take 2:&nbsp\; Camera\, ready\, action! In this round you will use a mix of generative AI & human creativity to create your filmscript and upload it to Github. Present it to the group in a 1-minute pitch. The movie critics from the other teams will provide feedback at the end of this take.&nbsp\;&nbsp\;Take 3:&nbsp\;&nbsp\;Use the feedback movie critics feedback to finalize your filmscript. Your script is done\, splendid! &nbsp\;But the audiences still need to know your movie exists. Design a film poster that really captivates your core message. Submit both your filmscript and the poster as an entry for the ceremonies. Post-production:&nbsp\;&nbsp\;&nbsp\;We summarize what we learned about the quality characteristics and their role in test automation.\n\n\nKey takeaways:&nbsp\;\nLearn about the ISO25010 quality characteristics and their part in software testingUse AI as a partner to brainstorm and create something newCollaborate in a team with diverse roles\n
CATEGORIES:WORKSHOP 2H
LOCATION:Stalker\, Kultuurikatel
SEQUENCE:0
UID:79ce45317fe6407e8dca85a3a534df73
URL:http://ntd2026.sched.com/event/79ce45317fe6407e8dca85a3a534df73
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T073000Z
DTEND:20260605T123000Z
SUMMARY:The 70% Problem: Reclaiming Testing’s Intellectual Core With Agentic Quality Engineering
DESCRIPTION:The software testing profession has been around for approximately 70 years\, yet nothing has fundamentally transformed it to deliver on what it was always capable of. The majority of our industry has delivered "glorified clerical work" in the name of testing. Industry reports show that almost 70% of testing capacity is spent on testing-related activities\, while only 30% is devoted to actual testing that creates real value.Organizations have been trying to automate away all things testing for decades. It never worked because the real value of testing comes from the intellectual part i.e. asking the right questions\, critical evaluation\, risk analysis\, deep exploration\, and informed decision-making. But mastering this craft requires years of investment that organizations see as overhead. Hence\, the widespread acceptance of "testing as artefact-building" - easy to automate\, but without substantial value.What if you could deliver at scale and speed without compromising the value real testing creates?&nbsp\;Agentic Quality Engineering&nbsp\;gives every tester access to expert-level thinking without years of investment. AI agents built on 47 years of combined practitioner experience based on the award-winning QCSD (Quality Conscious Software Delivery) framework\, context-driven approaches\, risk-based thinking\, deep exploration techniques - all encoded into 41 specialized skills and 30 purpose-built agents. The agents are self-learning\, building institutional knowledge over time. They collaborate with other agents\, with humans\, and with existing systems. This isn't automation replacing testers\; it's accumulated wisdom amplifying what testers can do from day one.\n\n\nKey takeaways:\nExpert Thinking\, Accessible: Leverage decades of encoded testing expertise without years of personal skill developmentHands-On Agent Orchestration: Configure\, understand and run multi-agent pipelines that involve AI agents to support test activities across the entire SDLC. It includes 6 Core Agents\, 2 Performance Agents\, 3 Strategic Agents\, 4 Advanced and 3 Specialized agents. More yet\, 11 purpose-built agents for widespread coverage of important testing activities.The PACT Framework: Evaluate agentic quality systems using Proactive\, Autonomous\, Collaborative\, Targeted principlesSelf-Learning & Collaborative Systems: Understand with practical hands-on how these agents build institutional knowledge and collaborate with humans and systemsProduction-Ready Tools: Leave with a configured environment and open-source framework (MIT license) — nothing held backPersonal Adoption Roadmap: Design a concrete plan tailored to your context with clear first steps
CATEGORIES:WORKSHOP 4H
LOCATION:Terrassi\, Kultuurikatel
SEQUENCE:0
UID:d8f941261bdd1ef7ce63b1207895f70f
URL:http://ntd2026.sched.com/event/d8f941261bdd1ef7ce63b1207895f70f
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T073000Z
DTEND:20260605T123000Z
SUMMARY:Using OpenTelemetry Data (Traces\, Metrics And Logs) In Tests
DESCRIPTION:Observability and testing are treated as kind of separate practices in software engineering. Usually in organziation there are testing teams that focus on tests and site reliability teams that monitor applications in production.Testers find bugs before software is released and after the release\, when bug occurs\, we get that information from SRE teams.What if we could shift the process of monitoring system behaviour a little bit left and combine SRE practices with power of testing?\n\n\nKey takeaways:\nHow to implement traces\, metrics and logs in testing framework.How to set up OpenSource observability backend - Grafana LGTM stack.How to visualize test logs in LokiHow to visualize test metrics in PrometheusHow to visualize test traces in Tempo
CATEGORIES:WORKSHOP 4H
LOCATION:Puupakusaal\, Kultuurikatel
SEQUENCE:0
UID:672c0910fb9bca25c905b7ff59999c6d
URL:http://ntd2026.sched.com/event/672c0910fb9bca25c905b7ff59999c6d
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T081000Z
DTEND:20260605T085000Z
SUMMARY:Testing Agentic Ai Applications: Beyond Traditional QA
DESCRIPTION:Traditional software testing assumes deterministic behaviour: predictable inputs produce expected outputs. Agentic AI systems shatter this assumption. These autonomous agents make independent decisions\, learn from interactions\, and exhibit emergent behaviours that render traditional unit and integration testing insufficient.This talk examines critical testing challenges through three real-world case studies:Voice AI Agent: Deployed across 20+ corporate environments\, this system processes natural speech\, maintains conversational context\, and autonomously decides what additional information to provide. Traditional testing covered individual components but missed integration issues where the agent would correctly understand "Q3 sales figures" but autonomously add irrelevant market trend analysis.Phone Caller Agent:&nbsp\;Handling 5\,000+ patient interactions for healthcare appointment scheduling and reminders. Standard integration tests passed\, but the agent failed in production when encountering background noise\, elderly patients requiring slower conversations\, or unexpected human responses that weren't in test scenarios.Chat Agent: Processing 100+ daily customer service conversations with multi-session context retention. While individual NLP components performed well\, the integrated agent exhibited unexpected behaviours during complex\, multi-issue conversations that spanned several sessions.These case studies reveal five critical testing gaps:Non-deterministic behavior validation – the same&nbsp\;inputs can produce different valid outputsContextual decision testing – validating&nbsp\;autonomous choices about escalation\, information depth\, and communication styleMulti-modal integration complexity – components&nbsp\;work individually but fail in integrated agent workflowsContinuous learning validation – ensuring&nbsp\;agent improvements don't introduce biases or degrade existing capabilitiesReal-world variability simulation – testing&nbsp\;across acoustic environments\, human communication patterns\, and infrastructure variationsThe presentation introduces a practical testing framework specifically designed for agentic systems: Behavioural Goal Testing (testing achievement rather than outputs)\, Probabilistic Validation (acceptable outcome ranges vs. exact matches)\, Adversarial Scenario Generation (systematic edge case creation)\, and Contextual Journey Simulation (multi-session user interactions).\n\n\nKey takeaways:\nHow to test non-deterministic AI systems with confidenceParticipants will learn how to move beyond exact assertions and design test oracles based on intent\, semantics\, and properties\, enabling reliable validation of probabilistic LLM and agent outputs.Practical frameworks for validating LLMs and multi-agent architecturesAttendees will gain hands-on experience testing AI systems across layers\, including orchestration\, inference\, and inter-agent communication\, using structured frameworks and real-world scenarios.Actionable tools to operationalize AI quality in productionThe workshop equips participants with Python-based evaluators\, red teaming techniques\, and automated quality metrics that can be integrated into CI/CD pipelines and governance strategies immediately.\n
CATEGORIES:TRACK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:786410cedff3ea2af3e2b98c9d9145a7
URL:http://ntd2026.sched.com/event/786410cedff3ea2af3e2b98c9d9145a7
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T085000Z
DTEND:20260605T093000Z
SUMMARY:Running A Thousand End-To-End Cypress Tests Every Day
DESCRIPTION:In this talk\, I show how we run a lot of full end-to-end Cypress web application tests every day. In addition to running the full data set\, we do separate feature test runs based on test tags. We also allow everyone from all teams to trigger the tests right from GitHub Actions UI. This lets every group quickly test their feature before merging into the main branch. For pull requests\, we employ source code analysis based on data test IDs to run the affected tests first for quicker feedback. The software automation team uses the flake test information to chase the sources of the underlying errors to minimize noise and make every passing test run give us confidence in the released code\, and every failing test run useful to quickly diagnose the real underlying issue. The presentation covers test writing\, test organization\, selecting tests to run based on the source code changes\, running tests in different resolutions. I also look into making the tests faster by employing data creation and caching\, as well as using API calls to bypass the user interface in some places. Finally\, making the tests robust and flake-free and triaging the failed runs is an ongoing activity for the automation team.\n\n\nKey takeaways:\nHow to run 1000 of end-to-end tests quicklyWhich tests to run on a pull requestHow AI is helping us pick tests to run
CATEGORIES:TRACK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:86607f8efe5cc10757fcfbf2b4650fe9
URL:http://ntd2026.sched.com/event/86607f8efe5cc10757fcfbf2b4650fe9
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T093000Z
DTEND:20260605T103000Z
SUMMARY:Lunch
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Puupakusaal\, Kultuurikatel
SEQUENCE:0
UID:3f28cf7d6c548215c932d0b7a5130d56
URL:http://ntd2026.sched.com/event/3f28cf7d6c548215c932d0b7a5130d56
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T093000Z
DTEND:20260605T103000Z
SUMMARY:Lunch
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Stalker\, Kultuurikatel
SEQUENCE:0
UID:63ed02d3b8dc70f0be4b1b409f8b3cd5
URL:http://ntd2026.sched.com/event/63ed02d3b8dc70f0be4b1b409f8b3cd5
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T093000Z
DTEND:20260605T103000Z
SUMMARY:Lunch
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:D-Saal\, Kultuurikatel
SEQUENCE:0
UID:7c0fac3061051ecd1a87ddb224ccb175
URL:http://ntd2026.sched.com/event/7c0fac3061051ecd1a87ddb224ccb175
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T093000Z
DTEND:20260605T103000Z
SUMMARY:Lunch
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:96a3858d7630508a7460c1570a67c4ac
URL:http://ntd2026.sched.com/event/96a3858d7630508a7460c1570a67c4ac
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T093000Z
DTEND:20260605T103000Z
SUMMARY:Lunch
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Terrassi\, Kultuurikatel
SEQUENCE:0
UID:c3510535b80f1ab709fcc7df25dbe74e
URL:http://ntd2026.sched.com/event/c3510535b80f1ab709fcc7df25dbe74e
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T103000Z
DTEND:20260605T111000Z
SUMMARY:Vito (Visual Test Oracle): How Genai Slashed Our Test Maintenance By 50%
DESCRIPTION:Every automation engineer knows the "Maintenance Tax." We spend hours fixing fragile XPaths and CSS selectors just to verify if a button is visible or a chart is correct. In fact\, our internal code analysis shows that assertion logic is typically five times (5x) larger in code size than action logic\, consuming up to three months of dedicated maintenance effort every year.In this session\, I introduce ViTO (Visual Testing Oracle)\, a production-deployed framework that ends the era of DOM-dependent verification. By leveraging multimodal Generative AI (GenAI)\, ViTO "sees" the application exactly like a human does.I will share our industrial experience of decoupling verification from the underlying code\, resulting in a 50% reduction in our assertion codebase. You will see how we replaced thousands of lines of brittle verification logic with resilient\, prompt-driven visual oracles that can handle complex data visualisations and unseen UI faults with zero extra effort. If you are tired of your tests breaking because a div changed\, it's time to shift from structural selectors to a visual AI oracle.\n\n\nKey takeaways:\nPrompt Engineering for Testers: How to write resilient "Assertion Prompts" that replace complex conditional code and handle visual regression automatically.Real-World ROI: Evidence-based results from a production environment\, showing a 50% reduction in code maintenance and expanded coverage for rich UI components.Deterministic AI: Practical strategies to control GenAI hallucinations using "concentrated screenshots" and "dynamic HTML filtering."\n
CATEGORIES:TRACK
LOCATION:D-Saal\, Kultuurikatel
SEQUENCE:0
UID:26f96b2e3600867f0950af46b7d6998d
URL:http://ntd2026.sched.com/event/26f96b2e3600867f0950af46b7d6998d
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T103000Z
DTEND:20260605T111000Z
SUMMARY:When Life Gives You Lemons… Are You Counting Them Or Making Lemonade?
DESCRIPTION:Teams often rely on test cases executed\, bugs reported\, and pass rates to measure success. These numbers might look impressive\, but do they truly reflect software quality? Vanity metrics can mislead teams\, encourage the wrong behaviours\, and create a false sense of progress.&nbsp\;&nbsp\;&nbsp\;This talk introduces a 7-step framework to move beyond superficial KPIs and focus on metrics that drive real value. Inspired by analytical approaches in competitive sports\, this model helps teams make better decisions\, align testing efforts with business goals\, and ensure that data supports meaningful improvements.\n\n\nKey takeaways:\nThe risks of vanity metrics and how they can mislead decision-making.How to design KPIs that focus on value\, not just activity.A practical framework to ensure testing metrics drive meaningful change.\n
CATEGORIES:TRACK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:cc3e8e814cc46e1db19a2a30a766024f
URL:http://ntd2026.sched.com/event/cc3e8e814cc46e1db19a2a30a766024f
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T103000Z
DTEND:20260605T123000Z
SUMMARY:REST API Automation With Python 101
DESCRIPTION:API testing is a core part of modern testing and delivery pipelines\, yet it is often misunderstood or introduced too late. This session provides a practical introduction to REST API automation using Python\, focusing on what to test\, how to structure tests\, and how API tests fit into a modern testing infrastructure.The workshop starts with a short overview of API testing fundamentals and common use cases. As a practical part\, we'll have a hands-on walkthrough where we write REST API tests covering basic CRUD operations. Attendees will work with Python and the Requests library against a real service with well-documented APIs.I will provide a basic test framework\, and we will extend it together by adding and improving tests during the session. The workshop requires Python 3.13+ installed and basic familiarity with Python to read and write test code.
CATEGORIES:WORKSHOP 2H
LOCATION:Stalker\, Kultuurikatel
SEQUENCE:0
UID:adeb91bec501dee986c963529b80f3e1
URL:http://ntd2026.sched.com/event/adeb91bec501dee986c963529b80f3e1
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T111000Z
DTEND:20260605T115000Z
SUMMARY:Lessons Learned From Ai-Powered Visual Reasoning Feedback
DESCRIPTION:Visual testing is supposed to protect QA teams from the familiar “it looks wrong” bug\, yet traditional pixel-diff approaches only show that something changed\, not whether that change actually matters. As modern interfaces grow more dynamic and design systems become more complex\, teams need smarter ways to detect meaningful visual regressions.\n\n This talk presents a practical approach to automated visual bug detection using multimodal LLMs. Drawing on a real-world implementation\, it shows how AI models from providers such as OpenAI\, Anthropic\, and Google can be orchestrated to analyze screenshots and identify issues that pixel-based tools often cannot interpret on their own. These include layout breaks\, missing elements\, accessibility concerns\, color contrast problems\, and platform-specific guideline violations.\n\n The session explores how AI-driven visual analysis can move beyond pixel-perfect comparison toward semantic understanding\, helping teams distinguish intentional UI changes from genuine defects. It also addresses one of the biggest challenges in visual testing at scale: false positives\, demonstrating how agent-based review systems can reduce noise while still surfacing critical issues.\n\n Attendees will leave with practical ideas for using multimodal AI to strengthen visual testing workflows and make automated UI validation more accurate\, scalable\, and useful.\n\nKey Takeaways:How to evolve from “pixel diffs” to impact-based automated visual feedbackPatterns that turn image feedback into structured results (what changed\, where\, severity\, why it matters)Tips for integrating automated LLM-powered visual feedback into existing automated UI test frameworks
CATEGORIES:TRACK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:5bd1a1c773cc6d9a2cd43885f6b7299a
URL:http://ntd2026.sched.com/event/5bd1a1c773cc6d9a2cd43885f6b7299a
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T111000Z
DTEND:20260605T115000Z
SUMMARY:To Be Announced Soon
DESCRIPTION:This track will be presented by our Gold Partner. Will be announced soon.
CATEGORIES:TRACK
LOCATION:D-Saal\, Kultuurikatel
SEQUENCE:0
UID:316260ddef90b0649d940853cf947100
URL:http://ntd2026.sched.com/event/316260ddef90b0649d940853cf947100
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T115000Z
DTEND:20260605T123000Z
SUMMARY:From Chaos To Confidence: Building Rock-Solid Stability In Mobile E2E Testing
DESCRIPTION:99.59%.That’s not uptime\, not code coverage - it’s our yearly stability rate for mobile end-to-end test runs. It sounds almost impossible\, especially if you’ve ever managed a growing Slack thread titled #iHateMobile.For three years\, we fought the usual suspects of mobile automation: Appium timeouts\, vanishing selectors\, and flaky infrastructure. This talk condenses that journey into a survival guide for anyone who has ever wanted to throw their test phone across the room.In this fast-paced session\, we will bypass the basics and dive straight into the specific architecture decisions that turned chaos into trust. We will look at how we moved beyond standard WebdriverIO implementations to build a system that is fast\, predictable\, and relied upon by the entire engineering organization.We will cover the "Big Three" that solved our flakiness:The Framework: How small\, low-level fixes in element interaction and strict state management snowballed into massive stability gains.The Shortcuts: Why we killed UI-based setup in favor of API data seeding and custom app states to drastically reduce execution time.The Orchestration: Introducing our homemade "device-thread balancer" and CI triggers that made testing "one-click" easy.Finally\, we’ll touch on the human element: how stable builds transformed our culture\, turning skeptics into believers and making "just run the tests" the team's favorite phrase.\n\n\nKey takeaways:\nRoot Cause Analysis: Techniques for diagnosing the real source of mobile flakiness (it's not always the device).Speed vs. Stability: How to use API seeding and backend shortcuts to stabilize frontend tests.DevOps Integration: Blueprints for a "device-thread balancer" that optimizes cost and speed.Culture: How to build trust with developers so they treat E2E tests as an asset\, not a blocker.\n
CATEGORIES:TRACK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:93a1d89ae8cfc01ca98b2c131f24cf4d
URL:http://ntd2026.sched.com/event/93a1d89ae8cfc01ca98b2c131f24cf4d
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T115000Z
DTEND:20260605T123000Z
SUMMARY:Testing Cloud Applications Without Breaking The Bank: Testcontainers And Localstack
DESCRIPTION:How do you test an application that relies heavily on cloud services? Do you have a specific strategy for testing it\, or do you simply run your tests regardless of the infrastructure costs?Nowadays\, many applications rely on different cloud services\, such as databases\, message queues\, and file storage offered by cloud providers. Those cloud services bring considerable infrastructure costs and complexity in terms of testing cloud applications. The challenges include teams relying on mocks to test the application locally and in CI/CD\, as well as extra costs to create test environments that use real services. However\, a good alternative to deal with that is to use emulation tools to simulate those cloud services\, providing good confidence and saving a lot of costs.In this talk\, we’ll explore how Testcontainers and LocalStack offer an affordable and scalable solution to cloud application testing without compromising on quality. This session will demonstrate (including a live showcase) how to use Testcontainers in combination with LocalStack to spin up containerized services to emulate all the AWS cloud services that your application depends on\, enabling you to have your own cloud running locally on your machine or CI/CD. Together\, those two tools can provide an efficient\, cost-saving alternative to traditional cloud testing strategies.Here is the agenda that I plan for this talk:State of cloud applications nowadaysWhat are the challenges when testing cloud applications?Which options do we have to avoid some of those costs?Introduction to Localstack and TestcontainersLocalstack and TestContainers in actionConclusionBy the end of this session\, you will have actionable insights on how to optimize your testing process\, lower your infrastructure costs\, and ensure your cloud applications are ready for production without complex setups.\n\n\nKey takeaways:\nLearn how to create and run tests for cloud applications using free and open-source tools while reducing the costs of infrastructure and cloud services.Discover some common challenges when testing cloud applications and how to deal with them.Understand how to use real containerized cloud services instead of mocks to make your tests more closely mimic the production environment setup.\n
CATEGORIES:TRACK
LOCATION:D-Saal\, Kultuurikatel
SEQUENCE:0
UID:d701cf66dd69d9589993ead51892a390
URL:http://ntd2026.sched.com/event/d701cf66dd69d9589993ead51892a390
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T123000Z
DTEND:20260605T130000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:56a2ae07891cc7b797592632a791798f
URL:http://ntd2026.sched.com/event/56a2ae07891cc7b797592632a791798f
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T123000Z
DTEND:20260605T130000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:D-Saal\, Kultuurikatel
SEQUENCE:0
UID:5dc7a3f5f2fd6a7e900372e34b9b7881
URL:http://ntd2026.sched.com/event/5dc7a3f5f2fd6a7e900372e34b9b7881
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T123000Z
DTEND:20260605T130000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Stalker\, Kultuurikatel
SEQUENCE:0
UID:a86ee403d90949617f89931da6987e7e
URL:http://ntd2026.sched.com/event/a86ee403d90949617f89931da6987e7e
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T123000Z
DTEND:20260605T130000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Terrassi\, Kultuurikatel
SEQUENCE:0
UID:df5d3b3026788fe4ac2a6740a2fe989e
URL:http://ntd2026.sched.com/event/df5d3b3026788fe4ac2a6740a2fe989e
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T123000Z
DTEND:20260605T130000Z
SUMMARY:Coffee Break
DESCRIPTION:\n
CATEGORIES:BREAK
LOCATION:Puupakusaal\, Kultuurikatel
SEQUENCE:0
UID:feccf553b9b0b8373a48f5df087f592d
URL:http://ntd2026.sched.com/event/feccf553b9b0b8373a48f5df087f592d
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260518T030745Z
DTSTART:20260605T130000Z
DTEND:20260605T140000Z
SUMMARY:KEYNOTE: Testing =/= Fun?
DESCRIPTION:Testing is serious business. Fun is not. Or is it?\n\nWe use games to teach testing\, gamification to motivate work\, playful exercises to build skills\, and “fun” as a selling point for products. But fun is slippery. It is personal\, contextual\, fragile\, and surprisingly easy to ruin by trying to measure it.\n\nIn this keynote\, Kristjan will explore what fun means in testing. Can testing be fun? Should learning testing be fun? Does gamification actually help\, or does it simply decorate boring work with badges and points? And when a product is meant to be enjoyable\, how can testers investigate that without reducing the experience to a lifeless checklist?\nThrough painful personal examples\, testing games\, teaching experiences\, and a dangerous amount of theory\, Kristjan will break fun into smaller pieces: challenge\, surprise\, flow\, social interaction\, and quality-of-life features we often confuse with fun.\n\nYou will leave with an urge to analyze your own enjoyment - and may never look at your relaxing hobbies the same way again.\n\nKey Takeaways:\nHow to think about fun as something observable\, discussable\, and testable.Why gamification\, testing games\, and playful learning can help - but can also fail badly.Why fun should be treated as a serious quality attribute\, not a vague bonus.
CATEGORIES:KEYNOTE
LOCATION:BlackBox\, Kultuurikatel
SEQUENCE:0
UID:baf9f4412b14995a26b2ba656e72db49
URL:http://ntd2026.sched.com/event/baf9f4412b14995a26b2ba656e72db49
END:VEVENT
END:VCALENDAR