# 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. ## Building a Playwright Training Environment Around Real CI Failures DevFeed: [Building a Playwright Training Environment Around Real CI Failures]() Original publisher: [Read original article]() Author: Roman Kudriavtsev Published: 2026-09-27T18:12:52Z Content type: tutorial Language: en Sources: [HackerNoon]() Topics: [Playwright](), [Test-driven development](), [CI/CD]() Tags: [browser](), [ci](), [cicd](), [e2e-testing](), [end-to-end-testing](), [flaky](), [flaky-tests](), [github-actions](), [javascript](), [playwright](), [playwright-chat-lab](), [test-automation](), [testing](), [typescript-testing]() ### AI overview The article describes playwright-chat-lab, a free Playwright training environment built around a chat application and a course of 11 lessons. It emphasizes realistic CI failures, debugging flaky end-to-end tests, and learning through review and feedback. ### Source excerpt A free Playwright lab teaches reliable E2E testing through deliberately tricky exercises, CI failures, GitHub pull requests, and real code review. ## 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: article Language: en Sources: [Flutter Community]() Topics: [Flutter](), [Test automation](), [Integration testing](), [Continuous integration](), [mobile devops](), [CI/CD](), [UiAutomator](), [AI Integration Strategies](), [Visual Studio Code](), [Learning]() Tags: [ai](), [ai-powered](), [android](), [app](), [automation](), [automation-testing](), [ci](), [cloud](), [e2e](), [e2e-testing](), [flutter](), [flutter-app-development](), [framework](), [infrastructure](), [ios](), [junit](), [multiplatform](), [native](), [notifications](), [open-source](), [package](), [permission](), [ui-testing]() ### AI overview Patrol combines Flutter widget testing with native UI automation so a single end-to-end test can cover Flutter screens and elements outside the Flutter runtime, such as permission prompts, notifications, and other native UI. Its Dart tests run with Flutter testing APIs alongside native runners--XCUITest on iOS and UIAutomator on Android--which communicate over localhost. The excerpt describes Patrol 4.0 support for Android, iOS, and Web, plus a VS Code extension for running and debugging tests and Patrol MCP tools for AI-assisted test execution and inspection. Native test infrastructure enables compatibility with device farms and JUnit reporting; test bundling, sharding, parallel execution, artifact collection, and duration reporting support larger runs. The excerpt also presents Patrol Finders as a more concise alternative to Flutter's built-in finders, with waits for dynamic UI. It does not provide a full feature-by-feature account of Web support or the listed integrations. ### 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 Model](), [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]() Topics: [Network](), [evpn](), [Artificial Intelligence](), [Automation](), [Software 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: [Software 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: Dead Simple E2E Testing with Maestro DevFeed: [Automating Apple Maps: Dead Simple E2E Testing with Maestro]() Original publisher: [Read original article]() Author: Leland Takamine Published: 2025-09-04T00:00:00Z Content type: tutorial Language: en Sources: [Mobile]() Topics: [Software Testing](), [ui-testing](), [Test automation](), [iOS]() Tags: [accessibility](), [appium](), [apple](), [automate](), [boilerplate](), [cli](), [code](), [commands](), [details](), [e2e](), [e2e-testing](), [espresso](), [flow](), [frameworks](), [loops](), [maestro](), [maintenance](), [maps](), [testing](), [yaml]() ### AI overview The excerpt presents Maestro as a way to write Apple Maps end-to-end tests in a single YAML flow, with the CLI handling setup. Its example searches for "Apple HQ," explores Look Around, repeatedly taps a navigation cone until an address appears, then checks that "Closed" is to the right of "Sunday." It says an accessibility identifier can target the cone and a relative selector can disambiguate repeated text. The author contrasts this concise approach with the boilerplate and maintenance burden they associate with Appium, Detox, XCUITest, and Espresso. The excerpt does not include the actual flow code, and its claims about reliability are the author's characterization. ### 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: [Neon Docs]() Topics: [Continuous integration]() 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]() Topics: [Test automation](), [Software Testing](), [Integration testing](), [CI/CD](), [dropbox]() Tags: [android](), [app](), [automated](), [automated-testing](), [case-study](), [confidence](), [culture](), [dropbox](), [e2e](), [e2e-testing](), [engineering](), [engineering-culture](), [featured](), [feedback](), [infrastructure](), [integration](), [os](), [quality](), [scale](), [strategies](), [testing](), [trust]() ### AI overview Dropbox describes moving from a slow, monolithic Android end-to-end test suite toward a balanced testing strategy. JUnit and Robolectric JVM tests provide fast feedback and are the only tests counted toward coverage, with an 80% target and overrides when unit testing is infeasible or unhelpful; JaCoCo's Kotlin limitations sometimes require overrides. Renewed E2E investment focuses on reliable infrastructure, removing flaky tests, and defining meaningful cases with product and design partners. Paparazzi supports fast, isolated view and composable screenshot tests, while Dropshots runs screenshots on devices or emulators to check system integrations. Manual testing remains part of release checks for workflows that are difficult to automate or judge programmatically. Dropbox is extending Dropshots to multiple device configurations and experimenting with Compose Preview Screenshot Testing. ### 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 ## Introducing: Maestro Webhooks DevFeed: [Introducing: Maestro Webhooks]() Original publisher: [Read original article]() Author: Felipe Duarte Published: 2025-03-29T00:00:00Z Content type: release Language: en Sources: [Mobile]() Topics: [Web APIs](), [CI/CD]() Tags: [bot](), [ci-cd](), [cloud](), [dashboards](), [e2e-testing](), [environment-variables](), [http](), [maestro](), [mobile](), [monitoring-tools](), [notifications](), [payload](), [pipelines](), [plan](), [post](), [real-time](), [reporting](), [server](), [slack](), [webhooks]() ### AI overview Maestro Webhooks are available to all Maestro Cloud Plan accounts and send an HTTP POST to a configured server whenever an upload completes. Payloads include upload and test-flow context such as environment variables, timing, individual flow results, and failure reasons. Setup requires entering a publicly accessible URL that accepts POST requests in Project Settings; a Webhook Token is sent in a header to help verify requests. Projects can have multiple webhooks, which can be disabled at any time. The text describes integrations with internal dashboards, issue trackers, notifications, CI/CD pipelines, and other systems. ### Source excerpt We're excited to introduce Maestro Webhooks - now available for all Cloud Plan accounts! ## How Gumroad Migrated 100M Emails to Resend DevFeed: [How Gumroad Migrated 100M Emails to Resend]() Original publisher: [Read original article]() Author: Jonni Lundy Published: 2025-03-14T00:00:00Z Content type: article Language: en Sources: [Resend]() Topics: [developer-productivity](), [rate-limiting](), [incident](), [CI/CD](), [API Governance]() Tags: [alerts](), [api](), [batch](), [customer-experience](), [deliverability](), [developer](), [developer-experience](), [e2e-testing](), [guides](), [infrastructure]() ### AI overview After its previous email provider blocked its account during a busy holiday season, Gumroad moved its email sending to Resend. The migration involved domain segmentation, paced sending, batch processing, bounce and complaint monitoring, and importing suppression lists. Resend also supported migration planning and email end-to-end testing. ### Source excerpt From critical service disruption to successfully migrating over 100 million emails in record time. ## 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: news Language: en Sources: [Mobile]() Topics: [Software Testing](), [Mobile Testing](), [ui-testing](), [Mobile]() Tags: [applications](), [automation](), [bluetooth](), [case-study](), [compliance](), [e2e-testing](), [healthcare](), [maestro](), [medical-devices](), [mobile](), [mobile-app](), [mobile-app-testing](), [regulated-industries](), [testing]() ### AI overview Doccla's regulatory requirements meant retesting every app requirement and keeping records with each release. Before automation, staff manually ran 120-130 tests, taking half a day or more and leaving less time for feature work. The excerpt says Doccla sought an open-source framework that developers could learn easily, could control device-level features such as Chrome and Google Play, and tested from a real user's perspective. It identifies Maestro as meeting those criteria, but provides no implementation details or quantified results. ### 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... ## Keeping User Journey SLOs Up-to-Date with E2E Testing in a Microservices Architecture DevFeed: [Keeping User Journey SLOs Up-to-Date with E2E Testing in a Microservices Architecture]() Original publisher: [Read original article]() Author: Yakenji Published: 2024-12-06T11:00:19Z Content type: article Language: en Sources: [Mercari Engineering]() Topics: [site-reliability-engineering](), [Microservices](), [reliability-engineering](), [Availability](), [Latency](), [incident](), [dashboards](), [Back end]() Tags: [availability](), [backend](), [dashboards](), [e2e-testing](), [incident](), [latency](), [microservices-architecture](), [monitoring](), [reduction](), [reliability](), [site-reliability-engineering](), [tests](), [triage]() ### AI overview Mercari's Site Reliability Engineering team describes how it revised user-journey SLOs in a microservices architecture and used end-to-end tests to automate their maintenance. The approach connects critical user journeys with service-level indicators, dashboards, and incident response, reducing SLO maintenance time and enabling impact assessment within seconds of detection. ### Source excerpt This post is for Day 3 of Mercari Advent Calendar 2024, brought to you by @yakenji from the Mercari Site Reliability Engineering (SRE) team. At Mercari, our SRE team is dedicated to maintaining and enhancing the reliability of our core product, the Mercari marketplace app, by measuring its availability and latency. We establish Service Level [...] ## 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: [Software Testing](), [Kubernetes](), [Developer Tools](), [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: [Test automation](), [Software Testing](), [CI/CD](), [software-development](), [Software Engineering]() Tags: [app](), [appium](), [automated](), [development](), [diversity](), [e2e](), [e2e-testing](), [engineering](), [feature](), [gap](), [gender](), [gender-equality](), [growth](), [impact](), [improvements](), [insights](), [klarna](), [learnings](), [native](), [program](), [testing](), [typescript](), [women]() ### AI overview The author introduced native end-to-end tests in mini Klarna app feature projects to reduce repeated manual release-candidate testing across iOS and Android. Using Appium and Mocha with TypeScript, she isolated test files from conflicting global Jest and JQuery types through tsconfig exclusions and local configuration, established Appium naming conventions, and used Diglett ignore entries when integrating dependencies into the monorepo made version alignment impractical. Co-locating tests with features clarified ownership and was later used as a reference for central Cypress test migration. The article also describes the six-month Senior Engineering Program for Women, including coaching, project feedback, and peer connections; the author says the work improved pipeline efficiency and developer confidence, and prompted other teams to explore native E2E testing. ### 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]() Topics: [Cypress](), [Turso](), [libSQL](), [SDK](), [Database]() 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]() Topics: [ui-testing](), [Software Testing](), [React Native](), [Test automation](), [Mobile Testing](), [User Interfaces]() Tags: [automate](), [boilerplate](), [e2e](), [e2e-testing](), [end-to-end-testing](), [framework](), [integrate](), [integration](), [maestro](), [mobile](), [mobile-apps](), [open-source](), [react-native](), [testing](), [ui](), [ui-testing]() ### AI overview Ignite v8.7.0 adopts Maestro as its default end-to-end testing tool, replacing Detox, and includes Maestro tests. Maestro lets developers define user-journey tests as Flows. For a new Ignite app, the excerpt describes installing Ignite and Maestro, launching the app in a simulator, then running the included flows from the project's Maestro directory. For existing projects, it says to install Maestro, create a flows folder at the project root, and add flows. The excerpt omits several commands and directory names, so it does not provide a complete runnable setup guide. ### 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: [Software 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 ## React, Vite and TypeScript: Get started in under 2 minutes DevFeed: [React, Vite and TypeScript: Get started in under 2 minutes]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2023-01-12T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [React](), [Developer Tools](), [Vite](), [TypeScript](), [Software Testing]() Tags: [best-practices](), [code-generation](), [e2e-testing](), [formatting](), [jest](), [linting](), [nx](), [react](), [testing](), [typescript](), [vite]() ### AI overview Nx 15.3 can scaffold a standalone React, Vite, and TypeScript app, including tooling for testing, formatting, and linting. The excerpt says Nx supports Vite with Vitest, or Webpack with Jest, and offers generators, caching, modularization, and automated upgrades. Running an app invokes an Nx target: a plugin-provided function that wraps a task and accepts options. The excerpt is truncated and omits the setup commands and details of configuring targets. ### Source excerpt Learn how to quickly set up a modern React application with Vite and TypeScript using Nx, featuring built-in testing, linting, and development tools. ## 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: [Neon Docs]() Topics: [CI/CD](), [Continuous integration]() 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](), [Software Testing](), [software-development](), [developer setup]() Tags: [angular](), [best-practices](), [cli](), [commands](), [custom](), [cypress](), [development-environment](), [e2e](), [e2e-testing](), [eslint](), [github](), [jest](), [linting](), [monorepo](), [nx](), [nx-cloud](), [react](), [runner](), [server](), [share]() ### AI overview Nx generates a Cypress setup for each application by default, alongside configured TypeScript, Jest, ESLint and Prettier. In an Nx workspace, Cypress end-to-end tests can be run headlessly or interactively with the test runner, which reruns tests when source changes. The excerpt says this requires no manual configuration or separately starting the development server. It introduces sharing custom Cypress commands across applications in an Nx monorepo as the article's goal, but the provided excerpt ends before explaining how to do that. ### Source excerpt Lorem ipsum dolor sit amet ## Static vs Unit vs Integration vs E2E Testing for Frontend Apps DevFeed: [Static vs Unit vs Integration vs E2E Testing for Frontend Apps]() Original publisher: [Read original article]() Published: 2021-06-03T00:00:00Z Content type: tutorial Language: en Sources: [Kent C. Dodds Blog]() Topics: [Software Testing](), [Front end](), [Cypress]() Tags: [cypress](), [e2e-testing](), [frontend](), [functional-testing](), [integration](), [static](), [testing]() ### AI overview This article explains the Testing Trophy model for frontend applications, covering static, unit, integration, and end-to-end tests. It discusses how to choose a testing strategy and gives examples, including Cypress-based tests. ### Source excerpt What these mean, why they matter, and why they don't ## Balancing Test Coverage vs. Overhead DevFeed: [Balancing Test Coverage vs. Overhead]() Original publisher: [Read original article]() Author: Erik Fogg Published: 2021-03-23T00:00:00Z Content type: article Language: en Sources: [Interrupt]() Topics: [test-coverage](), [Software Testing](), [Embedded Software Dev]() Tags: [e2e-testing](), [firmware](), [test-coverage]() ### AI overview The article examines how teams can balance test coverage with time and budget constraints when rapidly updating firmware for changing hardware components. It describes coverage across code components, branches, configurations, and end-to-end testing, including firmware testing through device interfaces. ### Source excerpt In a perfect world, all software and firmware are given precisely the time and budget it needs to be successful, code is uniformly well-written to industry best practices, and the code is complemented with a complete test suite instrumenting all aspects of the software. In practice, this rarely, if ever, happens! Development teams and organizations continually have to re-prioritize tasks to meet deadlines and avoid going over budget. In this article, we'll cover how you can think about rapidly modifying and updating firmware, testing these changes, all the while allowing you to get the product out the door. Continue reading... ## UI Testing Myths DevFeed: [UI Testing Myths]() Original publisher: [Read original article]() Published: 2018-11-08T00:00:00Z Content type: tutorial Language: en Sources: [Kent C. Dodds Blog]() Topics: [Software Testing](), [ui-testing](), [Cypress](), [testing-library](), [software-development](), [Redux](), [React Router]() Tags: [cypress](), [e2e-testing](), [react](), [redux](), [testing](), [testing-library](), [ui-testing]() ### AI overview The article examines common UI and end-to-end testing myths. It argues for testing user-visible behavior instead of implementation details, testing connected components with real Redux integration, and avoiding repetitive setup and page objects in end-to-end tests. ### Source excerpt Some common myths around testing and what the reality is...