# E2E Testing Published articles for E2E Testing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Everything You Need to Know About Patrol in 2026 DevFeed: [Everything You Need to Know About Patrol in 2026]() Original publisher: [Read original article]() Author: LeanCode Published: 2026-07-24T02:52:52Z Content type: tutorial Language: en Sources: [Flutter Community - Medium]() Topics: [Flutter](), [Mobile Testing](), [ui-testing](), [multiplatform](), [ci](), [Android](), [iOS](), [Web](), [Open Source]() Tags: [ai](), [android](), [automation-testing](), [ci](), [e2e-testing](), [flutter](), [flutter-app-development](), [ios](), [mobile](), [mobile-testing](), [multiplatform](), [open-source](), [ui-testing](), [web]() ### AI overview This article explains Patrol, an open-source multiplatform end-to-end UI testing framework for Flutter apps. It describes how Patrol combines Flutter testing APIs with native Android and iOS UI automation to test Flutter widgets alongside system dialogs, biometric prompts, notifications, and other native interfaces, while integrating with CI pipelines and device farms. ### Source excerpt Author: Katarzyna Szulc from LeanCode Patrol has come a long way from being "just another Flutter testing tool." Today, it powers end-to-end testing across Android, iOS, and Web, integrates with native testing infrastructure, runs on cloud device farms, offers AI-powered testing capabilities, and continues to push the boundaries of what's possible in the Flutter ecosystem. No matter if you've been following Patrol for a while or you're simply looking for the best way to handle Flutter E2E testing, this article is the perfect place to catch up. What exactly is Patrol? Let's break it down Developed by LeanCode, Patrol is a powerful, open-source, multiplatform E2E UI testing framework for Flutter apps that overcomes the limitations of integration_test by handling native interactions. Let's dig deeper into that. Flutter's greatest strength also creates one of its biggest testing challenges. Unlike native apps, Flutter renders its entire UI using its own graphics engine instead of platform-native components. This enables a consistent, pixel-perfect experience across devices, but it also means that native UI automation tools often see a Flutter app as little more than a single canvas. They simply cannot interact with Flutter widgets. The official solution is the integration_test package, which gives tests direct access to the Flutter widget tree. As long as everything happens inside Flutter, it works well. But real apps rarely stay there. System permission dialogs, biometric prompts, notifications, WebViews, and other native UI all exist outside the Flutter runtime, making them inaccessible to integration_test. Patrol bridges this gap. It lets tests interact with both Flutter widgets and native UI elements in a single test. Because Patrol builds on native frameworks such as JUnit and XCTest, it also integrates seamlessly with existing CI pipelines, device farms, and the broader mobile testing ecosystem. If you are new to automating E2E testing in Flutter, you can start by ## Vercel Sandbox can now run for up to 24 hours DevFeed: [Vercel Sandbox can now run for up to 24 hours]() Original publisher: [Read original article]() Author: Rob Herley Published: 2026-06-16T00:01:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [data-processing](), [Persistence]() Tags: [agentic](), [data-processing](), [documentation](), [e2e-testing](), [enterprise](), [persistence](), [sandboxes](), [scale](), [vercel]() ### AI overview Vercel Sandboxes now support uninterrupted sessions of up to 24 hours, increased from 5 hours. The longer runtime supports large-scale data processing, end-to-end testing pipelines, and long-lived agentic workflows, with persistent sandboxes preserving state across extended runs. ### Source excerpt Vercel Sandboxes can run uninterrupted sessions for up to 24 hours (up from 5 hours). This new max duration unlocks workloads that require longer runtimes, such as large-scale data processing, E2E testing pipelines, and long-lived agentic workflows. Pair with persistent sandboxes to maintain durable state across extended runs. The 24 hour max duration is available on all Pro and Enterprise plans. Learn more about limits in the documentation and see how Vercel Sandbox duration and persistence work. Read more ## Agentic Testing: Where Agents Fit in the E2E Testing Stack DevFeed: [Agentic Testing: Where Agents Fit in the E2E Testing Stack]() Original publisher: [Read original article]() Author: Sergii Gorbachov Published: 2026-06-11T14:15:28Z Content type: article Language: en Sources: [Engineering at Slack]() Topics: [Playwright](), [Model Context Protocol](), [large-language-models](), [User Interfaces]() Tags: [agentic](), [agents](), [automation-testing](), [browser](), [code](), [cost](), [developer-productivity](), [e2e-testing](), [innovation](), [language-models](), [large-language-models](), [mcp](), [speed](), [testing](), [uncategorized](), [workflow]() ### AI overview The article examines agent-driven end-to-end testing as an exploratory complement to deterministic tests. Based on more than 200 runs using Playwright MCP, Playwright CLI, and agent-generated Playwright tests, it compares how agents pursue goals through variable UI paths and considers reliability, execution time, and cost. ### Source excerpt Abstract Agent-driven end-to-end (E2E) tests add a new exploratory layer to testing, but should they replace traditional deterministic tests? We ran more than 200 agentic E2E workflows using the Playwright MCP, Playwright CLI, and agent-generated Playwright tests in test workspaces using non-production data to find out how agentic testing could fit into both our and... ## SwiNOG 41: It Was Nice to Be Back DevFeed: [SwiNOG 41: It Was Nice to Be Back]() Original publisher: [Read original article]() Published: 2026-05-04T05:09:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [evpn](), [Artificial Intelligence](), [Automation](), [Testing]() Tags: [ai](), [conferences](), [e2e-testing](), [evpn](), [llms](), [network-automation](), [networking](), [pytest]() ### AI overview A personal recap of SwiNOG 41 in Switzerland, highlighting discussions and presentations on networking topics including transceiver power, shared spectrum, AI and LLMs in networking, EVPN gateways, network automation, and end-to-end testing with Netlab and pytest. ### Source excerpt Last week's SwiNOG was (as expected) great fun at a phenomenal location, starting with the first slide of the first presentation: "6 Stages of Network De-sh*tification". I particularly loved the "talk less, chat more" schedule. The longer breaks gave us plenty of time to catch up with old friends and discuss interesting, sometimes completely unexpected, topics. For example, I learned that SIP MESSAGE is used to carry SMS messages these days. As much as I loved chatting with fellow networking engineers, I also found these presentations highly interesting: Read more ... ## A better way to end-to-end test your webapp DevFeed: [A better way to end-to-end test your webapp]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-01-06T00:00:00Z Content type: opinion Language: en Sources: [Swizec Teller]() Topics: [Testing](), [Web app](), [computer-use](), [Playwright](), [OpenAI](), [TypeScript]() Tags: [agentic](), [computer-use](), [e2e](), [e2e-testing](), [flaky](), [mocking](), [open-source](), [openai](), [playwright](), [tests]() ### AI overview The article proposes an agentic approach to end-to-end testing for web applications. Tests describe user goals, while an agent uses screenshots and browser interactions to achieve and record those goals. Later runs replay the stored actions to check for regressions, reducing test-writing overhead and sensitivity to UI implementation changes. ### Source excerpt End-to-end tests are the best way to test your webapp, but they're flaky and annoying to write. I'm trying a new agentic approach that fixes the issue. ## Automating Apple Maps End-to-End Tests with Maestro DevFeed: [Automating Apple Maps End-to-End Tests with Maestro]() Original publisher: [Read original article]() Author: Leland Takamine Published: 2025-09-04T00:00:00Z Content type: tutorial Language: en Sources: [mobile.dev - Medium]() Topics: [Testing](), [YAML](), [selectors]() Tags: [accessibility](), [apple](), [e2e-testing](), [maestro](), [yaml]() ### AI overview A step-by-step tutorial showing how to automate an Apple Maps flow with Maestro. The example uses a YAML test to search for Apple HQ, explore Look Around, navigate dynamically, and verify UI details with selectors and assertions. ### Source excerpt Automate Apple Maps with Maestro. A step-by-step E2E test in simple YAML - readable, reliable, and flake-free. ## Endform Wants to Scale your Playwright End-to-end Tests DevFeed: [Endform Wants to Scale your Playwright End-to-end Tests]() Original publisher: [Read original article]() Author: Carlota Soto Published: 2025-05-15T23:46:42Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [ci]() Tags: [auth](), [case-studies](), [ci](), [databases](), [e2e-testing](), [infrastructure](), [postgres](), [scale](), [serverless]() ### AI overview Endform describes using Neon's serverless Postgres to provide fast, isolated database environments for repeated Playwright end-to-end testing in CI. ### Source excerpt "Every tech choice we make is about staying lightweight and scalable. Neon fits that perfectly: we can spin up real Postgres databases in CI, in seconds, with zero hassle." (Oliver Stenbom, co-founder of Endform) Before starting Endform, Oliver spent years working at Mentimeter,... ## How Dropbox leverages testing to maintain high level of trust at scale DevFeed: [How Dropbox leverages testing to maintain high level of trust at scale]() Original publisher: [Read original article]() Author: Jose Alcérreca Published: 2025-04-23T17:26:09Z Content type: article Language: en Sources: [Android Developers - Medium]() Topics: [dropbox](), [Testing](), [Android](), [test](), [engineering-culture]() Tags: [android](), [automated](), [case-study](), [dropbox](), [e2e-testing](), [engineering](), [engineering-culture](), [featured](), [quality](), [testing]() ### AI overview This article describes how Dropbox evolved its Android testing strategies to maintain user trust and timely feedback at scale. It discusses the testing pyramid, automated and end-to-end testing, Android integration, and the costs of an early monolithic app structure. ### Source excerpt This is part 2 of the Testing at scale series of articles where we asked industry experts to share their testing strategies. In this article, Ryan Harter, Staff Engineer at Dropbox, shares how the shape of Dropbox's testing pyramid changed over time, and what tools they use to get timely feedback. With more than one billion downloads, the Dropbox app for Android has to maintain a high quality bar for a diverse set of use cases and users. With less than 30 Android engineers, manual testing and #yolo isn't enough to maintain confidence in our codebase, so we employ a variety of different testing strategies to ensure we can continually serve our users needs. Since Dropbox makes it easy to access your files across all of your devices, the Android app has to support viewing as many of those files as possible, including media files, documents, photos, and all of the variations within these categories. Additionally, features like Camera Uploads, which automatically backs up all of your most important photos, require deep integration with the Android OS in ways that have changed significantly over the years and across Android versions. All of this needs to continually work for our users, without them having to worry about the complexity, because the last thing anyone wants is to worry that they might lose their data. While the size and distribution of the Android team at Dropbox has changed throughout the years, it's imperative that we're able to consistently build and refine features within the app while maintaining the level of trust from our users that we've become known for. To help underscore how Dropbox has been able to foster that trust, I'd like to share some ways that our testing strategies have changed over the years. How it started While automated testing has always been an important part of engineering culture at Dropbox, it hasn't always been easy on Android. Years ago Dropbox invested in testing infrastructure that leaned heavily on End-to-End (E2E) testing. B ## Case Study: How Doccla Transformed Mobile App Testing with Maestro DevFeed: [Case Study: How Doccla Transformed Mobile App Testing with Maestro]() Original publisher: [Read original article]() Author: Jake Krupski Published: 2025-03-12T00:00:00Z Content type: article Language: en Sources: [mobile.dev - Medium]() Topics: [Testing](), [Mobile](), [Test automation](), [Automation](), [Open Source]() Tags: [automation](), [bluetooth](), [case-study](), [compliance](), [e2e-testing](), [healthcare](), [maestro](), [mobile](), [open-source](), [testing]() ### AI overview This case study describes how Doccla addressed the burden of manually testing a mobile app used for remote patient monitoring in a regulated healthcare setting. The team adopted Maestro, an open-source end-to-end testing framework for mobile and web apps, to automate much of the workflow. ### Source excerpt Testing mobile applications, especially in highly regulated industries like healthcare, can be a daunting, time-consuming, and repetitive task. But what if there was a way to a... ## Spotlight on SIG Testing DevFeed: [Spotlight on SIG Testing]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2023-11-24T00:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Testing](), [Kubernetes](), [Tooling](), [Logging](), [Open Source]() Tags: [developers](), [e2e-testing](), [go](), [intel](), [kubernetes](), [logging](), [open-source](), [testing](), [tooling](), [unit-testing]() ### AI overview An interview-style Kubernetes SIG spotlight introduces SIG Testing and its contributors, describing the group's work on testing tools, infrastructure, test-result analysis, E2E testing practices, and unit-testing approaches. ### Source excerpt Welcome to another edition of the SIG spotlight blog series, where we highlight the incredible work being done by various Special Interest Groups (SIGs) within the Kubernetes project. In this edition, we turn our attention to SIG Testing , a group interested in effective testing of Kubernetes and automating away project toil. SIG Testing focus on creating and running tools and infrastructure that make it easier for the community to write and run tests, and to contribute, analyze and act upon test results. To gain some insights into SIG Testing, Sandipan Panda spoke with Michelle Shepardson , a senior software engineer at Google and a chair of SIG Testing, and Patrick Ohly , a software engineer and architect at Intel and a SIG Testing Tech Lead. Meet the contributors Sandipan: Could you tell us a bit about yourself, your role, and how you got involved in the Kubernetes project and SIG Testing? Michelle: Hi! I'm Michelle, a senior software engineer at Google. I first got involved in Kubernetes through working on tooling for SIG Testing, like the external instance of TestGrid. I'm part of oncall for TestGrid and Prow, and am now a chair for the SIG. Patrick: Hello! I work as a software engineer and architect in a team at Intel which focuses on open source Cloud Native projects. When I ramped up on Kubernetes to develop a storage driver, my very first question was "how do I test it in a cluster and how do I log information?" That interest led to various enhancement proposals until I had (re)written enough code that also took over official roles as SIG Testing Tech Lead (for the E2E framework ) and structured logging WG lead. Testing practices and tools Sandipan: Testing is a field in which multiple approaches and tools exist; how did you arrive at the existing practices? Patrick: I can't speak about the early days because I wasn't around yet 😆, but looking back at some of the commit history it's pretty obvious that developers just took what was available and started usi ## Introducing native E2E testing: Learnings from the Senior Engineering Program for Women DevFeed: [Introducing native E2E testing: Learnings from the Senior Engineering Program for Women]() Original publisher: [Read original article]() Author: Joana Melo Published: 2023-09-08T12:35:44Z Content type: article Language: en Sources: [Klarna Engineering]() Topics: [Testing](), [App](), [Development]() Tags: [appium](), [automated](), [diversity](), [e2e-testing](), [engineering](), [gender](), [gender-equality](), [klarna](), [learnings](), [professional-development](), [regression](), [testing](), [typescript]() ### AI overview The author describes introducing native end-to-end testing in mini versions of the Klarna app to enable automated feature regression tests in development pipelines. The article also reflects on the Senior Engineering Program for Women, including its focus on professional growth, coaching, collaboration, technology, influence, and diversity. ### Source excerpt I made company-wide impact by successfully delivering the introduction of native end-to-end (E2E) testing in mini versions of the Klarna app. The goal was to have automated feature regression tests in our pipelines. I developed this as part of a program for senior engineering women, and today, I want to share the insights and learnings I gained from this experience. Creating fair and equal opportunities for women How do we offer women equal and fair opportunities in an industry dominated by men? Well, there are many ways to work on this topic. One that piqued my curiosity was Klarna's Senior Engineering Program for Women (SEPW). As you might wonder as well, my initial thoughts on it as with any other initiatives like this came with a lot of reservations: Is this fair? Is this the best way for me to ensure that I'm being fairly evaluated? Will it look like I am being brought to a speedlane towards an easy promotion if I happen to get one because I'm a woman? Are we going to get treated like tokens? Is this all just a marketing strategy to promote? Am I being part of and legitimizing something that has no real content and value for my career or other women? What will everyone think? When we are faced to join initiatives related to gender gap improvements, we might fall into the trap of having all the perfect and right answers before we take risks, or we can accept that there will never be the perfectly carved, impactful and life-changing solution at our doorstep. We can only experiment and learn from the results to make better decisions as we help evolving into a hopefully more gender-fair world. As a woman in engineering, I understand the issues, but I don't claim to have all the answers. And that's ok. The program The SEPW is a way for Klarna to acknowledge and accelerate the professional development of promising engineers and promote diversity within engineering. The 6 month program is designed with the individual's growth as the main focus, and based on four theme ## Reliable state in Cypress tests using Turso's libSQL driver DevFeed: [Reliable state in Cypress tests using Turso's libSQL driver]() Original publisher: [Read original article]() Author: James Sinkala Published: 2023-07-06T00:00:00Z Content type: article Language: en Sources: [Turso Blog]() Topics: [Cypress](), [Turso](), [libSQL](), [SDKs](), [Databases]() Tags: [cloud](), [cypress](), [databases](), [e2e-testing](), [integration](), [libsql](), [offline](), [replication](), [sdks](), [turso]() ### AI overview A developer article explains how Turso and its libSQL SDK can provide reliable state for end-to-end tests with Cypress. It describes Turso Cloud database access and synchronization across devices and servers, with offline support, while noting that the post covers an older version of Turso and that legacy libSQL SDKs have since been replaced. ### Source excerpt While performing e2e tests can be a pain, here's how Turso and it's libSQL SDK can still offer reliable state when performing e2e tests with Cypress. ## Efficient React Native UI Testing with Maestro and Ignite DevFeed: [Efficient React Native UI Testing with Maestro and Ignite]() Original publisher: [Read original article]() Author: Ashish Kharche Published: 2023-05-01T07:00:00Z Content type: tutorial Language: en Sources: [mobile.dev - Medium]() Topics: [Testing](), [React Native](), [ui](), [Mobile]() Tags: [app](), [e2e-testing](), [maestro](), [mobile](), [react-native](), [testing](), [ui-testing]() ### AI overview This tutorial explains how Maestro, an open-source mobile UI testing framework, integrates with Ignite for React Native apps. It covers Ignite's replacement of Detox with Maestro as its default end-to-end testing tool and outlines setup steps for new and existing Ignite projects. ### Source excerpt UI testing an Ignite App ## E2E Testing Best Practices, Reloaded DevFeed: [E2E Testing Best Practices, Reloaded]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2023-04-12T00:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Testing](), [Kubernetes](), [Code]() Tags: [architecture](), [best-practices](), [debugging](), [dependencies](), [e2e-testing](), [kubernetes](), [migration](), [technical](), [testing]() ### AI overview This Kubernetes blog post summarizes cleanup and refactoring of the project's end-to-end testing framework after its migration to Ginkgo v2 in Kubernetes 1.25. It describes goals for reducing internal-code dependencies, organizing sub-packages, and improving test failure messages. ### Source excerpt End-to-end (E2E) testing in Kubernetes is how the project validates functionality with real clusters. Contributors sooner or later encounter it when asked to write E2E tests for new features or to help with debugging test failures. Cluster admins or vendors might run the conformance tests, a subset of all tests in the E2E test suite . The underlying E2E framework for writing these E2E tests has been around for a long time. Functionality was added to it as needed, leading to code that became hard to maintain and use. The testing commons WG started cleaning it up, but dissolved before completely achieving their goals. After the migration to Gingko v2 in Kubernetes 1.25, I picked up several of the loose ends and started untangling them. This blog post is a summary of those changes. Some of this content is also found in the Kubernetes contributor document about writing good E2E tests and gets reproduced here to raise awareness that the document has been updated. Overall architecture At the moment, the framework is used in-tree for testing against a cluster (test/e2e), testing kubeadm (test/e2e_kubeadm) and kubelet (test/e2e_node). The goal is to make the core test/e2e/framework a package that has no dependencies on internal code and that can be used in different E2E suites without polluting them with features or options that make no sense for them. This is currently only a technical goal. There are no plans anymore to actually move the code into a staging repository. The framework acts like a normal client of an apiserver and thus doesn't need much more than client-go. Since the sub-package refacoring , additional sub-packages like test/e2e/framework/pod depend on the framework, not the other way around. Those other sub-packages therefore can still use internal code. The import boss configuration enforces these constraints . What's left to clean up is that the framework contains a TestContext with fields that are used only by some tests or some test suites. The configur ## Branching Postgres databases with the Neon API DevFeed: [Branching Postgres databases with the Neon API]() Original publisher: [Read original article]() Author: Raouf Chebri Published: 2022-12-07T17:43:14Z Content type: tutorial Language: en Sources: [Blog -- Neon Docs]() Topics: [CI/CD](), [ci]() Tags: [api](), [automation](), [ci](), [ci-cd](), [code](), [community](), [databases](), [e2e-testing](), [github](), [github-actions](), [postgres](), [production](), [testing](), [workflow]() ### AI overview The article explains how to use Neon database branches and the Neon API in a CI/CD pipeline to test code and schema changes before production deployment. It describes GitHub Actions that create and delete database branches for end-to-end testing. ### Source excerpt In this post, we'll discuss using database branching and the Neon API from a CI/CD pipeline. By the end of this post, you'll have a better understanding of how database branching can help you test your code and schema changes before deploying to production. What is a branch? A br... ## Share Cypress Commands in an Nx Workspace DevFeed: [Share Cypress Commands in an Nx Workspace]() Original publisher: [Read original article]() Published: 2022-04-13T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Cypress](), [Testing](), [Development](), [React](), [Angular]() Tags: [angular](), [cypress](), [development](), [e2e-testing](), [eslint](), [jest](), [make](), [monorepo](), [nx](), [react](), [testing](), [typescript]() ### AI overview A tutorial on using Cypress in an Nx workspace, with a focus on sharing custom Cypress commands in an Nx monorepo. It also covers Nx-generated testing and development tooling and the initial setup of React- or Angular-based workspaces. ### Source excerpt Lorem ipsum dolor sit amet ## Challenging the Testing Pyramid DevFeed: [Challenging the Testing Pyramid]() Original publisher: [Read original article]() Published: 2019-07-16T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Testing](), [Cypress](), [Selenium](), [Tooling](), [Web Development]() Tags: [automated](), [cypress](), [e2e-testing](), [javascript](), [selenium](), [testing](), [web-development]() ### AI overview An introduction to automated UI and end-to-end testing with Cypress. The article discusses testing costs and benefits, contrasts manual and automated testing, and places UI testing in the context of the testing pyramid and testing trophy. ### Source excerpt Lorem ipsum dolor sit amet