Nordic Testing Days 2026

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.


Key takeaways:

1. Root 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.
2. DevOps Integration: Blueprints for a "device-thread balancer" that optimizes cost and speed.
3. Culture: How to build trust with developers so they treat E2E tests as an asset, not a blocker.

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.


Key takeaways:

1. Learn how to create and run tests for cloud applications using free and open-source tools while reducing the costs of infrastructure and cloud services.
2. Discover some common challenges when testing cloud applications and how to deal with them.
3. Understand how to use real containerized cloud services instead of mocks to make your tests more closely mimic the production environment setup.